linux-kernel - [PATCH] CPUSETS: add mems to basic usage documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 Mar 2007 13:10:03 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	linux-kernel@...r.kernel.org
Cc:	Paul Jackson <pj@....com>, Simon Derr <simon.derr@...l.net>
Subject: [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@...ge.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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/