From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: glauber@gmx.de
Cc: Linux Arch list <linux-arch@vger.kernel.org>, schwidefsky@de.ibm.com
Subject: Re: [Patch] SMP call function cleanup
Date: Fri, 23 Apr 2004 10:04:08 +1000 [thread overview]
Message-ID: <1082678647.22367.126.camel@gaston> (raw)
In-Reply-To: <1082636511.1332.34.camel@halo>
> there are 3 different kinds of SMP calls:
> 1. all CPUs
> 2. all CPUs but my own
> 3. one CPU
>
> only _one_ basic function is needed to implement all variants:
Well, I'd go further and allow an arbitraty cpu_mask. There are
cases where that could be an interesting optimisation to be able
to send an IPI to a "set" of CPUs. If the HW can't do it easily,
just send on all and software mask who gets the actual function
call.
Ben.
next prev parent reply other threads:[~2004-04-23 0:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 12:21 [Patch] SMP call function cleanup Jan Glauber
2004-04-22 12:28 ` William Lee Irwin III
2004-04-22 12:37 ` Anton Blanchard
2004-04-22 12:49 ` William Lee Irwin III
2004-04-22 12:59 ` James Bottomley
2004-04-22 13:24 ` William Lee Irwin III
2004-04-22 13:46 ` James Bottomley
2004-04-22 14:06 ` William Lee Irwin III
[not found] ` <1082641822.1329.45.camel@halo>
[not found] ` <1082642332.1778.39.camel@mulgrave>
2004-04-22 14:15 ` Jan Glauber
2004-04-23 0:05 ` Benjamin Herrenschmidt
2004-04-23 0:21 ` Anton Blanchard
2004-04-23 0:32 ` Benjamin Herrenschmidt
2004-04-22 13:58 ` Jan Glauber
2004-04-22 12:33 ` Anton Blanchard
2004-04-22 14:00 ` Jan Glauber
2004-04-22 14:13 ` William Lee Irwin III
2004-04-23 0:04 ` Benjamin Herrenschmidt [this message]
2004-04-23 23:38 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2004-04-23 6:46 Martin Schwidefsky
2004-04-23 6:53 Martin Schwidefsky
2004-04-23 7:05 ` Anton Blanchard
2004-04-23 9:00 ` Russell King
2004-04-23 7:46 Martin Schwidefsky
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=1082678647.22367.126.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=glauber@gmx.de \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.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