From: "Stephen C. Tweedie" <sct@redhat.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: Another wish item for your TODO list...
Date: Mon, 23 Oct 2000 23:32:53 +0100 [thread overview]
Message-ID: <20001023233253.E3749@redhat.com> (raw)
In-Reply-To: <20001024002851.G727@nightmaster.csn.tu-chemnitz.de>; from ingo.oeser@informatik.tu-chemnitz.de on Tue, Oct 24, 2000 at 12:28:51AM +0200
Hi,
On Tue, Oct 24, 2000 at 12:28:51AM +0200, Ingo Oeser wrote:
> On Mon, Oct 23, 2000 at 06:36:49PM +0100, Stephen C. Tweedie wrote:
> > On Mon, Oct 23, 2000 at 03:02:06PM -0200, Rik van Riel wrote:
> > > I take it you mean "move all the pages from before the
> > > currently read page to the inactive list", so we preserve
> > > the pages we just read in with readahead ?
> > No, I mean that once we actually remove a page, we should also remove
> > all the other pages IF the file has never been accessed in a
> > non-sequential manner. The inactive management is separate.
>
> *.h files, which are read in by the GCC are always accessed
> sequentielly (at least from the kernel POV) and while unmapping
> them is ok, they should at least remain in cache to speed up
> compiling. That's just one example for a workload which will
> suffer from this idea.
No. If they stay in cache, then that's fine: we won't change the
caching behaviour at all.
All we do is change what happens _after_ the kernel has already
decided to start moving pages of the file out of cache because they
are old. For small sequential files like header files, there's
absolutely no point in having just a few of the pages in cache --- you
know, for sure, that if you need one of the pages, you'll need all of
them. So, once one of the pages is old enough to be evicted from the
cache, there's no point in keeping any of the other pages around.
Cheers,
Stephen
--
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.eu.org/Linux-MM/
prev parent reply other threads:[~2000-10-23 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-23 16:54 Stephen C. Tweedie
2000-10-23 17:02 ` Rik van Riel
2000-10-23 17:36 ` Stephen C. Tweedie
2000-10-23 18:07 ` Rik van Riel
2000-10-23 19:38 ` Stephen C. Tweedie
2000-10-23 20:13 ` Rik van Riel
2000-10-23 20:44 ` Stephen C. Tweedie
2000-10-23 22:28 ` Ingo Oeser
2000-10-23 22:32 ` Stephen C. Tweedie [this message]
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=20001023233253.E3749@redhat.com \
--to=sct@redhat.com \
--cc=ingo.oeser@informatik.tu-chemnitz.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