[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0710261052530.15895@schroedinger.engr.sgi.com>
Date: Fri, 26 Oct 2007 10:55:59 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Pavel Machek <pavel@....cz>
cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Daniel Phillips <phillips@...nq.net>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
dkegel@...gle.com, David Miller <davem@...emloft.net>,
Nick Piggin <npiggin@...e.de>
Subject: Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
On Fri, 26 Oct 2007, Pavel Machek wrote:
> > And, _no_, it does not necessarily mean global serialisation. By simply
> > saying there must be N pages available I say nothing about on which node
> > they should be available, and the way the watermarks work they will be
> > evenly distributed over the appropriate zones.
>
> Agreed. Scalability of emergency swapping reserved is simply
> unimportant. Please, lets get swapping to _work_ first, then we can
> make it faster.
Global reserve means that any cpuset that runs out of memory may exhaust
the global reserve and thereby impact the rest of the system. The
emergencies that are currently localized to a subset of the system and
may lead to the failure of a job may now become global and lead to the
failure of all jobs running on it.
But Peter mentioned that he has some way of tracking the amount of memory
used in a certain context (beancounter?) which would address the issue.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists