From: Daniel Phillips <phillips@bonn-fries.net>
To: Rik van Riel <riel@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Helge Hafting <helgehaf@idb.hist.no>, <linux-kernel@vger.kernel.org>
Subject: Re: VM working much better in 2.4.8 than before
Date: Tue, 14 Aug 2001 15:03:51 +0200 [thread overview]
Message-ID: <20010814125859Z16031-1231+838@humbolt.nl.linux.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108131245200.6118-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0108131245200.6118-100000@imladris.rielhome.conectiva>
On August 13, 2001 05:52 pm, Rik van Riel wrote:
> On Mon, 13 Aug 2001, Alan Cox wrote:
> > > Yes, those would be the expected effects of use-once, in fact it was
> > > "morning after updatedb" question that got me started on it.
> >
> > updatedb is also absolutely fine if you just work with the existing VM
> > and up the inode pressure a little. I'm still very unconvinced by
> > use-once.
>
> Use-once has a number of theoretical disadvantages too:
>
> 1) newly read in pages are evicted earlier, this means
> readahead pages will either evict each other or the
> amount of readahead done might need to be shrunk
> -- the current readahead code is not prepared for this,
> use-once could lead to more disk seeks being done
Have you actually seen this happening?
> 2) since we add new pages to the inactive list, VM
> balancing is faced with a really strange situation ;)
>
> Yes, these things are solvable, but not without redesigning
> major parts of the VM balancing to do things which have never
> been done before. I'm not sure 2.4 is the time to do that.
--
Daniel
prev parent reply other threads:[~2001-08-14 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 3:48 misty-
2001-08-13 8:41 ` Helge Hafting
2001-08-13 10:55 ` Daniel Phillips
2001-08-13 12:41 ` Alan Cox
2001-08-13 15:52 ` Rik van Riel
2001-08-14 13:03 ` Daniel Phillips [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=20010814125859Z16031-1231+838@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®