From: Bart Van Assche <bvanassche@acm.org>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
lf-virt <virtualization@lists.linux-foundation.org>,
kvm-devel <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Zhi Yong Wu <wuzhy@cn.ibm.com>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 0/6] tcm_vhost/virtio-scsi WIP code for-3.6
Date: Thu, 05 Jul 2012 17:53:24 +0000 [thread overview]
Message-ID: <4FF5D494.2090707@acm.org> (raw)
In-Reply-To: <1341453135.23954.214.camel@haakon2.linux-iscsi.org>
On 07/05/12 01:52, Nicholas A. Bellinger wrote:
> fio randrw workload | virtio-scsi-raw | virtio-scsi+tcm_vhost | bare-metal raw block
> ------------------------------------------------------------------------------------
> 25 Write / 75 Read | ~15K | ~45K | ~70K
> 75 Write / 25 Read | ~20K | ~55K | ~60K
These numbers are interesting. To me these numbers mean that there is a
huge performance bottleneck in the virtio-scsi-raw storage path. Why is
the virtio-scsi-raw bandwidth only one third of the bare-metal raw block
bandwidth ?
Bart.
next prev parent reply other threads:[~2012-07-05 17:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 4:24 [PATCH 0/6] tcm_vhost/virtio-scsi WIP code for-3.6 Nicholas A. Bellinger
2012-07-04 4:24 ` [PATCH 1/6] vhost: Separate vhost-net features from vhost features Nicholas A. Bellinger
2012-07-04 4:41 ` Asias He
2012-07-04 4:24 ` [PATCH 2/6] vhost: make vhost work queue visible Nicholas A. Bellinger
2012-07-04 4:24 ` [PATCH 3/6] vhost: Add vhost_scsi specific defines Nicholas A. Bellinger
2012-07-04 4:24 ` [PATCH 4/6] tcm_vhost: Initial merge for vhost level target fabric driver Nicholas A. Bellinger
2012-07-05 17:47 ` Bart Van Assche
2012-07-05 17:59 ` Bart Van Assche
2012-07-04 4:24 ` [PATCH 5/6] virtio-scsi: Add vdrv->scan for post VIRTIO_CONFIG_S_DRIVER_OK LUN scanning Nicholas A. Bellinger
2012-07-04 14:50 ` Paolo Bonzini
2012-07-04 4:24 ` [PATCH 6/6] virtio-scsi: Set shost->max_id=1 for tcm_vhost WWPNs Nicholas A. Bellinger
2012-07-04 14:50 ` Paolo Bonzini
2012-07-05 2:05 ` Nicholas A. Bellinger
2012-07-05 6:42 ` Paolo Bonzini
2012-07-04 14:02 ` [PATCH 0/6] tcm_vhost/virtio-scsi WIP code for-3.6 Michael S. Tsirkin
2012-07-04 14:52 ` Paolo Bonzini
2012-07-04 15:05 ` Michael S. Tsirkin
2012-07-04 22:12 ` Anthony Liguori
2012-07-05 1:52 ` Nicholas A. Bellinger
2012-07-05 10:22 ` Paolo Bonzini
2012-07-05 13:53 ` Michael S. Tsirkin
2012-07-05 14:06 ` Anthony Liguori
2012-07-05 14:40 ` Michael S. Tsirkin
2012-07-05 14:47 ` Paolo Bonzini
2012-07-05 17:26 ` Michael S. Tsirkin
2012-07-06 3:01 ` Nicholas A. Bellinger
2012-07-06 5:43 ` SCSI Performance regression [was Re: [PATCH 0/6] tcm_vhost/virtio-scsi WIP code for-3.6] James Bottomley
2012-07-06 9:13 ` Nicholas A. Bellinger
2012-07-06 13:49 ` James Bottomley
2012-07-06 18:21 ` Nicholas A. Bellinger
2012-07-06 20:30 ` [Ksummit-2012-discuss] " Christoph Lameter
2012-07-06 22:06 ` Nicholas A. Bellinger
2012-07-05 14:32 ` [PATCH 0/6] tcm_vhost/virtio-scsi WIP code for-3.6 Paolo Bonzini
2012-07-05 21:00 ` Michael S. Tsirkin
2012-07-06 3:38 ` Nicholas A. Bellinger
2012-07-06 5:39 ` Paolo Bonzini
2012-07-05 17:53 ` Bart Van Assche [this message]
2012-07-05 19:57 ` Bart Van Assche
2012-07-10 0:29 ` Nicholas A. Bellinger
2012-07-05 2:01 ` Nicholas A. Bellinger
2012-07-05 9:31 ` Michael S. Tsirkin
2012-07-06 3:13 ` Nicholas A. Bellinger
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=4FF5D494.2090707@acm.org \
--to=bvanassche@acm.org \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@linux.vnet.ibm.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wuzhy@cn.ibm.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).