Following fixes a couple of trivial typos in the cpusets
Documentation file, that is now in Linus's bk tree.
Thanks to Martin Hicks <[EMAIL PROTECTED]> for noticing these.
Signed-off-by: Paul Jackson <[EMAIL PROTECTED]>
===================================================================
--- 2.6.12-pj.orig/Documentation/cpusets.txt 2005-03-16 01:04:48.000000000
-0800
+++ 2.6.12-pj/Documentation/cpusets.txt 2005-03-16 11:07:35.000000000 -0800
@@ -130,7 +130,7 @@ Cpusets extends these two mechanisms as
The implementation of cpusets requires a few, simple hooks
into the rest of the kernel, none in performance critical paths:
- - in main/init.c, to initialize the root cpuset at system boot.
+ - in init/main.c, to initialize the root cpuset at system boot.
- in fork and exit, to attach and detach a task from its cpuset.
- in sched_setaffinity, to mask the requested CPUs by what's
allowed in that tasks cpuset.
@@ -138,7 +138,7 @@ into the rest of the kernel, none in per
the CPUs allowed by their cpuset, if possible.
- in the mbind and set_mempolicy system calls, to mask the requested
Memory Nodes by what's allowed in that tasks cpuset.
- - in page_alloc, to restrict memory to allowed nodes.
+ - in page_alloc.c, to restrict memory to allowed nodes.
- in vmscan.c, to restrict page recovery to the current cpuset.
In addition a new file system, of type "cpuset" may be mounted,
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373,
1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
