From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix for-loop in sn_hwperf_geoid_to_cnode()
Date: Thu, 09 Mar 2006 17:57:09 +0000 [thread overview]
Message-ID: <200603091057.09980.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20060303150312.GA32225@sgi.com>
On Thursday 09 March 2006 09:12, Robin Holt wrote:
> On Wed, Mar 08, 2006 at 04:55:45PM -0700, Bjorn Helgaas wrote:
> > On Wednesday 08 March 2006 15:02, Dean Roe wrote:
> > > Are you saying you *really* want a for_each_sn_cnode() macro? I guess
> > > we can go that route if necessary...I just prefer the one-line change
> > > rather than changing 4-5 files when we aren't really sure yet what the
> > > final implementation will look like.
> >
> > I saw his response, but it wasn't clear to me what ACPI 3.0 is going
> > to solve. Are you saying that with ACPI 3.0, you will be able to
> > use for_each_node()?
>
> The node informatoin is stored in a single byte. With the introduction
> of I/O only nodes, we can easily exceed the 512 node limit placed on
> the byte size. ACPI 3.0 should raise that node limit to at least a
> 16-bit word.
I'm only trying to point out that you should be able to separate the
for_each_XXX() interface from the current ACPI limit.
> > If that's the case, my question is, why can't you use for_each_node()
> > today, and use some interim hack to fill in node_possible_map?
>
> The node field size does not allow for it.
Which node field doesn't allow it? for_each_node() uses the
node_possible_mask bitmap, which can be any size you need.
> > If not, what "for_each_XXX" macro are you planning to use when
> > you have ACPI 3.0?
>
> Not sure yet because ACPI 3.0 is still way off in the future. We
> will know more when that time comes.
If you think for_each_node() is the correct interface to use here,
just use it, and make node_possible_mask large enough. That means
you might need some glue code deal with the fact that ACPI 2.0
can't populate the whole thing, but that's not a problem.
If you think you need something other than for_each_node(), why
not just take a stab at defining the correct interface now, and
fix it later if you need to? I think that's better than putting
in something that you *know* will need to be changed later.
next prev parent reply other threads:[~2006-03-09 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 15:03 [PATCH] fix for-loop in sn_hwperf_geoid_to_cnode() Dean Roe
2006-03-03 17:01 ` Luck, Tony
2006-03-03 19:49 ` Jack Steiner
2006-03-03 21:52 ` Luck, Tony
2006-03-06 16:28 ` Dean Roe
2006-03-06 16:32 ` Dean Roe
2006-03-06 17:35 ` Bjorn Helgaas
2006-03-08 22:02 ` Dean Roe
2006-03-08 23:55 ` Bjorn Helgaas
2006-03-09 16:12 ` Robin Holt
2006-03-09 17:57 ` Bjorn Helgaas [this message]
2006-03-10 17:57 ` 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=200603091057.09980.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.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