From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, paulus@samba.org,
tglx@linutronix.de, mingo@redhat.com, tony.luck@intel.com,
Alan.Brunelle@hp.com
Subject: Re: [PATCH 0/5] Generic smp_call_function(), improvements, and smp_call_function_single()
Date: Thu, 27 Mar 2008 13:02:44 +0100 [thread overview]
Message-ID: <20080327120244.GL12346@kernel.dk> (raw)
In-Reply-To: <20080327104359.GC26725@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Thu, Mar 27 2008, Ingo Molnar wrote:
>
> * Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > I very much wanted the kthread approach to work, since it's easier to
> > work with. It's not for lack of will or trying... I'll be happy to
> > supply you otherwise identical patches for this, the only difference
> > being kthread of IPI completions if you want to play with this.
>
> i'd love to be able to run/pull something simple that enables me to
> replicate the measurements you did on a generic PC [without having to
> hit any real IO hardware which would put any context switching effects
> down into the noise category].
You can pull io-cpu-affinity or io-cpu-affinity-kthread from
git://git.kernel.dk/linux-2.6-block.git - or just see the two attached
patches, apply either one to current -git to test it.
> Obviously since the kthread approach embedds IPI sending it can never be
> as fast as a pure IPI approach - but it should still be reasonably fast.
> 3 usecs versus 2 usecs in a microbenchmark sounds about right to me, but
> it would be better to make it a better-sounding 2.5 usecs versus 2 usecs
> or so :-)
If you have ideas to speedup the kthread approach, fire away :-)
--
Jens Axboe
[-- Attachment #2: io-affinity-ipi.patch.bz2 --]
[-- Type: application/x-bzip, Size: 15107 bytes --]
[-- Attachment #3: io-affinity-kthread.patch.bz2 --]
[-- Type: application/x-bzip, Size: 6966 bytes --]
next prev parent reply other threads:[~2008-03-27 12:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 11:56 [PATCH 0/5] Generic smp_call_function(), improvements, and smp_call_function_single() Jens Axboe
2008-03-19 11:56 ` [PATCH 1/5] Add generic helpers for arch IPI function calls Jens Axboe
2008-03-19 11:56 ` [PATCH 2/5] x86: convert to generic helpers for " Jens Axboe
2008-03-19 11:56 ` [PATCH 3/5] x86-64: " Jens Axboe
2008-03-19 11:56 ` [PATCH 4/5] powerpc: " Jens Axboe
2008-03-19 11:56 ` [PATCH 5/5] ia64: " Jens Axboe
2008-03-21 9:53 ` [PATCH 0/5] Generic smp_call_function(), improvements, and smp_call_function_single() Ingo Molnar
2008-03-21 13:15 ` Jens Axboe
2008-03-25 8:00 ` Nick Piggin
2008-03-27 10:08 ` Ingo Molnar
2008-03-27 10:37 ` Jens Axboe
2008-03-27 10:43 ` Ingo Molnar
2008-03-27 12:02 ` Jens Axboe [this message]
2008-03-27 12:32 ` Ingo Molnar
2008-03-27 12:35 ` Jens Axboe
2008-03-21 18:22 ` Luck, Tony
2008-03-21 18:31 ` Jens Axboe
2008-03-21 18:56 ` Luck, Tony
2008-03-22 12:29 ` Jens Axboe
2008-03-24 16:45 ` Luck, Tony
2008-03-24 20:28 ` Luck, Tony
2008-03-25 8:12 ` Jens Axboe
2008-03-25 16:48 ` Luck, Tony
2008-03-25 18:00 ` Jens Axboe
2008-03-21 20:04 ` Luck, Tony
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=20080327120244.GL12346@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Alan.Brunelle@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=npiggin@suse.de \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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 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.