From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
linux-mm@kvack.org, shai@scalex86.org
Subject: Re: [rfc] [patch] mm: zone_reclaim fix for pseudo file systems
Date: Mon, 30 Jul 2007 22:58:09 -0700 [thread overview]
Message-ID: <20070730225809.ed0a95ff.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707302224190.30889@schroedinger.engr.sgi.com>
On Mon, 30 Jul 2007 22:33:03 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:
> On Mon, 30 Jul 2007, Andrew Morton wrote:
>
> > Nonsense. The VM used to handle it just fine. That's what I wrote the
> > all_unreclaimable logic *for*. It wasn't just added as typing practice.
>
> That is if the whole zone is unreclaimable. The problems that we want to
> solve are due to parts of a zone being unreclaimable and due to the VM
> counters giving an inaccurate picture of the memory situation.
Where is the evidence that this is happening in Kiran's situation?
> > See? "general".
>
> Nope. Its a special situation in which the whole zone has become
> unhandleable by the reclaim logic so it gives up and waits for things
> somehow to get better.
yes.
> During that time we cannot allocate from a zone
> which typically makes a vital zone or a node unusuable.
Of course you can't - there are no free pages and none are reclaimable.
> In a NUMA
> configuration performance degrades in unacceptable ways.
No it won't - you must be referring to something else, or speculating.
> What we want is to remove the unreclaimable pages from the LRU and have
> reclaim continue on the remainder of the zone.
Well that might be what we want. afacit we don't know yet.
> > No, let us not. If the existing crap isn't working as it should (and as it
> > used to) let us first fix (or at least understand) that before adding more
> > crap.
> >
> > No?
>
> The all_reclaimable logic is different. It was never been designed to
> remove the unreclaimable pages.
Of course not. But I don't know how you can be proposing solutions
without yet knowing what the problem is.
The first thing Kiran should have done was to gather a kernel profile. If
we're spending a lot (proably half) of time in shrink_active_lsit() then
yeah, that's a plausible theory.
And yes, keeping these pages off the LRU does make sense, and it heaps
easier to handle than mlocked pages.
Sorry, I just go crazy when I see these random pokes at the VM which
are nowhere near being backed by sufficient analysis of the problem
which they allegedly solve.
The _theory_ here is that a large number (but not all) of the pages
in the zone are in ramfs and so page reclaim is making some progress,
but reclaim efficiency is low, hence there is high CPU consumption.
OK, plausible. But where's the *proof*? We probably already have
sufficient statistics to be able to prove this.
--
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-07-31 5:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 23:27 Ravikiran G Thirumalai
2007-07-30 18:12 ` Christoph Lameter
2007-07-30 20:23 ` Andrew Morton
2007-07-30 20:31 ` Christoph Lameter
2007-07-30 21:12 ` Lee Schermerhorn
2007-07-31 0:01 ` Ravikiran G Thirumalai
2007-07-31 0:20 ` Andrew Morton
2007-07-31 0:27 ` Christoph Lameter
2007-07-31 1:06 ` Andrew Morton
2007-07-31 1:52 ` Christoph Lameter
2007-07-31 1:56 ` Ravikiran G Thirumalai
2007-07-31 2:01 ` Christoph Lameter
2007-07-31 2:27 ` Andrew Morton
2007-07-31 2:36 ` Christoph Lameter
2007-07-31 4:47 ` Andrew Morton
2007-07-31 5:00 ` Christoph Lameter
2007-07-31 5:17 ` Andrew Morton
2007-07-31 5:33 ` Christoph Lameter
2007-07-31 5:58 ` Andrew Morton [this message]
2007-07-31 6:09 ` Christoph Lameter
2007-07-31 6:18 ` Andrew Morton
2007-07-31 19:35 ` Christoph Lameter
2007-07-31 19:46 ` Andrew Morton
2007-07-31 19:50 ` Christoph Lameter
2007-07-31 8:27 ` Ravikiran G Thirumalai
2007-07-31 8:35 ` Andrew Morton
2007-07-31 19:30 ` Christoph Lameter
2007-07-31 19:20 ` Christoph Lameter
2007-07-31 7:15 ` Ravikiran G Thirumalai
2007-07-31 19:18 ` Christoph Lameter
2007-07-31 1:36 ` Ravikiran G Thirumalai
2007-07-31 1:53 ` Andrew Morton
2007-07-31 1:56 ` Christoph Lameter
2007-07-31 2: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=20070730225809.ed0a95ff.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=kiran@scalex86.org \
--cc=linux-mm@kvack.org \
--cc=shai@scalex86.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