From: William Lee Irwin III <wli@holomorphy.com>
To: Matthew Dobson <colpatch@us.ibm.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 14:47:25 -0800 [thread overview]
Message-ID: <20021029224725.GH23425@holomorphy.com> (raw)
In-Reply-To: <3DBF096D.6080703@us.ibm.com>
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.
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.
Bill
next prev parent reply other threads:[~2002-10-29 22:41 UTC|newest]
Thread overview: 16+ 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 [this message]
2002-10-30 0:01 ` Matthew Dobson
2002-10-29 23:43 ` Erich Focht
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 0:07 [Linux-ia64] " David Mosberger
2002-10-22 9:23 ` Erich Focht
2002-10-29 22:19 ` Matthew Dobson
2002-10-29 22:35 ` Michael Hohnbaum
2002-10-29 23:43 ` Erich Focht
2002-10-29 23:55 ` Matthew Dobson
2002-10-30 0:01 ` Matthew Dobson
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=20021029224725.GH23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.