public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Auto-regulated swappiness
Date: Tue, 03 Feb 2004 15:49:47 -0500	[thread overview]
Message-ID: <4020096B.7000408@techsource.com> (raw)

I just noticed the kerneltrap article about Con's new patchset.  In 
particular, I am curious about the auto-regulated swappiness.

I've done a little searching through the archives, but I can't seem to 
find the lkml posts I'm thinking about.  In any event, I vaguely 
remember two things:

- auto-regulation was developed because the kernel seemed to swap too 
much or too little under certain circumstances.

- Someone said that auto-regulating swappiness didn't make sense, 
because there was some constant value that should have had the desired 
effect.

I don't remember there being a resolution to this discussion.

For my own curiosity, what happens if swappiness is too high but there 
isn't any pressure to swap from memory usage?  Do user pages get swapped 
out in favor of making room for potential buffer pages?

What happens if it's too low and there's lots of pressure to swap?

How does the auto-regulator fix this?

Thanks.


                 reply	other threads:[~2004-02-03 20:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4020096B.7000408@techsource.com \
    --to=miller@techsource.com \
    --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