From: Matthew Dobson <colpatch@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Erich Focht <efocht@ess.nec.de>,
davidm@hpl.hp.com, linux-ia64 <linux-ia64@linuxia64.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-ia64] Re: [PATCH] topology for ia64
Date: Tue, 29 Oct 2002 16:01:02 -0800 [thread overview]
Message-ID: <3DBF213E.5090902@us.ibm.com> (raw)
In-Reply-To: 20021029224725.GH23425@holomorphy.com
William Lee Irwin III wrote:
> On Tue, Oct 29, 2002 at 02:19:25PM -0800, Matthew Dobson wrote:
> +/*
> + * Returns the number of the first CPU on Node 'node'.
> + * Slow in the current implementation.
> + * Who needs this?
> + */
> +/* #define __node_to_first_cpu(node) pool_cpus[pool_ptr[node]] */
> +static inline int __node_to_first_cpu(int node)
>
> So far so safe... though no obvious use of it.
Yep...
> On Tue, Oct 29, 2002 at 02:19:25PM -0800, Matthew Dobson wrote:
>
>>No one is using it now. I think that I will probably deprecate this
>>function in the near future as it is pretty useless. Anyone looking for
>>that functionality can just do an __ffs(__node_to_cpu_mask(node))
>>instead, and hope that there is a reasonably quick implementation of
>>__node_to_cpu_mask.
>
>
> This assumes the value returned by __node_to_cpu_mask() is a single word.
Which is the case right now. When (not if) that changes, we'll come up
with more flexible ffs macros, or a better way to count variable length
bitmasks... especially as there will be a TON of them.
Cheers!
-Matt
next prev parent reply other threads:[~2002-10-29 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 17:04 [PATCH] topology for ia64 Erich Focht
2002-10-22 0:07 ` David Mosberger
2002-10-22 9:23 ` Erich Focht
2002-10-29 22:19 ` Matthew Dobson
2002-10-29 22:35 ` [Linux-ia64] " Michael Hohnbaum
2002-10-29 23:55 ` Matthew Dobson
2002-10-29 22:47 ` William Lee Irwin III
2002-10-30 0:01 ` Matthew Dobson [this message]
2002-10-29 23:43 ` Erich Focht
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=3DBF213E.5090902@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=davidm@hpl.hp.com \
--cc=efocht@ess.nec.de \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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