From: Asias He <asias@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Tejun Heo <tj@kernel.org>, Shaohua Li <shli@kernel.org>
Subject: Re: [PATCH V6 0/2] Improve virtio-blk performance
Date: Wed, 08 Aug 2012 14:24:22 +0800 [thread overview]
Message-ID: <50220616.6060508@redhat.com> (raw)
In-Reply-To: <5021D87C.4050400@redhat.com>
On 08/08/2012 11:09 AM, Asias He wrote:
> On 08/07/2012 05:16 PM, Christoph Hellwig wrote:
>> On Tue, Aug 07, 2012 at 04:47:13PM +0800, Asias He wrote:
>>> 1) Ramdisk device
>>> With bio-based IO path, sequential read/write, random read/write
>>> IOPS boost : 28%, 24%, 21%, 16%
>>> Latency improvement: 32%, 17%, 21%, 16%
>>> 2) Fusion IO device
>>> With bio-based IO path, sequential read/write, random read/write
>>> IOPS boost : 11%, 11%, 13%, 10%
>>> Latency improvement: 10%, 10%, 12%, 10%
>>
>> Do you also have numbers for normal SAS/SATA disks? The changelog should
>> have a reall good explanation of why this is optional, and numbers are a
>> very important part of that.
Yes. I posted the numbers on normal SATA disks a few days ago in the
thread with Sasha. Will add that data and explanation of why optional to
the changelog
--
Asias
prev parent reply other threads:[~2012-08-08 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 8:47 [PATCH V6 0/2] Improve virtio-blk performance Asias He
2012-08-07 8:47 ` [PATCH V6 1/2] virtio-blk: Add bio-based IO path for virtio-blk Asias He
2012-08-07 8:47 ` [PATCH V6 2/2] virtio-blk: Add REQ_FLUSH and REQ_FUA support to bio path Asias He
2012-08-07 9:15 ` Christoph Hellwig
2012-08-08 6:20 ` Asias He
2012-08-07 9:16 ` [PATCH V6 0/2] Improve virtio-blk performance Christoph Hellwig
[not found] ` <5021D87C.4050400@redhat.com>
2012-08-08 6:24 ` Asias He [this message]
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=50220616.6060508@redhat.com \
--to=asias@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=shli@kernel.org \
--cc=tj@kernel.org \
--cc=virtualization@lists.linux-foundation.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 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).