From: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Elie De Brauwer
<eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 1/2] proc.5: Explain /proc/sys/vm/compact_memory
Date: Thu, 22 Jan 2015 20:21:02 +0100 [thread overview]
Message-ID: <1421954463-2853-2-git-send-email-eliedebrauwer@gmail.com> (raw)
In-Reply-To: <1421954463-2853-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Since 2.6.36 [1] CONFIG_COMPACTION is supported in Linux (for a
detailed explanation see [2]). But in essence the contents of /proc/buddyinfo
shows how much contiguous areas of a certain size are available. These
numbers are not actually up to date as the Linux kernel will implicitely
trigger compaction (+- defragmentation) when an allocation is done.
This makes it difficult since you can't predict upfront whether or not a
large allocation will succeed or not.
By using /proc/sys/vm/compact_memory you can explicitely trigger compaction
to occur and /proc/buddyinfo will give a more realistic view on the
available memory in contiguous areas.
This patch updates proc.5 to explain the usage of this file and is
inspired upon Documentation/systcl/vm.txt [3]
[1] http://kernelnewbies.org/Linux_2_6_35#head-9cb0a1275559d40296da42efb7977896ac9edab7
[2] http://lwn.net/Articles/368869/
[3] http://lxr.free-electrons.com/source/Documentation/sysctl/vm.txt#L100
Signed-off-by: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
man5/proc.5 | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/man5/proc.5 b/man5/proc.5
index 860eb66..5bff2a0 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -3943,6 +3943,15 @@ On some systems, it is not present.
This directory contains files for memory management tuning, buffer and
cache management.
.TP
+.IR /proc/sys/vm/compact_memory " (since Linux 2.6.35)"
+When 1 is written to this file, all zones are compacted such that free
+memory is available in contiguous blocks where possible.
+The effect of this action can be seen by examining
+.IR /proc/buddyinfo .
+.IP
+Only present if the kernel was configured with
+.BR CONFIG_COMPACTION .
+.TP
.IR /proc/sys/vm/drop_caches " (since Linux 2.6.16)"
Writing to this file causes the kernel to drop clean caches, dentries, and
inodes from memory, causing that memory to become free.
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-22 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 19:21 [PATCH 0/2] proc.5 modification Elie De Brauwer
[not found] ` <1421954463-2853-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-22 19:21 ` Elie De Brauwer [this message]
[not found] ` <1421954463-2853-2-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-22 19:52 ` [PATCH 1/2] proc.5: Explain /proc/sys/vm/compact_memory Michael Kerrisk (man-pages)
2015-01-22 19:21 ` [PATCH 2/2] proc.5: tfix Elie De Brauwer
[not found] ` <1421954463-2853-3-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-22 19:53 ` Michael Kerrisk (man-pages)
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=1421954463-2853-2-git-send-email-eliedebrauwer@gmail.com \
--to=eliedebrauwer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.