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: Wed, 6 Jul 2005 20:13:49 +0200	[thread overview]
Message-ID: <20050706181349.GN21330@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0507061058260.30702@graphe.net>

On Wed, Jul 06, 2005 at 11:01:14AM -0700, Christoph Lameter wrote:
> On Wed, 6 Jul 2005, Andi Kleen wrote:
> 
> > On Wed, Jul 06, 2005 at 09:35:32AM -0700, Christoph Lameter wrote:
> > > On Wed, 6 Jul 2005, Andi Kleen wrote:
> > > 
> > > > Instead of adding messy kmalloc_node()s everywhere run the 
> > > > PCI driver probe on the node local to the device.
> > > > Then the normal NUMA aware allocators do the right thing.
> > > 
> > > 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.
> 
> GFP allocs may not do the right thing. If you want to do this then it 
> may be best to set the memory policy to restrict allocations to the node 
> on which the device resides.

They will do the right thing. Under memory pressue on the node 
it is better to back off than to fail.

> 
> Plus there are CPU less nodes. What happens to those?

They are not worse off that they are now.

> 
> > Patching every driver in existence? That sounds like a lot of
> > work. 
> 
> No just patch those that would benefit from it. The existing 

This would be "all devices that SGI ships on Altixes" ?

IMHO all can benefit.

-Andi

  reply	other threads:[~2005-07-07  0:17 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 [this message]
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
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=20050706181349.GN21330@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