linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: 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 14:45:04 -0200 (BRDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0102011441380.1321-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20010201143606.P11607@redhat.com>

On Thu, 1 Feb 2001, Stephen C. Tweedie wrote:
> On Thu, Feb 01, 2001 at 08:53:33AM -0200, Marcelo Tosatti wrote:
> > On Thu, 1 Feb 2001, Stephen C. Tweedie wrote:
> > 
> > If we're under free memory shortage, "unlucky" readaheads will be harmful.
> 
> I know, it's a balancing act.  But given that even one
> successful readahead per read will halve the number of swapin
> seeks, the performance loss due to the extra scavenging has got
> to be bad to outweigh the benefit.

But only when the extra pages we're reading in don't
displace useful data from memory, making us fault in
those other pages ... causing us to go to the disk
again and do more readahead, which could potentially
displace even more pages, etc...

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.

(and with the size of the inactive list being 1 second worth
of page steals, those pages still have a good chance of being
used before they're being recycled)

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 16:45 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 [this message]
2001-02-01 17:20                 ` Ingo Oeser
2001-02-01 17:54                   ` Rik van Riel
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.0102011441380.1321-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=dg@suse.com \
    --cc=ebiederm@xmission.com \
    --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