mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aaron Tomlin <atomlin@redhat.com>
To: mingo@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	rientjes@google.com, mingo@redhat.com, oleg@redhat.com,
	riel@redhat.com, bmr@redhat.com, akpm@linux-foundation.org,
	atomlin@redhat.com
Subject: [PATCH] mm: Document improved handling of swappiness==0
Date: Fri, 24 Jan 2014 15:13:28 +0000	[thread overview]
Message-ID: <1390576408-16673-1-git-send-email-atomlin@redhat.com> (raw)

Prior to upstream commit fe35004f ("[mm] avoid swapping out
with swappiness==0") setting swappiness to 0, reclaim code
could still evict recently used user anonymous memory to swap
even though there is a significant amount of RAM used for page
cache.

The behaviour of setting swappiness to 0 has since changed.
When set, the reclaim code does not initiate swap until the
amount of free pages and file-backed pages, is less than the
high water mark in a zone.

Let's update the documentation to reflect this.

Signed-off-by: Aaron Tomlin <atomlin@redhat.com>
Acked-by: Rik van Riel <riel@redhat.com>
Acked-by: Bryn M. Reeves <bmr@redhat.com>
---
 Documentation/sysctl/vm.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
index 9f5481b..38388ee 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -696,7 +696,9 @@ swappiness
 
 This control is used to define how aggressive the kernel will swap
 memory pages.  Higher values will increase agressiveness, lower values
-decrease the amount of swap.
+decrease the amount of swap.  A value of 0 instructs the kernel not to
+initiate swap until the amount of free and file-backed pages, is less
+than the high water mark in a zone.
 
 The default value is 60.
 
-- 
1.8.4.2


             reply	other threads:[~2014-01-24 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 15:13 Aaron Tomlin [this message]
2014-01-24 18:53 ` Randy Dunlap

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=1390576408-16673-1-git-send-email-atomlin@redhat.com \
    --to=atomlin@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bmr@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    /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

Powered by JetHome