From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] avoid creating empty nodes [0/2]
Date: Thu, 30 Mar 2006 01:38:16 +0000 [thread overview]
Message-ID: <20060330013816.GA25530@sgi.com> (raw)
In-Reply-To: <20060329110903.d7bae796.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Mar 30, 2006 at 08:31:02AM +0900, KAMEZAWA Hiroyuki wrote:
> On Wed, 29 Mar 2006 08:37:34 -0600
> Jack Steiner <steiner@sgi.com> wrote:
> > ACPI3.0 will have a way to describe these IO nodes. We have not done the
> > design but when ACPI3.0 is available, we intend to make the kernel fully
> > aware of IO-only nodes.
> >
>
> Then, we should set I/O nodes's pxm to pxm_online_map (I added in patch) in
> acpi_numa_arch_fixup() in addition to cpus and memory. But there are no codes
> to find available I/O nodes now.
> Correct ?
Correct for ACPI2.0. ACPI3.0 has the PXM for IO buses (at least I think it was
at the bus level - I don't have the spec right now) in one of the IO tables.
>
> BTW I heared ACPI3.0 can define pxm > 256. If we support it, entire codes should
> be rewrote ;(.
Yes. IIRC, PXM is a 32-bits in some tables, 24-bits in other tables.
>
> -- Kame
---
Jack
prev parent reply other threads:[~2006-03-30 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 2:09 [RFC][PATCH] avoid creating empty nodes [0/2] KAMEZAWA Hiroyuki
2006-03-29 2:11 ` [RFC][PATCH] avoid creating empty nodes [1/2] move reserve memory KAMEZAWA Hiroyuki
2006-03-29 2:12 ` [RFC][PATCH] avoid creating empty nodes [2/2] ignore empty pxms KAMEZAWA Hiroyuki
2006-03-29 14:37 ` [RFC][PATCH] avoid creating empty nodes [0/2] Jack Steiner
2006-03-29 23:31 ` KAMEZAWA Hiroyuki
2006-03-30 1:38 ` Jack Steiner [this message]
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=20060330013816.GA25530@sgi.com \
--to=steiner@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