From: Rik van Riel <riel@conectiva.com.br>
To: Scott Kaplan <sfkaplan@cs.amherst.edu>
Cc: linux-mm@kvack.org
Subject: Re: Broad questions about the current design
Date: Mon, 12 Aug 2002 17:55:02 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0208121752480.23404-100000@imladris.surriel.com> (raw)
In-Reply-To: <147C8BD2-AE1D-11D6-8D07-000393829FA4@cs.amherst.edu>
On Mon, 12 Aug 2002, Scott Kaplan wrote:
> I want a simpler, non-scanning structure. I want the CLOCK/LRU SEGQ
> structure that I described. So I'll just go ahead and do that, as it will
> be the basis of some other experiments that I'm trying to do. Once (if?)
> I've managed that, we can try some workloads to see what the overhead of
> scanning is vs. the overhead of minor (non-I/O) page faults for the
> inactive list references. My prediction for the outcome is as follows:
> Anyone think this is interesting?
Absolutely. One thing to keep in mind though is streaming
IO and things like 'find' that touch a LOT of pages once.
We probably want some kind of mechanism to prevent these
streaming IO pages to flush out the whole working set at
once.
kind regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-08-12 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 15:12 Scott Kaplan
2002-08-09 15:52 ` William Lee Irwin III
2002-08-09 15:53 ` Rik van Riel
2002-08-12 9:13 ` Daniel Phillips
2002-08-12 17:58 ` Scott Kaplan
2002-08-12 20:55 ` Rik van Riel [this message]
2002-08-12 21:07 ` Martin J. Bligh
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.4.44L.0208121752480.23404-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=sfkaplan@cs.amherst.edu \
/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