public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <christoph@lameter.com>
Cc: Andi Kleen <ak@suse.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] Run PCI driver initialization on local node
Date: Thu, 7 Jul 2005 12:39:18 +0200	[thread overview]
Message-ID: <20050707103918.GV21330@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0507061232040.720@graphe.net>

On Wed, Jul 06, 2005 at 12:33:51PM -0700, Christoph Lameter wrote:
> On Wed, 6 Jul 2005, Andi Kleen wrote:
> 
> > > That depends on the architecture. Some do round robin allocs for periods 
> > > of time during bootup. I think it is better to explicitly place control 
> > 
> > slab will usually do the right thing because it has a forced
> > local node policy, but __gfp might not.
> 
> The slab allocator will do the right thing with the numa slab allocator in 
> Andrew's tree but not with the one in Linus'tree. The one is Linus tree
> will just pickup whatever slab is available irregardless of the node.

It should usually do the right thing because it
runs on the correct CPUs. The only case that doesn't work 
is freeing on different CPUs than it was allocated, but hopefully
that is not too common during system startup.

And then at some point NUMA aware slab will make it into mainline
I guess.

> Only kmalloc_node will make a reasonable attempt to locate the memory on 
> a specific node.

You forgot __get_free_pages.

-Andi

  reply	other threads:[~2005-07-07 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 13:32 [PATCH] Run PCI driver initialization on local node Andi Kleen
2005-07-06 16:35 ` Christoph Lameter
2005-07-06 17:56   ` Andi Kleen
2005-07-06 18:01     ` Christoph Lameter
2005-07-06 18:13       ` Andi Kleen
2005-07-06 18:28         ` Christoph Lameter
2005-07-06 19:31         ` Christoph Lameter
2005-07-06 19:33     ` Christoph Lameter
2005-07-07 10:39       ` Andi Kleen [this message]
2005-07-07 13:52         ` Christoph Lameter
2005-07-07 14:13           ` Andi Kleen

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=20050707103918.GV21330@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=christoph@lameter.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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