linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Christoph Hellwig <hch@lst.de>, Dave Jones <davej@redhat.com>,
	David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-mm@kvack.org,
	"Benzi Galili (Benzi@ScaleMP.com)" <benzi@scalemp.com>,
	"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>
Subject: Re: [PATCH 2/3] add dev_to_node()
Date: Tue, 7 Nov 2006 11:15:31 +0100	[thread overview]
Message-ID: <20061107101531.GB28970@lst.de> (raw)
In-Reply-To: <20061107062536.GA3729@localhost.localdomain>

On Mon, Nov 06, 2006 at 10:25:36PM -0800, Ravikiran G Thirumalai wrote:
> On Sun, Nov 05, 2006 at 12:53:23AM +0100, Christoph Hellwig wrote:
> > On Sat, Nov 04, 2006 at 06:06:48PM -0500, Dave Jones wrote:
> > > On Sat, Nov 04, 2006 at 11:56:29PM +0100, Christoph Hellwig wrote:
> > > 
> > > This will break the compile for !NUMA if someone ends up doing a bisect
> > > and lands here as a bisect point.
> > > 
> > > You introduce this nice wrapper..
> > 
> > The dev_to_node wrapper is not enough as we can't assign to (-1) for
> > the non-NUMA case.  So I added a second macro, set_dev_node for that.
> > 
> > The patch below compiles and works on numa and non-NUMA platforms.
> > 
> > 
> 
> Hi Christoph,
> dev_to_node does not work as expected on x86_64 (and i386).  This is because
> node value returned by pcibus_to_node is initialized after a struct device
> is created with current x86_64 code.
> 
> We need the node value initialized before the call to pci_scan_bus_parented,
> as the generic devices are allocated and initialized
> off pci_scan_child_bus, which gets called from pci_scan_bus_parented
> The following patch does that using "pci_sysdata" introduced by the PCI
> domain patches in -mm.

A nice, that some non-cell folks actually care for this patch.  As far
as my x86_64 pci code knowledge is concerned that patch look fine to me.

--
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>

  reply	other threads:[~2006-11-07 10:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 14:15 Christoph Hellwig
2006-10-30 22:33 ` David Miller, Christoph Hellwig
2006-11-01  0:10   ` Christoph Lameter
2006-11-01  0:53     ` David Miller, Christoph Lameter
2006-11-01  1:58       ` Christoph Lameter
2006-11-04 22:56   ` Christoph Hellwig
2006-11-04 23:06     ` Dave Jones
2006-11-04 23:09       ` Christoph Hellwig
2006-11-04 23:53       ` Christoph Hellwig
2006-11-05  8:22         ` David Miller, Christoph Hellwig
2006-11-06 23:39           ` Christoph Hellwig
2006-11-07  6:25         ` Ravikiran G Thirumalai
2006-11-07 10:15           ` Christoph Hellwig [this message]
2006-11-08  2:40     ` KAMEZAWA Hiroyuki
2006-11-10 18:16       ` Christoph Lameter
2006-11-10 18:28         ` Lee Schermerhorn
2006-11-11  0:08           ` KAMEZAWA Hiroyuki

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=20061107101531.GB28970@lst.de \
    --to=hch@lst.de \
    --cc=benzi@scalemp.com \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=shai@scalex86.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