From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: "Benjamin C.R. LaHaise" <blah@kvack.org>,
Andrea Arcangeli <arcangeli@mbox.queen.it>,
Stephen Tweedie <sct@dcs.ed.ac.uk>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
Linux MM <linux-mm@kvack.org>
Subject: Re: cp file /dev/zero <-> cache [was Re: increasing page size]
Date: Thu, 9 Jul 1998 20:59:57 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980709205619.28236F-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199807091442.PAA01020@dax.dcs.ed.ac.uk>
On Thu, 9 Jul 1998, Stephen C. Tweedie wrote:
> On Tue, 7 Jul 1998 13:50:02 -0400 (EDT), "Benjamin C.R. LaHaise"
> <blah@kvack.org> said:
>
> > Right. I'd rather see a multi-level lru like policy (ie on each cache hit
> > it gets moved up one level in the cache, with the lru'd pages from a given
>
> There's a fundamentally nice property about the multi-level cache
> which we _cannot_ easily emulate with page aging, and that is the
> ability to avoid aging any hot pages at all while we are just
> consuming cold pages. For example, a large "find|xargs grep" can be
> satisfied without staling any of the existing hot cached pages.
Then I'd better incorporate a design for this in the zone
allocator (we could add this to the page_struct, but in
the zone_struct we can make a nice bitmap of it).
OTOH, is it really _that_ much different from an aging
scheme with an initial age of 1?
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
next parent reply other threads:[~1998-07-09 18:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199807091442.PAA01020@dax.dcs.ed.ac.uk>
1998-07-09 18:59 ` Rik van Riel [this message]
1998-07-09 23:37 ` Stephen C. Tweedie
1998-07-10 5:57 ` Rik van Riel
1998-07-11 14:14 ` Rik van Riel
1998-07-11 21:23 ` Stephen C. Tweedie
1998-07-11 22:25 ` Rik van Riel
1998-07-13 13:23 ` Stephen C. Tweedie
1998-07-12 1:47 ` Benjamin C.R. LaHaise
1998-07-13 13:42 ` Stephen C. Tweedie
1998-07-18 22:10 ` Rik van Riel
1998-07-20 16:04 ` Stephen C. Tweedie
1998-07-09 13:01 Zachary Amsden
[not found] <Pine.LNX.3.96.980705072829.17879D-100000@mirkwood.dummy.home>
1998-07-05 11:32 ` Andrea Arcangeli
1998-07-05 17:00 ` Rik van Riel
1998-07-05 18:38 ` Andrea Arcangeli
1998-07-05 19:31 ` Rik van Riel
1998-07-06 10:38 ` Stephen C. Tweedie
1998-07-06 11:42 ` Rik van Riel
1998-07-06 14:20 ` Andrea Arcangeli
1998-07-06 10:31 ` Stephen C. Tweedie
1998-07-06 12:34 ` Andrea Arcangeli
1998-07-06 14:36 ` Stephen C. Tweedie
1998-07-06 19:28 ` Andrea Arcangeli
1998-07-07 12:01 ` Stephen C. Tweedie
1998-07-07 15:54 ` Rik van Riel
1998-07-07 17:32 ` Benjamin C.R. LaHaise
1998-07-08 13:54 ` Stephen C. Tweedie
1998-07-08 21:19 ` Andrea Arcangeli
1998-07-11 11:18 ` Rik van Riel
1998-07-11 21:11 ` Stephen C. Tweedie
1998-07-08 13:45 ` Stephen C. Tweedie
1998-07-08 18:57 ` Rik van Riel
1998-07-08 22:11 ` Stephen C. Tweedie
1998-07-09 7:43 ` Rik van Riel
1998-07-09 20:39 ` Rik van Riel
1998-07-13 11:54 ` Stephen C. Tweedie
1998-07-05 18:57 ` MOLNAR Ingo
1998-07-06 10:24 ` Stephen C. Tweedie
1998-07-06 13:37 ` Eric W. Biederman
1998-07-07 12:35 ` 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.96.980709205619.28236F-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=arcangeli@mbox.queen.it \
--cc=blah@kvack.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
--cc=sct@redhat.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