From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Stephen Tweedie <sct@dcs.ed.ac.uk>
Cc: Linux MM <linux-mm@kvack.org>
Subject: on the topic of LRU lists
Date: Sun, 12 Jul 1998 09:15:18 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980712091320.9888A-100000@mirkwood.dummy.home> (raw)
Hi Stephen,
now that I think of multiple lists, it might be nice to
have a 2-level LRU scheme for each type of allocation:
- user pages
- shared stuff
- buffers
- page cache
Then we do a sort of round-robin allocation and memory
pressure will make sure that the amount of memory is
automatically balanced between the different uses.
(just a stupid idea)
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
reply other threads:[~1998-07-13 1:30 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=Pine.LNX.3.96.980712091320.9888A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
/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