From: Nick Piggin <npiggin@suse.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
"Alan D. Brunelle" <Alan.Brunelle@hp.com>,
linux-kernel@vger.kernel.org, dgc@sgi.com, arjan@linux.intel.com
Subject: Re: IO queueing and complete affinity w/ threads: Some results
Date: Tue, 19 Feb 2008 02:49:12 +0100 [thread overview]
Message-ID: <20080219014911.GD21165@wotan.suse.de> (raw)
In-Reply-To: <p73ablyxuci.fsf@bingen.suse.de>
On Mon, Feb 18, 2008 at 02:33:17PM +0100, Andi Kleen wrote:
> Jens Axboe <jens.axboe@oracle.com> writes:
>
> > and that scrapping the remote
> > softirq trigger stuff is sanest.
>
> I actually liked Nick's queued smp_function_call_single() patch. So even
> if it was not used for block I would still like to see it being merged
> in some form to speed up all the other IPI users.
Yeah, that hasn't been forgotten (nor have your comments about folding
my special function into smp_call_function_single).
The call function path is terribly unscalable at the moment on a lot
of architectures, and also it isn't allowed to be used with interrupts
off due to deadlock (which the queued version can allow, provided
that wait=0).
I will get around to sending that upstream soon.
next prev parent reply other threads:[~2008-02-19 1:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 20:56 IO queueing and complete affinity w/ threads: Some results Alan D. Brunelle
2008-02-12 20:56 ` Alan D. Brunelle
2008-02-12 22:08 ` Alan D. Brunelle
2008-02-12 22:26 ` Alan D. Brunelle
2008-02-13 15:35 ` Alan D. Brunelle
2008-02-14 15:36 ` Alan D. Brunelle
2008-02-18 12:37 ` Jens Axboe
2008-02-18 13:33 ` Andi Kleen
2008-02-18 14:16 ` Jens Axboe
2008-02-19 1:49 ` Nick Piggin [this message]
2008-02-19 21:14 ` Paul Jackson
2008-02-19 21:31 ` Mike Travis
2008-02-20 8:08 ` Jens Axboe
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=20080219014911.GD21165@wotan.suse.de \
--to=npiggin@suse.de \
--cc=Alan.Brunelle@hp.com \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=dgc@sgi.com \
--cc=jens.axboe@oracle.com \
--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 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.