Commit 2400ff77 authored by Simon Horman's avatar Simon Horman Committed by Linus Torvalds

[PATCH] CPUSETS: add mems to basic usage documentation

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: default avatarSimon Horman <horms@verge.net.au>
Acked-by: default avatarPaul Jackson <pj@sgi.com>
Cc: Paul Menage <menage@google.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent bf703c3f
...@@ -557,6 +557,9 @@ Set some flags: ...@@ -557,6 +557,9 @@ Set some flags:
Add some cpus: Add some cpus:
# /bin/echo 0-7 > cpus # /bin/echo 0-7 > cpus
Add some mems:
# /bin/echo 0-7 > mems
Now attach your shell to this cpuset: Now attach your shell to this cpuset:
# /bin/echo $$ > tasks # /bin/echo $$ > tasks
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment