From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: linux-kernel@vger.kernel.org
Cc: discuss@x86-64.org
Subject: pcibus_to_node value when no pxm info is present for the pci bus
Date: Wed, 7 Dec 2005 14:34:14 -0800 [thread overview]
Message-ID: <20051207223414.GA4493@localhost.localdomain> (raw)
Most of the arches seem to return -1 for pcibus_to_node if there is no pxm
kind of proximity information for the pci busses. Arch specific code on
those arches check if nodeid >= 0 before using the nodeid for kmalloc_node
etc. But some code paths in x86_64/i386 does not doe this --
x86_64/dma_alloc_pages() and e1000 node local descriptor (I am to blame for
the second one). Also, pcibus_to_node seems to be 0 when there is no pxm
info available.
The question is, what should be the default pcibus_to_node if there is no
pxm info? Answer seems like -1 -- in which case dma_alloc_pages and e1000
driver has to be fixed.
Thanks,
Kiran
next reply other threads:[~2005-12-07 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 22:34 Ravikiran G Thirumalai [this message]
2005-12-08 19:05 ` pcibus_to_node value when no pxm info is present for the pci bus Christoph Lameter
2005-12-08 19:34 ` Ravikiran G Thirumalai
2005-12-08 20:04 ` [discuss] " Andi Kleen
2005-12-08 20:21 ` Ravikiran G Thirumalai
2005-12-08 20:26 ` Andi Kleen
2005-12-08 20:41 ` Christoph Lameter
2005-12-08 20:47 ` 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=20051207223414.GA4493@localhost.localdomain \
--to=kiran@scalex86.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@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