linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	David Gould <dg@suse.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] vma limited swapin readahead
Date: Thu, 1 Feb 2001 15:54:44 -0200 (BRDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0102011552180.1321-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20010201182021.N1173@nightmaster.csn.tu-chemnitz.de>

On Thu, 1 Feb 2001, Ingo Oeser wrote:
> On Thu, Feb 01, 2001 at 02:45:04PM -0200, Rik van Riel wrote:
> > One solution could be to put (most of) the swapin readahead
> > pages on the inactive_dirty list, so pressure by readahead
> > on the resident pages is smaller and the not used readahead
> > pages are reclaimed faster.
> 
> Shouldn't they be on inactive_clean anyway?

No, the inactive_clean pages are reclaimed before the
other inactive pages, and we want to give all pages
an equal chance to be used when we put them on the
inactive list.

This is especially true for freshly read in swap cache
pages, because we _expect_ that some of them will be
used.

> Or do I still not get the new linux mm design? ;-(

Read mm/swap.c::deactivate_page_nolock(), my decision to
put all clean inactive pages directly on inactive_clean
lead to the fact that dirty pages would stick around
forever and page reclaim could be quite unfair towards
clean pages. This was changed later to put all inactive
pages on the inactive_dirty list first and have them
more fairly reclaimed in page_launder.

regards,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com.br/

--
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/

  reply	other threads:[~2001-02-01 17:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31  3:05 Marcelo Tosatti
2001-01-31 10:21 ` Stephen C. Tweedie
2001-01-31  8:40   ` Marcelo Tosatti
2001-01-31 19:40     ` Eric W. Biederman
2001-02-01  0:24       ` David Gould
2001-02-01  7:41         ` Eric W. Biederman
2001-02-01 11:26         ` Stephen C. Tweedie
2001-02-01 10:53           ` Marcelo Tosatti
2001-02-01 14:36             ` Stephen C. Tweedie
2001-02-01 16:45               ` Rik van Riel
2001-02-01 17:20                 ` Ingo Oeser
2001-02-01 17:54                   ` Rik van Riel [this message]
2001-02-01 17:27                 ` Stephen C. Tweedie
2001-02-01 18:59           ` David Gould
2001-02-01 19:07             ` 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=Pine.LNX.4.21.0102011552180.1321-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=dg@suse.com \
    --cc=ebiederm@xmission.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@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