From: Andrew Morton <akpm@osdl.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6.8-rc1-mm1] Autotune swappiness01
Date: Sun, 25 Jul 2004 17:36:52 -0700 [thread overview]
Message-ID: <20040725173652.274dcac6.akpm@osdl.org> (raw)
In-Reply-To: <cone.1090801520.852584.20693.502@pc.kolivas.org>
Con Kolivas <kernel@kolivas.org> wrote:
>
> Attached is a patch designed to improve the behaviour of the swappiness knob
> in 2.6.8-rc1-mm1.
>
> The current mechanism decides to reclaim mapped pages based on the
> combination of mapped_ratio/2 and the manual setting of swappiness currently
> tuned to 60. Biasing this mechanism to be proportional to the square root of
> mapped_ratio gives good overall performance improvement for desktop
> workloads without any noticable detriment to other loads.
OK...
> It has the effect
> of being fairly aggressive at avoiding loss of applications to swap under
> conditions of heavy or sustained file stress while allowing applications to
> swap out under what would be considered "application" memory stresses on a
> desktop.
But decreasing /proc/sys/vm/swappiness does that too?
> It has no measurable effect on any known benchmarks.
So how are we to evaluate the desirability of the patch???
> The swappiness knob is kept intact and ironically is set to the same value
> of 60, and overall behaves the same as previous patches posted for
> autoregulating swappiness. The idea of this patch is to ultimately deprecate
> the need for a swappiness knob if this achieves good performance in most
> workloads.
Don't think so. If you have a machine with a lot of memory which is doing
mainly pagecache-intensive work and you also want it to aggressively swap
out anonymous pages (ie: your initials are akpm) then you'll be setting
swappiness to 100.
Shouldn't mapped_bias be local to refill_inactive_zone()?
Why is `swappiness' getting squared? AFAICT this will simply make the
swappiness control behave nonlinearly, which seems undesirable?
next prev parent reply other threads:[~2004-07-26 0:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 0:25 Con Kolivas
2004-07-26 0:36 ` Andrew Morton [this message]
2004-07-26 0:43 ` Con Kolivas
2004-07-26 0:48 ` Andrew Morton
2004-07-26 1:01 ` Con Kolivas
2004-07-26 1:09 ` Con Kolivas
2004-07-26 8:52 ` R. J. Wysocki
2004-07-26 9:31 ` Con Kolivas
2004-07-26 10:34 ` R. J. Wysocki
2004-07-26 10:29 ` Con Kolivas
2004-07-26 10:54 ` R. J. Wysocki
2004-07-26 11:03 ` Con Kolivas
2004-07-26 11:13 ` Nick Piggin
2004-07-26 11:17 ` Con Kolivas
2004-07-26 11:47 ` Nick Piggin
2004-07-26 13:53 ` R. J. Wysocki
2004-07-26 18:45 ` Adam Kropelin
2004-07-26 18:53 ` R. J. Wysocki
2004-07-26 17:55 ` Gerrit Huizenga
2004-07-26 20:29 ` Joel Becker
2004-07-26 20:42 ` Andrew Morton
2004-07-26 22:58 ` Con Kolivas
2004-07-27 0:52 ` Clemens Schwaighofer
2004-07-27 1:09 ` Andrew Morton
2004-07-27 1:17 ` Clemens Schwaighofer
2004-07-27 2:03 ` Tim Connors
2004-07-27 2:43 ` Con Kolivas
2004-07-27 3:02 ` Tim Connors
2004-07-27 3:43 ` Clemens Schwaighofer
2004-07-27 3:47 ` Joel Becker
2004-07-27 15:32 ` William Lee Irwin III
2004-07-27 3:41 ` Clemens Schwaighofer
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=20040725173652.274dcac6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®