From: Jesse Barnes <jesse.barnes@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] pcibus_to_node implementation for ia64
Date: Wed, 11 May 2005 15:58:26 +0000 [thread overview]
Message-ID: <200505110858.26342.jesse.barnes@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505051707220.6114@schroedinger.engr.sgi.com>
On Wednesday, May 11, 2005 8:49 am, you wrote:
> On Wed, 11 May 2005, colin ngam wrote:
> > >That's certainly another way to go--just make the function do a
> > > search to find the closest node with memory (and/or CPUs) all by
> > > itself. The obvious disadvantage is that you'll incur that cost
> > > on every function call unless you build a lookup table at boot
> > > time or somesuch.
>
> This search is performed by alloc_pages using the zonelists.
Not right now it isn't. In the snippet you posted you might get back a
special node id, one that corresponds to an I/O node, which doesn't
have a pgdat associated with it, and therefore won't work when passed
to alloc_pages_node (I think it'll panic).
> How do I get a node that I can pass to alloc_pages_node?
Fix the sn2 implementation of I/O nodes to make them more like regular
nodes. Basically,
o put them in the SLIT and SRAT tables
o make sure empty pgdats are created for memoryless nodes (in
discontig.c), ideally on the closest node containing memory.
The first step isn't strictly necessary since you could fake it (you'd
probably have to pull some code from io_init.c out and make it usable
at early boot), but is probably preferable to putting together an ugly
hack.
Jesse
next prev parent reply other threads:[~2005-05-11 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 0:12 [RFC] pcibus_to_node implementation for ia64 Christoph Lameter
2005-05-10 23:56 ` colin ngam
2005-05-11 1:34 ` Christoph Lameter
2005-05-11 2:42 ` colin ngam
2005-05-11 6:51 ` Christoph Lameter
2005-05-11 15:29 ` Jesse Barnes
2005-05-11 15:44 ` colin ngam
2005-05-11 15:49 ` Christoph Lameter
2005-05-11 15:52 ` colin ngam
2005-05-11 15:54 ` Jesse Barnes
2005-05-11 15:58 ` Jesse Barnes [this message]
2005-05-11 16:05 ` colin ngam
2005-05-11 16:19 ` Jack Steiner
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=200505110858.26342.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--cc=linux-ia64@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