From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: 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 08:53:33 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0102010824000.17822-100000@freak.distro.conectiva> (raw)
In-Reply-To: <20010201112601.K11607@redhat.com>
On Thu, 1 Feb 2001, Stephen C. Tweedie wrote:
> Hi,
>
> On Wed, Jan 31, 2001 at 04:24:24PM -0800, David Gould wrote:
> >
> > I am skeptical of the argument that we can win by replacing "the least
> > desirable" pages with pages were even less desireable and that we have
> > no recent indication of any need for. It seems possible under heavy swap
> > to discard quite a portion of the useful pages in favor of junk that just
> > happenned to have a lucky disk address.
>
> When readin clustering was added to 2.2 for swap and paging,
> performance for a lot of VM-intensive tasks more than doubled. Disk
> seeks are _expensive_. If you read in 15 neighbouring pages on swapin
> and on average only one of them turns out to be useful, you have still
> halved the number of swapin IOs required. The performance advantages
> are so enormous that easily compensate for the cost of holding the
> other, unneeded pages in memory for a while.
>
> Also remember that the readahead pages won't actually get mapped into
> memory, so they can be recycled easily. So, under swapping you tend
> to find that the extra readin pages are going to be replacing old,
> unneeded readahead pages to some extent, rather than swapping out
> useful pages.
If we're under free memory shortage, "unlucky" readaheads will be harmful.
Currently the swapin readahead code can block waiting for memory to do the
readahead, forcing other pages to be aged/freed more aggressively.
--
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/
next prev parent reply other threads:[~2001-02-01 10:53 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 [this message]
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
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.0102010824000.17822-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=dg@suse.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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