From: "Dr. Werner Fink" <werner@suse.de>
To: H.H.vanRiel@fys.ruu.nl
Cc: sct@dcs.ed.ac.uk, teg@pvv.ntnu.no, linux-kernel@vger.rutgers.edu,
linux-mm@kvack.org
Subject: Re: 2.1.89 broken?
Date: Thu, 12 Mar 1998 20:30:16 +0100 [thread overview]
Message-ID: <199803121930.UAA12322@boole.suse.de> (raw)
In-Reply-To: <Pine.LNX.3.91.980312000536.14217A-100000@mirkwood.dummy.home> (message from Rik van Riel on Thu, 12 Mar 1998 00:11:38 +0100 (MET))
> 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 ;-).
Does this mean that mm/filemap.c:shrink_mmap() would call
for it's self in mm/vmscan.c:kswapd() if the level is above
the limit? ... without using mm/vmscan.c:(do_)try_to_free_page()
to become the buffer down without trashing the tasks?
This would need also a wrapper as it does for
do_try_to_free_page() to set/unset the kernel locks.
And this upper limit should be calculated dynamically because
there is a `small' difference between a 8Mb and a 512Mb
system ... the first systems should have a smaller amount
of buffer/cache to keep the system running :-)
Werner
prev parent reply other threads:[~1998-03-12 19:33 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
1998-03-12 19:30 ` Dr. Werner Fink [this message]
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=199803121930.UAA12322@boole.suse.de \
--to=werner@suse.de \
--cc=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