From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-mm@kvack.org
Subject: Re: Another wish item for your TODO list...
Date: Tue, 24 Oct 2000 00:28:51 +0200 [thread overview]
Message-ID: <20001024002851.G727@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20001023183649.H2772@redhat.com>; from sct@redhat.com on Mon, Oct 23, 2000 at 06:36:49PM +0100
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.
If you are going to include stuff like this, please make it at
least a sysctl. It would be nice, if I could tell the kernel the
workload I have, that these weird access patterns are quite
normal for me and how to handle them.
Thanks & Regards
Ingo Oeser
--
Feel the power of the penguin - run linux@your.pc
<esc>:x
--
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/
next prev parent reply other threads:[~2000-10-23 22:28 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 [this message]
2000-10-23 22:32 ` 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=20001024002851.G727@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--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