From: Paul Jackson <pj@sgi.com>
To: trivial@rustcorp.com.au
Cc: Simon Derr <Simon.Derr@bull.net>, Martin Hicks <mort@sgi.com>,
Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: [Trivial Patch] cpusets docs - a couple typos
Date: Wed, 16 Mar 2005 11:12:30 -0800 (PST) [thread overview]
Message-ID: <20050316191234.25203.12688.sendpatchset@sam.engr.sgi.com> (raw)
Following fixes a couple of trivial typos in the cpusets
Documentation file, that is now in Linus's bk tree.
Thanks to Martin Hicks <mort@sgi.com> for noticing these.
Signed-off-by: Paul Jackson <pj@sgi.com>
===================================================================
--- 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 <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
reply other threads:[~2005-03-16 19:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050316191234.25203.12688.sendpatchset@sam.engr.sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mort@sgi.com \
--cc=trivial@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox