From: Simon Horman <horms@verge.net.au>
To: linux-kernel@vger.kernel.org
Cc: Paul Jackson <pj@sgi.com>, Simon Derr <simon.derr@bull.net>
Subject: [PATCH] CPUSETS: add mems to basic usage documentation
Date: Fri, 30 Mar 2007 13:10:03 +0900 [thread overview]
Message-ID: <20070330041001.GA20566@verge.net.au> (raw)
It seems that there must be at least one node in mems
and at least one CPU in cpus in order to be able to assign
tasks to a cpuset. This makes sense. And I think it would
also make sense to include a mems setting in the basic usage
section of the documentation.
I also wonder if something logged to dmsg, explaining why
a write failed, would be a good enhancement. I ended up having
rummage arround in cpuset.c in order to work out why my
configuration was failing.
Signed-off-by: Simon Horman <horms@verge.net.au>
Index: linux-2.6/Documentation/cpusets.txt
===================================================================
--- linux-2.6.orig/Documentation/cpusets.txt 2007-03-30 13:03:07.000000000 +0900
+++ linux-2.6/Documentation/cpusets.txt 2007-03-30 13:03:19.000000000 +0900
@@ -557,6 +557,9 @@
Add some cpus:
# /bin/echo 0-7 > cpus
+Add some mems:
+# /bin/echo 0-7 > mems
+
Now attach your shell to this cpuset:
# /bin/echo $$ > tasks
next reply other threads:[~2007-03-30 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 4:10 Simon Horman [this message]
2007-03-30 9:30 ` Paul Jackson
2007-03-31 2:37 ` Simon Horman
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=20070330041001.GA20566@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=simon.derr@bull.net \
/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®