From: Andrea Arcangeli <andrea@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Rik van Riel <riel@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Theurer <habanero@us.ibm.com>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Linux 2.4.19-rc3 (hyperthreading)
Date: Tue, 30 Jul 2002 02:32:48 +0200 [thread overview]
Message-ID: <20020730003248.GP1201@dualathlon.random> (raw)
In-Reply-To: <20020730000912.GA6406@714-cm.cps.unizar.es>
On Tue, Jul 30, 2002 at 02:09:12AM +0200, J.A. Magallon wrote:
> How about this version (gcc-3.2 generates the same amount of assembler):
>
> int find(int this_cpu)
> {
> int i;
>
> for ( i = (this_cpu+1)%smp_num_cpus;
> i != this_cpu;
> i = (i+1)%smp_num_cpus )
> {
> int physical = cpu_logical_map(i);
> int sibling = cpu_sibling_map[physical];
>
> if (idle_cpu(physical) && idle_cpu(sibling))
> return physical;
> }
> return -1;
> }
I also find the above a bit more readable, I'll rediff once more time
then.
Andrea
next prev parent reply other threads:[~2002-07-30 0:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 19:54 Linux 2.4.19-rc3 (hyperthreading) Andrew Theurer
2002-07-29 21:28 ` Alan Cox
2002-07-29 20:38 ` Andrea Arcangeli
2002-07-29 23:45 ` Andrea Arcangeli
2002-07-29 23:51 ` Rik van Riel
2002-07-30 0:04 ` Andrea Arcangeli
2002-07-30 0:09 ` J.A. Magallon
2002-07-30 0:32 ` Andrea Arcangeli [this message]
2002-07-31 3:08 ` Bill Davidsen
2002-07-31 12:43 ` Rik van Riel
2002-07-31 14:16 ` Sam Vilain
2002-08-01 18:29 ` Ingo Oeser
2002-07-29 20:58 ` Andrew Theurer
2002-07-30 0:37 ` Alan Cox
2002-07-29 23:42 ` Andrew Theurer
2002-07-30 0:56 ` James Bourne
2002-07-30 0:47 ` James Bourne
2002-07-30 1:15 ` Andrew Theurer
2002-07-30 3:09 ` James Bourne
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=20020730003248.GP1201@dualathlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=habanero@us.ibm.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).