From: Daniel Phillips <phillips@bonn-fries.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Mike Galbraith <mikeg@wen-online.de>,
Frank Dekervel <Frank.dekervel@student.kuleuven.ac.Be>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.8/2.4.9 VM problems
Date: Mon, 20 Aug 2001 23:40:52 +0200 [thread overview]
Message-ID: <20010820213425Z16360-32383+586@humbolt.nl.linux.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0108201609190.538-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0108201609190.538-100000@freak.distro.conectiva>
On August 20, 2001 09:12 pm, Marcelo Tosatti wrote:
> On Mon, 20 Aug 2001, Daniel Phillips wrote:
> > On August 20, 2001 09:14 pm, Mike Galbraith wrote:
> > > We need to get the pages 'actioned' (the only thing that really matters)
> > > off of the dirty list so that they are out of the equation.. that I'm
> > > sure of.
> >
> > Well, except when the page is only going to be used once, or not at all (in
> > the case of an unused readahead page). Otherwise, no, we don't want to have
> > frequently used pages or pages we know nothing about dropping of the inactive
> > queue into the bit-bucket. There's more work to do to make that come true.
>
> Find riel's message with topic "VM tuning" to linux-mm, then take a look
> at the 4th aging option.
>
> That one _should_ be able to make us remove all kinds of "hacks" to do
> drop behind, and also it should keep hot/warm active memory _in cache_
> for more time.
I looked at it yesterday. The problem is, it loses the information about *how*
a page is used: pagecache lookup via readahead has different implications than
actual usage. The other thing that looks a little problematic, which Rik also
pointed out, is the potential long lag before the inactive page is detected.
A lot of IO can take place in this time, filling up the active list with pages
that we could have evicted much earlier.
--
Daniel
next prev parent reply other threads:[~2001-08-20 21:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 13:10 Frank Dekervel
2001-08-19 21:00 ` Daniel Phillips
2001-08-19 21:13 ` 2.4.8/2.4.9 problem Andrey Nekrasov
2001-08-20 21:20 ` Daniel Phillips
2001-08-23 10:04 ` Andrey Nekrasov
2001-08-23 14:46 ` Daniel Phillips
2001-08-23 15:39 ` Stephan von Krawczynski
2001-08-23 18:05 ` Daniel Phillips
2001-08-20 15:40 ` 2.4.8/2.4.9 VM problems Mike Galbraith
2001-08-20 17:10 ` Daniel Phillips
2001-08-20 19:14 ` Mike Galbraith
2001-08-20 20:34 ` Daniel Phillips
2001-08-20 19:12 ` Marcelo Tosatti
2001-08-20 21:40 ` Daniel Phillips [this message]
2001-08-20 20:08 ` Marcelo Tosatti
2001-08-20 20:16 ` Marcelo Tosatti
2001-08-20 22:54 ` Daniel Phillips
2001-08-20 21:50 ` Marcelo Tosatti
2001-08-20 23:29 ` Daniel Phillips
2001-08-20 22:05 ` Marcelo Tosatti
2001-08-20 23:54 ` Daniel Phillips
2001-08-21 1:55 ` Rik van Riel
2001-08-21 3:51 ` Daniel Phillips
2001-08-21 3:58 ` Rik van Riel
2001-08-21 4:11 ` Daniel Phillips
2001-08-21 4:08 ` Rik van Riel
2001-08-20 21:44 ` Rik van Riel
2001-08-20 22:47 ` Daniel Phillips
2001-08-21 4:52 ` Mike Galbraith
2001-08-21 5:14 ` Rik van Riel
2001-08-20 16:13 Benjamin Redelings I
2001-08-20 17:02 ` Rik van Riel
2001-08-20 20:13 ` Daniel Phillips
2001-08-20 19:32 ` Daniel Phillips
2001-08-20 21:38 ` Rik van Riel
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=20010820213425Z16360-32383+586@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=Frank.dekervel@student.kuleuven.ac.Be \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
/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
all inboxes | Powered by JetHome®