From: Andrew Morton <akpm@zip.com.au>
To: Vladimir Dergachev <volodya@mindspring.com>
Cc: linux-mm@kvack.org
Subject: Re: [RFC] start_aggressive_readahead
Date: Mon, 29 Jul 2002 00:53:17 -0700 [thread overview]
Message-ID: <3D44F46D.6B619EFB@zip.com.au> (raw)
In-Reply-To: Pine.LNX.4.44.0207290330280.19060-100000@node2.localnet.net
Vladimir Dergachev wrote:
>
> > > > - It shrinks the window size in response to "misses" - if
> > > > userspace requests a page which is *not* inside the previously-requested
> > > > window, the future window size is shrunk by 25%
> > >
> > > This one seems wierd. If I reference a page that could have been in a
> > > larger read-ahead window, shouldn't I make the window *larger* so that
> > > next time, it *will* be in the window?
> >
> > That's true. If the application is walking across a file
> > touching every fifth page, readahead will stabilise at
> > its minimum window size, which is less than five pages and
> > we lose bigtime. I'm not sure how to fix that while retaining
> > some sanity in the code.
>
> I am curious: which applications do you know of that actually do this ?
None. Just a test program which I used for testing readahead!
> What about growing the window even if there is a miss as long as misses
> are sequential and not further than a fixed amount from the window ?
That would work. If the window size is less than max, and the
miss occurred inside the max, increase the window to a size which
would have caught that page. Or to the max.
-
--
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-29 7:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 16:10 [RFC] start_aggressive_readahead 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 [this message]
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
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=3D44F46D.6B619EFB@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-mm@kvack.org \
--cc=volodya@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.