[PATCH] CPUSETS: add mems to basic usage documentation

[PATCH] CPUSETS: add mems to basic usage documentation

[Simon Horman]

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
 

Re: [PATCH] CPUSETS: add mems to basic usage documentation

[Paul Jackson]

Simon Horman wrote:
> +++ linux-2.6/Documentation/cpusets.txt	2007-03-30 13:03:19.000000000 +0900
> ...
> +Add some mems:
> +# /bin/echo 0-7 > mems

Nice change - thanks.

Acked-by: Paul Jackson <pj@sgi.com>


(I probably would not add a dmesg complaint; we don't usually
do that for ordinary system call failures.  Pay close attention
to the resulting errno - in this case ENOSPC.)

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

Re: [PATCH] CPUSETS: add mems to basic usage documentation

[Simon Horman]

On Fri, Mar 30, 2007 at 02:30:47AM -0700, Paul Jackson wrote:
> Simon Horman wrote:
> > +++ linux-2.6/Documentation/cpusets.txt	2007-03-30 13:03:19.000000000 +0900
> > ...
> > +Add some mems:
> > +# /bin/echo 0-7 > mems
> 
> Nice change - thanks.
> 
> Acked-by: Paul Jackson <pj@sgi.com>

Thanks

> (I probably would not add a dmesg complaint; we don't usually
> do that for ordinary system call failures.  Pay close attention
> to the resulting errno - in this case ENOSPC.)

Understood

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/