lkml.org 
[lkml]   [2012]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH 2/2] Documentation: mm: Fix path to extfrag_index in vm.txt
Date
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


\
 
 \ /
  Last update: 2012-04-05 18:51    [W:0.035 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site