From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: "Benjamin C.R. LaHaise" <blah@kvack.org>,
Linus Torvalds <torvalds@transmeta.com>,
Itai Nahshon <nahshon@actcom.co.il>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
paubert@iram.es, Ingo Molnar <mingo@chiara.csoma.elte.hu>,
linux-mm@kvack.org
Subject: Re: PATCH: Swap shared pages (was: How to read-protect a vm_area?)
Date: Wed, 25 Feb 1998 23:05:18 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980225225934.884C-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199802251900.TAA00898@dax.dcs.ed.ac.uk>
On Wed, 25 Feb 1998, Stephen C. Tweedie wrote:
> Feel free to comment; I won't be working on this any time in the
> immediate future...
OK, then I'll focus on memory balancing, starting with
the following simple rules:
- buffer memory isn't allowed to grow larger than
twice the size of the pagecache when nr_free_pages < free_pages_high
- if a cached inode uses more than half of the pagecache, and
the pagecache is larger than 1/4th of memory, and
nr_free_pages < 2 * free_pages_high (pfew!), then we won't
allocate new pagecache memory to satisfy _that_ inode's demand,
but steal memory from the pagecache or buffer instead.
- do some form of RSS balancing (later on, after we get the
stats right again).
- document the files in /proc/sys/vm and /proc/sys/kernel
(I've started, but really should finish the files tonight :-)
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
next prev parent reply other threads:[~1998-02-25 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802192321.XAA06580@dax.dcs.ed.ac.uk>
1998-02-20 5:41 ` How to read-protect a vm_area? Benjamin C.R. LaHaise
1998-02-23 23:17 ` PATCH: Swap shared pages (was: How to read-protect a vm_area?) Stephen C. Tweedie
1998-02-23 23:27 ` Linus Torvalds
1998-02-24 0:08 ` Benjamin C.R. LaHaise
1998-02-24 9:45 ` Stephen C. Tweedie
1998-02-24 9:42 ` Rik van Riel
1998-02-24 23:38 ` Stephen C. Tweedie
1998-02-25 10:41 ` Rik van Riel
1998-02-25 19:00 ` Stephen C. Tweedie
1998-02-25 22:05 ` Rik van Riel [this message]
1998-02-24 11:16 ` Thomas Sailer
[not found] ` <Pine.LNX.3.96.980224152231.7112A-100000@renass3.u-strasbg.fr>
1998-02-24 23:38 ` Stephen C. Tweedie
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.980225225934.884C-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=blah@kvack.org \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=nahshon@actcom.co.il \
--cc=paubert@iram.es \
--cc=sct@dcs.ed.ac.uk \
--cc=torvalds@transmeta.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