From: "Michael S. Tsirkin" <mst@redhat.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org
Subject: Re: [RFC] vhost-blk implementation
Date: Tue, 23 Mar 2010 14:39:16 +0200 [thread overview]
Message-ID: <20100323123916.GA24750@redhat.com> (raw)
In-Reply-To: <1269304444.7931.68.camel@badari-desktop>
On Mon, Mar 22, 2010 at 05:34:04PM -0700, Badari Pulavarty wrote:
> Write Results:
> ==============
>
> I see degraded IO performance when doing sequential IO write
> tests with vhost-blk compared to virtio-blk.
>
> # time dd of=/dev/vda if=/dev/zero bs=2M oflag=direct
>
> I get ~110MB/sec with virtio-blk, but I get only ~60MB/sec with
> vhost-blk. Wondering why ?
Try to look and number of interrupts and/or number of exits.
It could also be that you are overrunning some queue.
I don't see any exit mitigation strategy in your patch:
when there are already lots of requests in a queue, it's usually
a good idea to disable notifications and poll the
queue as requests complete. That could help performance.
--
MST
next prev parent reply other threads:[~2010-03-23 12:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 0:34 [RFC] vhost-blk implementation Badari Pulavarty
2010-03-23 12:39 ` Michael S. Tsirkin [this message]
2010-03-23 14:47 ` Badari Pulavarty
2010-03-23 17:57 ` Badari Pulavarty
2010-03-23 18:06 ` Michael S. Tsirkin
2010-03-23 19:55 ` Badari Pulavarty
2010-03-24 9:52 ` Michael S. Tsirkin
2010-03-24 11:23 ` Michael S. Tsirkin
2010-03-24 17:58 ` Badari Pulavarty
2010-03-24 18:28 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 1:00 Badari Pulavarty
2010-03-23 1:16 ` Anthony Liguori
2010-03-23 1:45 ` Badari Pulavarty
2010-03-23 2:00 ` Anthony Liguori
2010-03-23 2:50 ` Badari Pulavarty
2010-03-23 10:05 ` Avi Kivity
2010-03-23 14:48 ` Badari Pulavarty
2010-03-23 10:03 ` Avi Kivity
2010-03-23 14:55 ` Badari Pulavarty
2010-03-23 16:53 ` Avi Kivity
2010-03-24 20:05 ` Christoph Hellwig
2010-03-25 6:29 ` Avi Kivity
2010-03-25 15:48 ` Christoph Hellwig
2010-03-25 15:51 ` Avi Kivity
2010-03-25 15:00 ` Asdo
2010-04-05 19:59 ` Christoph Hellwig
2010-03-23 10:09 ` Eran Rom
2010-03-24 20:04 ` Christoph Hellwig
2010-03-24 20:22 ` Badari Pulavarty
2010-03-25 7:57 ` Avi Kivity
2010-03-25 14:36 ` Badari Pulavarty
2010-03-25 15:57 ` Christoph Hellwig
2010-03-26 18:53 ` Eran Rom
2010-04-08 16:17 ` Stefan Hajnoczi
2010-04-05 19:23 ` Christoph Hellwig
2010-04-05 23:17 ` Badari Pulavarty
2010-03-24 20:27 ` Badari Pulavarty
2010-03-29 15:41 ` Badari Pulavarty
2010-03-29 18:20 ` Chris Wright
2010-03-29 20:37 ` Avi Kivity
2010-03-29 22:51 ` Badari Pulavarty
2010-03-29 23:56 ` Chris Wright
2010-03-30 12:43 ` Avi Kivity
2010-04-05 14:22 ` Stefan Hajnoczi
2010-04-06 2:27 ` Badari Pulavarty
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=20100323123916.GA24750@redhat.com \
--to=mst@redhat.com \
--cc=pbadari@us.ibm.com \
--cc=qemu-devel@nongnu.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 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.