public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: interrupt locality for NUMA
Date: Fri, 13 Aug 2004 15:32:03 +0000	[thread overview]
Message-ID: <200408130832.03760.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1092365888.6434.25.camel@localhost.localdomain>

On Thursday, August 12, 2004 7:58 pm, Alex Williamson wrote:
>    This probably isn't ready for inclusion yet, but I wanted to see if
> anybody else could make use of it.  This works on HP sx1000 boxes setup
> for NUMA and I think it's ACPI namespace does the right thing.  All this
> does is walk through namespace looking for devices with an _MAT method
> that returns an IOSAPIC and also has a _PXM method to tell us the
> proximity domain where it lives.  The node data gets stored in the
> iosapic data structure because doing this lookup is pretty slow.  Does
> this jive with what other ACPI NUMA boxes are exporting in namespace?
> I'm hoping everyone will put the _PXM on the same device as the _MAT,
> but I'm wondering if I need to add support for looking on parent
> objects.  Thoughts?  Thanks,

Matt Dobson is working on a pci_to_nodemask, might that be used instead?  If 
we did it that way, we could put it in generic code, dependent on CONFIG_NUMA 
or something, rather than keeping it ACPI specific.

Jesse

  reply	other threads:[~2004-08-13 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13  2:58 interrupt locality for NUMA Alex Williamson
2004-08-13 15:32 ` Jesse Barnes [this message]
2004-08-13 15:41 ` Alex Williamson
2004-08-13 15:50 ` Jesse Barnes

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=200408130832.03760.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.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