mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Tue, 21 Aug 2001 01:54:53 +0200	[thread overview]
Message-ID: <20010820234822Z16360-32383+599@humbolt.nl.linux.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0108201857400.538-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0108201857400.538-100000@freak.distro.conectiva>

On August 21, 2001 12:05 am, Marcelo Tosatti wrote:
> On Tue, 21 Aug 2001, Daniel Phillips wrote:
> > On August 20, 2001 11:50 pm, Marcelo Tosatti wrote:
> > > On Tue, 21 Aug 2001, Daniel Phillips wrote:
> > 
> > > > If you've seen streaming IO pages getting evicted before being used,
> > > > I'd like to know about it because something is broken in that case.
> > > 
> > > I've seen the first page read by "swapin_readahead()" (which is the
> > > actual
> > > page we want to swapin) be evicted _before_ we could actually use it (so
> > > the read_swap_cache_async() call had to read the same page _again_ from
> > > disk).
> > 
> > is that even with yesterday's SetPageReferenced patch to do_swap_page?
> 
> No. It will not help: the call to read_swap_cache_async() is before the
> SetPageReferenced call.

Sure it will.  The readahead page will have to go all the way from one end of 
the inactive_dirty list to the other, then all the way down the 
inactive_clean list.  That should be plenty of time for the SetPageReferenced 
to catch it.  The main possibility to screw up is if we scan the inactive 
lists too fast, which probably happens sometimes because it's all grossly 
uncalibrated right now.

That's another issue, it needs fixing.  We'll never have really consistent, 
predictable aging or any other vm behaviour until the list scanning is 
operating in a rock-solid way.

As long as it isn't happening frequently we will be ok for now.

--
Daniel

  reply	other threads:[~2001-08-20 23:48 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
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 [this message]
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=20010820234822Z16360-32383+599@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®