From: Masanari Iida <standby24x7@gmail.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, Masanari Iida <standby24x7@gmail.com>
Subject: [PATCH 2/2] Documentation: mm: Fix path to extfrag_index in vm.txt
Date: Fri, 6 Apr 2012 01:48:09 +0900 [thread overview]
Message-ID: <1333644489-31466-2-git-send-email-standby24x7@gmail.com> (raw)
In-Reply-To: <1333644489-31466-1-git-send-email-standby24x7@gmail.com>
The path for extfrag_index has not been updated even after it moved
to under /sys. This patch fixed the path.
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
---
Documentation/sysctl/vm.txt | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
index c94acad..9dd8555 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -166,11 +166,12 @@ user should run `sync' first.
extfrag_threshold
This parameter affects whether the kernel will compact memory or direct
-reclaim to satisfy a high-order allocation. /proc/extfrag_index shows what
-the fragmentation index for each order is in each zone in the system. Values
-tending towards 0 imply allocations would fail due to lack of memory,
-values towards 1000 imply failures are due to fragmentation and -1 implies
-that the allocation will succeed as long as watermarks are met.
+reclaim to satisfy a high-order allocation.
+/sys/kernel/debug/extfrag/extfrag_index shows what the fragmentation index
+for each order is in each zone in the system. Values tending towards 0
+imply allocations would fail due to lack of memory, values towards 1000
+imply failures are due to fragmentation and -1 implies that the allocation
+will succeed as long as watermarks are met.
The kernel will not compact memory in a zone if the
fragmentation index is <= extfrag_threshold. The default value is 500.
--
1.7.10.rc4
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-05 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 16:48 [PATCH 1/2] Documentation: mm: Add compact_node on Documentation/sysctl/vm.txt Masanari Iida
2012-04-05 16:48 ` Masanari Iida [this message]
2012-04-05 21:41 ` [PATCH 2/2] Documentation: mm: Fix path to extfrag_index in vm.txt David Rientjes
2012-04-05 21:37 ` [PATCH 1/2] Documentation: mm: Add compact_node on Documentation/sysctl/vm.txt David Rientjes
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=1333644489-31466-2-git-send-email-standby24x7@gmail.com \
--to=standby24x7@gmail.com \
--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