]> bbs.cooldavid.org Git - net-next-2.6.git/commit
[PATCH] CPUSETS: add mems to basic usage documentation
authorSimon Horman <horms@verge.net.au>
Mon, 2 Apr 2007 06:49:40 +0000 (23:49 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Mon, 2 Apr 2007 17:06:08 +0000 (10:06 -0700)
commit2400ff77e7025bf6ffb71afdcbfbdd9aa47dfc36
tree6aade9c4ab95e81ef6385ed84d4dc2f4a5f9f2d4
parentbf703c3f199342da440a30798b6120f391741ffe
[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 <horms@verge.net.au>
Acked-by: Paul Jackson <pj@sgi.com>
Cc: Paul Menage <menage@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Documentation/cpusets.txt