From: Kent Overstreet <koverstreet@google.com>
To: john.wensley@gmail.com
Cc: fa.linux.kernel@googlegroups.com, linux-kernel@vger.kernel.org,
linux-aio@kvack.org, Zach Brown <zab@redhat.com>,
bcrl@kvack.org, jmoyer@redhat.com, axboe@kernel.dk,
viro@zeniv.linux.org.uk, tytso@mit.edu
Subject: Re: [PATCH 03/32] gadget: remove only user of aio retry
Date: Tue, 1 Jan 2013 11:15:06 -0800 [thread overview]
Message-ID: <20130101191506.GE10411@moria.home.lan> (raw)
In-Reply-To: <9d57e984-32bd-4d94-8137-6aeec4cf5986@googlegroups.com>
On Sat, Dec 29, 2012 at 12:19:10AM -0800, john.wensley@gmail.com wrote:
> On Thursday, December 27, 2012 4:08:46 AM UTC+2, Kent Overstreet wrote:
> ...
>
> Great. Did you measure by how much your changes improve performance?
This particular patch? No. As for the whole series, Jens has done the
best actual benchmarks; mostly I've just been looking at profiles - I
don't have any high end hardware with drivers suitable for that kind of
benchmarking, myself.
Also, my changes have been particularly aimed at improving the situation
where an ioctx is shared between different threads; we don't have any
actual benchmarks for how much that's improved as fio doesn't do that
but the gains there are going to be much more significant, for
applications where that's useful.
next prev parent reply other threads:[~2013-01-01 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.bKjJDjpiXe4ZyttQxy70URjcaYU@ifi.uio.no>
[not found] ` <fa.aKiGvXaqF8zkt42DoAyNZWYEe5M@ifi.uio.no>
2012-12-29 8:19 ` [PATCH 03/32] gadget: remove only user of aio retry john.wensley
2013-01-01 19:15 ` Kent Overstreet [this message]
2012-12-27 1:59 [PATCH 00/32] AIO performance improvements/cleanups, v3 Kent Overstreet
2012-12-27 1:59 ` [PATCH 03/32] gadget: remove only user of aio retry Kent Overstreet
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=20130101191506.GE10411@moria.home.lan \
--to=koverstreet@google.com \
--cc=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=fa.linux.kernel@googlegroups.com \
--cc=jmoyer@redhat.com \
--cc=john.wensley@gmail.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=zab@redhat.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;
as well as URLs for NNTP newsgroup(s).