From: Andi Kleen <ak@suse.de>
To: Nick Piggin <npiggin@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [rfc][patch] x86-64 new smp_call_function design
Date: Wed, 27 Feb 2008 14:04:18 +0100 [thread overview]
Message-ID: <47C55FD2.8030809@suse.de> (raw)
In-Reply-To: <20080227124217.GA1340@wotan.suse.de>
> On a 2 socket, 8 core system, I see anywhere up to nearly 16x better
> performance on a stress test. The common cases of call-all, and wait
> are improved the least, however I think that if call-single and nowait
> are turned into a high performance API, then new usages will pop up
> (eg. I started this because I wanted to do "call single, nowait" calls
> for migrating block IO completions back to submitting CPU; however I
> am also interested in improving the "call all, wait" case for example
> to improve vmalloc tlb flushing).
TLB flushing at least on x86-64 should be already well optimized on its
own. I would be surprised if you could do much better.
> As far as I understand, calling a subset of online CPUs that is not all or
> one, is used quite infrequently, so this might be OK.
With cpusets and isolation etc. it is the normal case.
-Andi
next prev parent reply other threads:[~2008-02-27 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 12:42 [rfc][patch] x86-64 new smp_call_function design Nick Piggin
2008-02-27 13:04 ` Andi Kleen [this message]
2008-02-27 13:07 ` Nick Piggin
2008-02-27 13:33 ` Andi Kleen
[not found] ` <47C5668C.6040906-l3A5Bk7waGM@public.gmane.org>
2008-03-16 14:33 ` Avi Kivity
2008-03-16 14:33 ` Avi Kivity
2008-02-27 13:27 ` Ingo Molnar
2008-02-27 13:50 ` Nick Piggin
2008-02-27 15:02 ` Ingo Molnar
2008-02-27 22:14 ` Nick Piggin
2008-02-28 8:45 ` Ingo Molnar
2008-02-28 12:55 ` 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=47C55FD2.8030809@suse.de \
--to=ak@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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.