From: Scott Kaplan <sfkaplan@cs.amherst.edu>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Andrew Morton <akpm@zip.com.au>,
Rik van Riel <riel@conectiva.com.br>,
Christoph Hellwig <hch@lst.de>,
linux-mm@kvack.org
Subject: Re: [RFC] start_aggressive_readahead
Date: Tue, 30 Jul 2002 12:38:52 -0400 [thread overview]
Message-ID: <D4FAAB57-A3DA-11D6-9922-000393829FA4@cs.amherst.edu> (raw)
In-Reply-To: <644994853.1028020916@[10.10.2.3]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, July 30, 2002, at 12:21 PM, Martin J. Bligh wrote:
> Thus I'd contend that either growing or shrinking in straight
> response to just a hit/miss rate is not correct. We need to actually
> look at the access pattern of the application, surely?
I agree. I probably should have made it clear that what I was suggesting
wasn't the right way to go about it, but rather an argument against the
heuristics that seemed backwards to me.
The causes for misses are necessarily as clear cut as you mentioned, as
there are a lot of behaviors that are neither fully random nor fully
sequential. So, while it is ideal to have some foresight before resizing
the window -- some calculation that determines whether or not growth will
help or shrinkage will hurt -- it will require the VM system to gather hit
distributions. I'm trying to make that happen right now, although for all
VM pages, and not for the specific purpose of read-ahead calculations.
However, the paper for which I gave a pointer (in a shameless act of self
promotion) proposes exactly that: Keeping reference distributions for
read-ahead and non-read-ahead pages, and then balancing the two against
each other in an attempt to determine what the best read-ahead window size
would be given recent reference behavior.
There may be simpler, kruftier, and/or more effective versions of what I
proposed, but what you said above is, I think, the right idea.
Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org
iD8DBQE9RsEf8eFdWQtoOmgRAp+vAJoCF6mUgAI42x6Bac4A2/u+7oZXIwCdHVqZ
AQCPlqTF+84udI5xSWqYWas=
=swZ6
-----END PGP SIGNATURE-----
--
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-07-30 16:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 16:10 Christoph Hellwig
2002-07-25 16:44 ` Rik van Riel
2002-07-25 19:40 ` Andrew Morton
2002-07-26 16:50 ` Scott Kaplan
2002-07-26 19:38 ` Andrew Morton
2002-07-28 23:32 ` Scott Kaplan
2002-07-29 0:19 ` Rik van Riel
2002-07-29 2:12 ` Scott Kaplan
2002-07-29 3:05 ` Rik van Riel
2002-07-29 15:24 ` Scott Kaplan
2002-07-29 7:34 ` Andrew Morton
2002-07-29 7:37 ` Vladimir Dergachev
2002-07-29 7:53 ` Andrew Morton
2002-07-29 8:04 ` Rik van Riel
2002-07-30 16:11 ` Scott Kaplan
2002-07-30 16:21 ` Martin J. Bligh
2002-07-30 16:38 ` Scott Kaplan [this message]
2002-07-30 16:52 ` Martin J. Bligh
2002-08-05 18:54 ` Scott Kaplan
2002-07-30 17:13 ` William Lee Irwin III
2002-07-26 20:14 ` Stephen Lord
2002-07-26 20:29 ` Andrew Morton
2002-07-26 6:53 ` Daniel Phillips
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=D4FAAB57-A3DA-11D6-9922-000393829FA4@cs.amherst.edu \
--to=sfkaplan@cs.amherst.edu \
--cc=Martin.Bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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