From: "Stone Wang" <pwstone@gmail.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH][4/8] Documentation/vm: minor corrections
Date: Mon, 20 Mar 2006 08:37:30 -0500 [thread overview]
Message-ID: <bc56f2f0603200537t234d75aau@mail.gmail.com> (raw)
Minor corrections of vm documentation.
Signed-off-by: Shaoping Wang <pwstone@gmail.com>
--
hugetlbpage.txt | 2 +-
locking | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -urN linux-2.6.15.orig/Documentation/vm/hugetlbpage.txt
linux-2.6.15/Documentation/vm/hugetlbpage.txt
--- linux-2.6.15.orig/Documentation/vm/hugetlbpage.txt 2006-01-02
22:21:10.000000000 -0500
+++ linux-2.6.15/Documentation/vm/hugetlbpage.txt 2006-03-06
06:30:06.000000000 -0500
@@ -59,7 +59,7 @@
This command will try to configure 20 hugepages in the system. The success
or failure of allocation depends on the amount of physically contiguous
-memory that is preset in system at this time. System administrators may want
+memory that is present in system at this time. System administrators may want
to put this command in one of the local rc init file. This will enable the
kernel to request huge pages early in the boot process (when the possibility
of getting physical contiguous pages is still very high).
diff -urN linux-2.6.15.orig/Documentation/vm/locking
linux-2.6.15/Documentation/vm/locking
--- linux-2.6.15.orig/Documentation/vm/locking 2006-01-02
22:21:10.000000000 -0500
+++ linux-2.6.15/Documentation/vm/locking 2006-03-07 03:43:44.000000000 -0500
@@ -37,7 +37,7 @@
4. The exception to this rule is expand_stack, which just
takes the read lock and the page_table_lock, this is ok
because it doesn't really modify fields anybody relies on.
-5. You must be able to guarantee that while holding page_table_lock
+5. You must be able to guarantee that while holding mmap_sem
or page_table_lock of mm A, you will not try to get either lock
for mm B.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2006-03-20 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 13:37 Stone Wang [this message]
2006-03-21 12:21 ` Nick Piggin
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=bc56f2f0603200537t234d75aau@mail.gmail.com \
--to=pwstone@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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