From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
Robin Holt <holt@sgi.com>, Brent Casavant <bcasavan@sgi.com>,
Christoph Rohland <cr@sap.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] tmpfs: recommend remount for mpol
Date: Fri, 24 Feb 2006 20:18:49 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0602242015490.4431@goblin.wat.veritas.com> (raw)
akpm points out that switching to a non-NUMA kernel could be irritating
if mounting tmpfs fails on an mpol option: tmpfs.txt recommend remount.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
---
Documentation/filesystems/tmpfs.txt | 9 +++++++++
1 files changed, 9 insertions(+)
--- 2.6.16-rc4-git7/Documentation/filesystems/tmpfs.txt 2006-02-24 19:56:07.000000000 +0000
+++ linux/Documentation/filesystems/tmpfs.txt 2006-02-24 19:56:45.000000000 +0000
@@ -92,6 +92,15 @@ NodeList format is a comma-separated lis
a range being two hyphen-separated decimal numbers, the smallest and
largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15
+Note that trying to mount a tmpfs with an mpol option will fail if the
+running kernel does not support NUMA; and will fail if its nodelist
+specifies a node >= MAX_NUMNODES. If your system relies on that tmpfs
+being mounted, but from time to time runs a kernel built without NUMA
+capability (perhaps a safe recovery kernel), or configured to support
+fewer nodes, then it is advisable to omit the mpol option from automatic
+mount options. It can be added later, when the tmpfs is already mounted
+on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'.
+
To specify the initial root directory you can use the following mount
options:
reply other threads:[~2006-02-24 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0602242015490.4431@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bcasavan@sgi.com \
--cc=cr@sap.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®