From: Mel Gorman <mel@csn.ul.ie>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
heiko.carstens@de.ibm.com, sachinp@in.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Tejun Heo <tj@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [RFC PATCH 0/3] Fix SLQB on memoryless configurations V2
Date: Tue, 22 Sep 2009 11:24:16 +0100 [thread overview]
Message-ID: <20090922102415.GF12254@csn.ul.ie> (raw)
In-Reply-To: <1253614875.30406.12.camel@penberg-laptop>
On Tue, Sep 22, 2009 at 01:21:15PM +0300, Pekka Enberg wrote:
> Hi Mel,
>
> On Tue, 2009-09-22 at 11:05 +0100, Mel Gorman wrote:
> > I'm going to punt the decision on this one to Pekka or Nick. My feeling
> > is leave it enabled for NUMA so it can be identified if it gets fixed
> > for some other reason - e.g. the stalls are due to a per-cpu problem as
> > stated by Sachin and SLQB happens to exasperate the problem.
>
> Can I have a tested patch that uses MAX_NUMNODES to allocate the
> structs, please? We can convert SLQB over to per-cpu allocator if the
> memoryless node issue is resolved.
>
Patch set in the process of testing. Should have something in a few
hours.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2009-09-22 10:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 16:10 [RFC PATCH 0/3] Fix SLQB on memoryless configurations V2 Mel Gorman
2009-09-21 16:10 ` [PATCH 1/3] powerpc: Allocate per-cpu areas for node IDs for SLQB to use as per-node areas Mel Gorman
2009-09-21 17:17 ` Daniel Walker
2009-09-21 17:24 ` Randy Dunlap
2009-09-21 17:29 ` Daniel Walker
2009-09-21 17:42 ` Mel Gorman
2009-09-22 0:01 ` Tejun Heo
2009-09-22 9:32 ` Mel Gorman
2009-09-21 16:10 ` [PATCH 2/3] slqb: Record what node is local to a kmem_cache_cpu Mel Gorman
2009-09-21 16:10 ` [PATCH 3/3] slqb: Allow SLQB to be used on PPC Mel Gorman
2009-09-22 9:30 ` Heiko Carstens
2009-09-22 9:32 ` Mel Gorman
2009-09-21 17:46 ` [RFC PATCH 0/3] Fix SLQB on memoryless configurations V2 Mel Gorman
2009-09-21 17:54 ` Christoph Lameter
2009-09-21 18:05 ` Pekka Enberg
2009-09-21 18:07 ` Mel Gorman
2009-09-21 18:17 ` Christoph Lameter
2009-09-22 10:05 ` Mel Gorman
2009-09-22 10:21 ` Pekka Enberg
2009-09-22 10:24 ` Mel Gorman [this message]
2009-09-22 5:03 ` Sachin Sant
2009-09-22 10:07 ` Mel Gorman
2009-09-22 12:55 ` Mel Gorman
2009-09-22 13:05 ` Sachin Sant
2009-09-22 13:20 ` Mel Gorman
[not found] ` <363172900909220629j2f5174cbo9fe027354948d37@mail.gmail.com>
2009-09-22 13:38 ` Mel Gorman
2009-09-22 23:07 ` Christoph Lameter
2009-09-22 0:00 ` Benjamin Herrenschmidt
2009-09-22 0:19 ` David Rientjes
2009-09-22 6:30 ` Christoph Lameter
2009-09-22 7:59 ` David Rientjes
2009-09-22 8:11 ` Benjamin Herrenschmidt
2009-09-22 8:44 ` David Rientjes
2009-09-22 15:26 ` Mel Gorman
2009-09-22 17:31 ` David Rientjes
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=20090922102415.GF12254@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=benh@kernel.crashing.org \
--cc=cl@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=sachinp@in.ibm.com \
--cc=tj@kernel.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).