X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=Documentation%2Fcpusets.txt;fp=Documentation%2Fcpusets.txt;h=76b44290c1546c50a4e15527c18a19e626249f35;hb=16c70f8c1b54b61c3b951b6fb220df250fe09b32;hp=159e2a0c3e80fa229fd2ff95f0e2015caf017ab7;hpb=4e76c8a9fa413ccc09d3f7f664183dcce3555d57;p=linux-2.6.git

diff --git a/Documentation/cpusets.txt b/Documentation/cpusets.txt
index 159e2a0c3..76b44290c 100644
--- a/Documentation/cpusets.txt
+++ b/Documentation/cpusets.txt
@@ -217,6 +217,12 @@ exclusive cpuset.  Also, the use of a Linux virtual file system (vfs)
 to represent the cpuset hierarchy provides for a familiar permission
 and name space for cpusets, with a minimum of additional kernel code.
 
+The cpus file in the root (top_cpuset) cpuset is read-only.
+It automatically tracks the value of cpu_online_map, using a CPU
+hotplug notifier.  If and when memory nodes can be hotplugged,
+we expect to make the mems file in the root cpuset read-only
+as well, and have it track the value of node_online_map.
+
 
 1.4 What are exclusive cpusets ?
 --------------------------------