From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Andi Kleen <andi@firstfloor.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86: implement multiple queues for smp function call IPIs
Date: Tue, 29 Jul 2008 16:43:59 -0700 [thread overview]
Message-ID: <488FAB3F.6050003@goop.org> (raw)
In-Reply-To: <488FA8A9.6000005@goop.org>
Jeremy Fitzhardinge wrote:
> This adds 8 queues for smp_call_function(), in order to avoid a
> bottleneck on a single global lock and list for function calls. When
> initiating a function call, the sender chooses a queue based on its
> own processor id (if there are more than 8 processors, they hash down
> to 8 queues). It then sends an IPI to the corresponding vector for
> that queue to each target CPU. The target CPUs use the vector number
> to determine which queue they should scan for work.
I should point out that this patch depends on the earlier tlb.c
unification patch, since it recycles the IPI vectors that series freed up.
J
next prev parent reply other threads:[~2008-07-29 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 23:32 [PATCH 2/2] x86: implement multiple queues for smp function call IPIs Jeremy Fitzhardinge
2008-07-29 23:43 ` Jeremy Fitzhardinge [this message]
2008-07-30 0:13 ` Andi Kleen
2008-07-30 0:44 ` Jeremy Fitzhardinge
2008-07-30 4:55 ` Nick Piggin
2008-07-31 22:08 ` Ingo Molnar
2008-07-31 22:12 ` Andi Kleen
2008-07-31 22:23 ` Jeremy Fitzhardinge
2008-07-31 22:42 ` Ingo Molnar
2008-08-01 4:58 ` Jeremy Fitzhardinge
2008-08-01 9:09 ` Ingo Molnar
2008-08-01 14:17 ` Andi Kleen
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=488FAB3F.6050003@goop.org \
--to=jeremy@goop.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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.