All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] Documentation: mm: fix location of extfrag_index
@ 2015-07-14  5:35 Rabin Vincent
  2015-07-14 18:42 ` Jonathan Corbet
  0 siblings, 1 reply; 2+ messages in thread
From: Rabin Vincent @ 2015-07-14  5:35 UTC (permalink / raw)
  To: corbet, akpm; +Cc: linux-kernel, linux-doc, Rabin Vincent

/proc/extfrag_index does not exist.  This file is in debugfs.  Fix the
description of extfrag_threshold to reflect this.

Signed-off-by: Rabin Vincent <rabin.vincent@axis.com>
---
 Documentation/sysctl/vm.txt |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
index 9832ec5..9c3f2f8 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -225,11 +225,11 @@ with your system.  To disable them, echo 4 (bit 3) into drop_caches.
 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. The extfrag/extfrag_index file in
+debugfs 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.4


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] Documentation: mm: fix location of extfrag_index
  2015-07-14  5:35 [PATCH] Documentation: mm: fix location of extfrag_index Rabin Vincent
@ 2015-07-14 18:42 ` Jonathan Corbet
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2015-07-14 18:42 UTC (permalink / raw)
  To: Rabin Vincent; +Cc: akpm, linux-kernel, linux-doc, Rabin Vincent

On Tue, 14 Jul 2015 07:35:11 +0200
Rabin Vincent <rabin.vincent@axis.com> wrote:

> /proc/extfrag_index does not exist.  This file is in debugfs.  Fix the
> description of extfrag_threshold to reflect this.

Applied to the docs tree, thanks.

jon

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-07-14 18:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-14  5:35 [PATCH] Documentation: mm: fix location of extfrag_index Rabin Vincent
2015-07-14 18:42 ` Jonathan Corbet

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.