From: Nick Piggin <npiggin@suse.de>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Mel Gorman <mel@csn.ul.ie>, Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
heiko.carstens@de.ibm.com, mingo@elte.hu, sachinp@in.ibm.com
Subject: Re: [RFC/PATCH] SLQB: Mark the allocator as broken PowerPC and S390
Date: Thu, 17 Sep 2009 20:51:06 +0200 [thread overview]
Message-ID: <20090917185106.GT18404@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.1.10.0909171437180.5220@V090114053VZO-1>
On Thu, Sep 17, 2009 at 02:38:08PM -0400, Christoph Lameter wrote:
> On Thu, 17 Sep 2009, Nick Piggin wrote:
>
> > > This machine has two CPUs (0, 1) and two nodes with actual memory (2,3).
> > > After applying a patch to kmem_cache_create, I see in the console
> > >
> > > MEL::Creating cache pgd_cache CPU 0 Node 0
> > > MEL::Creating cache pmd_cache CPU 0 Node 0
> > > MEL::Creating cache pid_namespace CPU 0 Node 0
> > > MEL::Creating cache shmem_inode_cache CPU 0 Node 0
> > > MEL::Creating cache scsi_data_buffer CPU 1 Node 0
>
> So we have two nodes 2,3 nothing on node 0 and we are creating caches on
> the node that does not exist? SLQB assumes node 0 is present?
It might do somewhere, but it shouldn't. It will ask for node 0
by default presumably if CPU0 is on node 0, but it should be able
to fall back...
next prev parent reply other threads:[~2009-09-17 18:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 6:37 Pekka Enberg
2009-09-16 6:55 ` David Rientjes
2009-09-16 7:01 ` Pekka Enberg
2009-09-16 8:04 ` Heiko Carstens
2009-09-17 10:08 ` Mel Gorman
2009-09-17 10:29 ` Pekka Enberg
2009-09-17 10:57 ` Mel Gorman
2009-09-17 11:13 ` Pekka Enberg
2009-09-17 11:18 ` Mel Gorman
2009-09-17 11:23 ` Pekka Enberg
2009-09-17 11:41 ` Nick Piggin
2009-09-17 18:18 ` Mel Gorman
2009-09-17 18:28 ` Nick Piggin
2009-09-17 18:38 ` Christoph Lameter
2009-09-17 18:51 ` Nick Piggin [this message]
2009-09-18 15:56 ` Mel Gorman
2009-09-17 11:23 ` Sachin Sant
2009-09-17 11:38 ` Nick Piggin
2009-09-17 11:43 ` Pekka Enberg
2009-09-17 11:52 ` Nick Piggin
2009-09-17 11:55 ` Pekka Enberg
2009-09-17 12:12 ` Heiko Carstens
2009-09-17 12:16 ` Pekka Enberg
2009-09-17 12:21 ` Heiko Carstens
2009-09-17 12:36 ` Nick Piggin
2009-09-17 12:42 ` Pekka Enberg
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=20090917185106.GT18404@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=sachinp@in.ibm.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
all inboxes | Powered by JetHome®