[PATCH 2/2] Documentation: mm: Fix path to extfrag_index in vm.txt

[Masanari Iida]

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@xxxxxxxxx>
---
 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/