From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: Trond Eivind Glomsrod <teg@pvv.ntnu.no>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: 2.1.89 broken?
Date: Thu, 12 Mar 1998 00:11:38 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980312000536.14217A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199803112237.WAA04217@dax.dcs.ed.ac.uk>
On Wed, 11 Mar 1998, Stephen C. Tweedie wrote:
> No, it's not necessarily doing the Right Thing. The trouble is that
> there is no balancing between swapping and emptying the page cache.
I've still got some Digital Unix-like balancing code
lying around...
Basically, you can set 3 values for the buffer/page
cache, a minimum value, a maximum value and a steal
value. When the buffer/page memory is above steal
level and the system needs memory, it'll steal memory
from the page cache first. A good default would be
25% of main memory. Of course, these values will be
sysctl controllable (we still got 8 unused variables
in swap_control ;-).
> Now, once we've got a single pass which can scavenge BOTH page cache
> and swap pages, then we're really going to be cooking on gas. :) For
I think we should just copy DU's scheme:
- when buffer/page cache is above steal level, we steal that memory
- otherwise, we steal in a round-robin fashion from both
> now, however, all we're doing is tweaking what is a very very delicate
> balance, and as we proved in the 1.2.4 and 1.2.5 swapping disasters,
> getting such a change done in a way which doesn't make at least
> somebody's performance very much worse is really quite hard to do in
> the current way of managing memory. When I was doing the first round
> of work on kswap, it was this balance between cache and swap which was
> the biggest problem, not the aging of individual pages from either
> source.
That's why we have sysctl controllable swapping. And now
we're talking about it, the sysctl really needs updating
too...
You can expect these patches RSN (maybe even tomorrow).
grtz,
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.fys.ruu.nl/~riel/ | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+
next prev parent reply other threads:[~1998-03-12 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3vhtnzc9g.fsf@s9412a.steinan.ntnu.no>
[not found] ` <Pine.LNX.3.91.980310093615.12682A-100000@mirkwood.dummy.home>
1998-03-11 22:37 ` Stephen C. Tweedie
1998-03-11 23:11 ` Rik van Riel [this message]
1998-03-12 19:30 ` Dr. Werner Fink
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=Pine.LNX.3.91.980312000536.14217A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
--cc=teg@pvv.ntnu.no \
/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