public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dobson <colpatch@us.ibm.com>
To: Michael Hohnbaum <hohnbaum@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 15:55:15 -0800	[thread overview]
Message-ID: <3DBF1FE3.2050804@us.ibm.com> (raw)
In-Reply-To: 1035930929.1274.1766.camel@dyn9-47-17-164.beaverton.ibm.com

Michael Hohnbaum wrote:
> On Tue, 2002-10-29 at 14:19, Matthew Dobson wrote:
> 
>>Erich Focht 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)
>>
>>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.
> 
> I'm using this in the simple NUMA scheduler.  This is quite useful
> for iterating through a specific node's CPUs.  Yes, the functionality
> can be obtained in a different manner, but is less obvious.

Hmmm...  This is true, but I'd like to keep the topology functions as 
minimal as possible.  Since the functionality is so easily duplicated, 
and in almost every arch, is implemented almost identically, it seems a 
waste.  In most architectures, they itterate across cpus, either 
returning the first one on the node, or adding each to a mask and 
returning that.

Besides, it's not gone yet... ;)

Cheers!

-Matt


  reply	other threads:[~2002-10-29 23:53 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 [this message]
2002-10-29 22:47       ` William Lee Irwin III
2002-10-30  0:01         ` Matthew Dobson
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=3DBF1FE3.2050804@us.ibm.com \
    --to=colpatch@us.ibm.com \
    --cc=davidm@hpl.hp.com \
    --cc=efocht@ess.nec.de \
    --cc=hohnbaum@us.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox