Commit:     2400ff77e7025bf6ffb71afdcbfbdd9aa47dfc36
Parent:     bf703c3f199342da440a30798b6120f391741ffe
Author:     Simon Horman <[EMAIL PROTECTED]>
AuthorDate: Sun Apr 1 23:49:40 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Mon Apr 2 10:06:08 2007 -0700

    [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: Simon Horman <[EMAIL PROTECTED]>
    Acked-by: Paul Jackson <[EMAIL PROTECTED]>
    Cc: Paul Menage <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 Documentation/cpusets.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/Documentation/cpusets.txt b/Documentation/cpusets.txt
index 842f0d1..f2c0a68 100644
--- a/Documentation/cpusets.txt
+++ b/Documentation/cpusets.txt
@@ -557,6 +557,9 @@ Set some flags:
 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
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to