From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>, linux-mm@kvack.org
Subject: Re: Drop PageReclaim()
Date: Thu, 8 Feb 2007 17:18:47 -0800 [thread overview]
Message-ID: <20070208171847.e7902ca7.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702081700360.15866@schroedinger.engr.sgi.com>
On Thu, 8 Feb 2007 17:06:33 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:
> On Thu, 8 Feb 2007, Andrew Morton wrote:
>
> > I doubt it. One would need to troll five-year-old changelogs and mailing
> > list discussion, but iirc that rotation was a large win in certain
> > workloads, preventing scanning meltdowns and general memory stress.
>
> I'd expect trouble here because of the taking of a LRU lock per page.
PG_reclaim is there to prevent that problem (amongst other things).
If the proportion of written-back pages due to the page scanner is large,
things already suck. The VM tries to minimise that IO and to maximise the
inode-based writeback.
> For
> large amounts of concurrent I/O this could be an issue.
>
> > > One additional issue that is raised by the writeback pages remaining on
> > > the LRU lists is that we can get into the same livelock situation as with
> > > mlocked pages if we keep on skipping over writeback pages.
> >
> > That's why we rotate the reclaimable pages back to the head-of-queue.
>
> I think the reclaim writeout is one minor contributor here.
To what?
> If there are
> large amounts of writeback pages from f.e. streaming general I/O then we
> may run still into bad situations because we need to scan over them.
If the inactive list is small relative to the number of under-writeback
pages in the zone then there could be problems there. But we just throttle
and wait for some pages to come clean, which seems to work OK.
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-09 1:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 14:13 Drop PageReclaim() Christoph Lameter
2007-02-07 14:32 ` Hugh Dickins
2007-02-08 21:20 ` Christoph Lameter
2007-02-08 21:38 ` Christoph Lameter
2007-02-08 21:42 ` Christoph Lameter
2007-02-08 21:55 ` Christoph Lameter
2007-02-08 22:03 ` Andrew Morton
2007-02-08 22:14 ` Christoph Lameter
2007-02-08 22:24 ` Andrew Morton
2007-02-08 22:26 ` Christoph Lameter
2007-02-08 22:37 ` Andrew Morton
2007-02-08 22:40 ` Christoph Lameter
2007-02-08 23:13 ` Andrew Morton
2007-02-09 0:22 ` Christoph Lameter
2007-02-09 0:39 ` Andrew Morton
2007-02-09 1:06 ` Christoph Lameter
2007-02-09 1:18 ` Andrew Morton [this message]
2007-02-11 5:12 ` Rik van Riel
2007-02-07 17:25 ` Andrew Morton
2007-02-08 21:19 ` Christoph Lameter
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=20070208171847.e7902ca7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).