From: Matthew Dobson <colpatch@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
Jesse Barnes <jbarnes@sgi.com>,
LKML <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
LSE Tech <lse-tech@lists.sourceforge.net>
Subject: Re: [RFC][PATCH] Change pcibus_to_cpumask() to pcibus_to_node()
Date: Tue, 27 Jul 2004 11:18:04 -0700 [thread overview]
Message-ID: <1090952283.18747.3.camel@arrakis> (raw)
In-Reply-To: <20040727175713.10a95ad6.ak@suse.de>
On Tue, 2004-07-27 at 08:57, Andi Kleen wrote:
> On Tue, 27 Jul 2004 08:15:39 -0700
> Jesse Barnes <jbarnes@engr.sgi.com> wrote:
>
> > On Tuesday, July 27, 2004 7:16 am, Andi Kleen wrote:
> > > On Mon, 26 Jul 2004 17:10:08 -0700
> > >
> > > Matthew Dobson <colpatch@us.ibm.com> wrote:
> > > > So in discussions with Jesse at OLS, we decided that pcibus_to_node() is
> > > > a more generally useful function than pcibus_to_cpumask(). If anyone
> > > > disagrees with that, now would be a good time to let us know.
> > >
> > > Not sure that is a good idea. Sometimes this information is not available.
> > > With pcibus_to_cpumask() the fallback is obvious, but it isn't with
> > > pcibus_to_node(). Returning a random node is wrong.
> >
> > Hmm... so there's no way for you to get a node or nodemask at all?
>
> When the BIOS has _PXM methods there will be probably.
> Just I cannot guarantee it has that, so there should be some clean fallback path.
>
> If cpumask is too complicated for you a pcibus_to_nodemask would be fine
> for me too, just please no single node number.
>
>
> -Andi
I guess I'm OK with a nodemask instead of a node. That will make this
patch dependent on my nodemask_t patch, which I'll also be sending out
again later today, though... A nodemask instead of a node also allows
us to return a mask of nearby memory-only nodes as well as CPU-only
nodes, if the arch supports that, for allocating buffers/doing DMA
from...
-Matt
next prev parent reply other threads:[~2004-07-27 18:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 0:10 [RFC][PATCH] Change pcibus_to_cpumask() to pcibus_to_node() Matthew Dobson
2004-07-27 3:38 ` Jesse Barnes
2004-07-27 9:51 ` [Lse-tech] " Christoph Hellwig
2004-07-27 15:22 ` Jesse Barnes
2004-07-27 18:32 ` Matthew Dobson
2004-07-27 18:40 ` Jesse Barnes
2004-07-29 0:06 ` Matthew Dobson
2004-07-29 15:43 ` Jesse Barnes
2004-07-29 22:23 ` Matthew Dobson
2004-07-30 15:36 ` Jesse Barnes
2004-07-30 22:17 ` Matthew Dobson
2004-07-30 22:21 ` Jesse Barnes
2004-07-30 22:33 ` Matthew Dobson
2004-07-29 17:02 ` Rajesh Shah
2004-07-29 22:27 ` Matthew Dobson
2004-07-30 0:02 ` Rajesh Shah
2004-07-28 15:01 ` Martin J. Bligh
2004-07-28 19:10 ` Matthew Dobson
2004-07-27 14:16 ` Andi Kleen
2004-07-27 15:15 ` Jesse Barnes
2004-07-27 15:57 ` Andi Kleen
2004-07-27 18:18 ` Matthew Dobson [this message]
2004-07-29 8:34 ` Paul Jackson
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=1090952283.18747.3.camel@arrakis \
--to=colpatch@us.ibm.com \
--cc=ak@suse.de \
--cc=jbarnes@engr.sgi.com \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
/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