All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>, Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: virtio-blk performance and MSI
Date: Sun, 09 Aug 2009 13:01:35 +0300	[thread overview]
Message-ID: <4A7E9E7F.2090901@redhat.com> (raw)
In-Reply-To: <20090806163549.GA25594@lst.de>

On 08/06/2009 07:35 PM, Christoph Hellwig wrote:
> Michael suggested to me a while ago to try MSI with virtio-blk and I
> played with this small patch:
>
>
> Index: qemu-kvm/hw/virtio-blk.c
> ===================================================================
> --- qemu-kvm.orig/hw/virtio-blk.c
> +++ qemu-kvm/hw/virtio-blk.c
> @@ -416,6 +416,7 @@ VirtIODevice *virtio_blk_init(DeviceStat
>       s->vdev.get_config = virtio_blk_update_config;
>       s->vdev.get_features = virtio_blk_get_features;
>       s->vdev.reset = virtio_blk_reset;
> +    s->vdev.nvectors = 2;
>       s->bs = bs;
>       s->rq = NULL;
>       if (strlen(ps = (char *)drive_get_serial(bs)))
>
> which gave about 5% speedups on 4k sized reads and writes, see the full
> iozone output I attached.  Now getting the information about using
> multiple MSI vectors from the command line to virtio-blk similar to how
> virtio-net does seems extremly messy right now.  Waiting for Gerd's
> additional qdev patches to make it easier as a qdev property.
>
>    

Looks good.  Anthony, I think this applies upstream?

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>, Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: virtio-blk performance and MSI
Date: Sun, 09 Aug 2009 13:01:35 +0300	[thread overview]
Message-ID: <4A7E9E7F.2090901@redhat.com> (raw)
In-Reply-To: <20090806163549.GA25594@lst.de>

On 08/06/2009 07:35 PM, Christoph Hellwig wrote:
> Michael suggested to me a while ago to try MSI with virtio-blk and I
> played with this small patch:
>
>
> Index: qemu-kvm/hw/virtio-blk.c
> ===================================================================
> --- qemu-kvm.orig/hw/virtio-blk.c
> +++ qemu-kvm/hw/virtio-blk.c
> @@ -416,6 +416,7 @@ VirtIODevice *virtio_blk_init(DeviceStat
>       s->vdev.get_config = virtio_blk_update_config;
>       s->vdev.get_features = virtio_blk_get_features;
>       s->vdev.reset = virtio_blk_reset;
> +    s->vdev.nvectors = 2;
>       s->bs = bs;
>       s->rq = NULL;
>       if (strlen(ps = (char *)drive_get_serial(bs)))
>
> which gave about 5% speedups on 4k sized reads and writes, see the full
> iozone output I attached.  Now getting the information about using
> multiple MSI vectors from the command line to virtio-blk similar to how
> virtio-net does seems extremly messy right now.  Waiting for Gerd's
> additional qdev patches to make it easier as a qdev property.
>
>    

Looks good.  Anthony, I think this applies upstream?

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-08-09  9:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 16:35 virtio-blk performance and MSI Christoph Hellwig
2009-08-06 16:35 ` [Qemu-devel] " Christoph Hellwig
2009-08-09 10:01 ` Avi Kivity [this message]
2009-08-09 10:01   ` [Qemu-devel] " Avi Kivity
2009-08-09 17:41   ` Christoph Hellwig
2009-08-09 17:41     ` Christoph Hellwig
2009-08-09 17:49     ` Avi Kivity
2009-08-09 17:49       ` Avi Kivity
2009-08-09 19:13       ` Christoph Hellwig
2009-08-09 19:13         ` Christoph Hellwig
2009-08-09 19:53         ` Michael S. Tsirkin
2009-08-09 19:53           ` Michael S. Tsirkin
2009-08-09 19:49     ` Michael S. Tsirkin
2009-08-09 19:49       ` Michael S. Tsirkin
2009-08-09 19:56   ` Michael S. Tsirkin
2009-08-09 19:56     ` [Qemu-devel] " Michael S. Tsirkin
2009-08-11  6:05 ` Eran Rom
2009-08-11 10:30 ` Eran Rom
2009-08-11 12:14 ` Eran Rom

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=4A7E9E7F.2090901@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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.