All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-aio@kvack.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Benjamin LaHaise <bcrl@kvack.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add vhost-blk support
Date: Tue, 17 Jul 2012 12:14:33 +0200	[thread overview]
Message-ID: <50053B09.2060703@redhat.com> (raw)
In-Reply-To: <20120717094526.GC7949@redhat.com>

Il 17/07/2012 11:45, Michael S. Tsirkin ha scritto:
>> So it begs the question, is it going to be used in production, or just a
>> useful reference tool?
> 
> Sticking to raw already makes virtio-blk faster, doesn't it?
> In that vhost-blk looks to me like just another optimization option.
> Ideally I think user just should not care where do we handle virtio:
> in-kernel or in userspace.  One can imagine it being enabled/disabled
> automatically if none of the features unsupported by it are used.

Ok, that would make more sense.  One difference between vhost-blk and
vhost-net is that for vhost-blk there are also management actions that
would trigger the switch, for example a live snapshot.

So a prerequisite for vhost-blk would be that it is possible to disable
it on the fly while the VM is running, as soon as all in-flight I/O is
completed.

(Note that, however, this is not possible for vhost-scsi, because it
really exposes different hardware to the guest.  It must not happen that
a kernel upgrade or downgrade toggles between userspace SCSI and
vhost-scsi, for example).

>> having to
>> support the API; having to handle transition from one more thing when
>> something better comes out.
> 
> Well this is true for any code. If the limited featureset which
> vhost-blk can accelerate is something many people use, then accelerating
> by 5-15% might outweight support costs.

It is definitely what people use if they are interested in performance.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Asias He <asias@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>,
	linux-kernel@vger.kernel.org, linux-aio@kvack.org,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	Benjamin LaHaise <bcrl@kvack.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add vhost-blk support
Date: Tue, 17 Jul 2012 12:14:33 +0200	[thread overview]
Message-ID: <50053B09.2060703@redhat.com> (raw)
In-Reply-To: <20120717094526.GC7949@redhat.com>

Il 17/07/2012 11:45, Michael S. Tsirkin ha scritto:
>> So it begs the question, is it going to be used in production, or just a
>> useful reference tool?
> 
> Sticking to raw already makes virtio-blk faster, doesn't it?
> In that vhost-blk looks to me like just another optimization option.
> Ideally I think user just should not care where do we handle virtio:
> in-kernel or in userspace.  One can imagine it being enabled/disabled
> automatically if none of the features unsupported by it are used.

Ok, that would make more sense.  One difference between vhost-blk and
vhost-net is that for vhost-blk there are also management actions that
would trigger the switch, for example a live snapshot.

So a prerequisite for vhost-blk would be that it is possible to disable
it on the fly while the VM is running, as soon as all in-flight I/O is
completed.

(Note that, however, this is not possible for vhost-scsi, because it
really exposes different hardware to the guest.  It must not happen that
a kernel upgrade or downgrade toggles between userspace SCSI and
vhost-scsi, for example).

>> having to
>> support the API; having to handle transition from one more thing when
>> something better comes out.
> 
> Well this is true for any code. If the limited featureset which
> vhost-blk can accelerate is something many people use, then accelerating
> by 5-15% might outweight support costs.

It is definitely what people use if they are interested in performance.

Paolo

  reply	other threads:[~2012-07-17 10:14 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 15:35 [PATCH 0/5] Add vhost-blk support Asias He
2012-07-12 15:35 ` Asias He
2012-07-12 15:35 ` [PATCH 1/5] aio: Export symbols and struct kiocb_batch for in kernel aio usage Asias He
2012-07-12 15:35 ` Asias He
2012-07-12 15:35   ` Asias He
2012-07-12 17:50   ` James Bottomley
2012-07-13  1:40     ` Asias He
2012-07-13  1:40     ` Asias He
2012-07-13  1:40       ` Asias He
2012-07-12 16:06 ` [PATCH 0/5] Add vhost-blk support Jeff Moyer
2012-07-12 16:06   ` Jeff Moyer
2012-07-13  1:19   ` Asias He
2012-07-13  1:19   ` Asias He
2012-07-13  1:19     ` Asias He
2012-07-12 16:06 ` Jeff Moyer
2012-07-16 11:58 ` Stefan Hajnoczi
2012-07-16 11:58 ` Stefan Hajnoczi
2012-07-16 11:58   ` Stefan Hajnoczi
2012-07-17  8:29   ` Asias He
2012-07-17  8:29     ` Asias He
2012-07-17  8:52     ` Paolo Bonzini
2012-07-17  8:52       ` Paolo Bonzini
2012-07-17  9:21       ` Asias He
2012-07-17  9:21       ` Asias He
2012-07-17  9:21         ` Asias He
2012-07-17  9:32         ` Paolo Bonzini
2012-07-17  9:32           ` Paolo Bonzini
2012-07-17  9:51           ` Michael S. Tsirkin
2012-07-17  9:51             ` Michael S. Tsirkin
2012-07-17  9:51           ` Michael S. Tsirkin
2012-07-17  9:32         ` Paolo Bonzini
2012-07-17 11:11         ` Stefan Hajnoczi
2012-07-17 11:11           ` Stefan Hajnoczi
2012-07-17 11:26           ` Michael S. Tsirkin
2012-07-17 11:26           ` Michael S. Tsirkin
2012-07-17 11:26             ` Michael S. Tsirkin
2012-07-17 11:42             ` Stefan Hajnoczi
2012-07-17 11:42               ` Stefan Hajnoczi
2012-07-17 11:51               ` Stefan Hajnoczi
2012-07-17 11:51                 ` Stefan Hajnoczi
2012-07-17 11:54               ` Michael S. Tsirkin
2012-07-17 11:54                 ` Michael S. Tsirkin
2012-07-17 12:03                 ` Stefan Hajnoczi
2012-07-17 12:03                   ` Stefan Hajnoczi
2012-07-17 12:48                   ` Michael S. Tsirkin
2012-07-17 12:48                     ` Michael S. Tsirkin
2012-07-17 13:02                     ` Paolo Bonzini
2012-07-17 13:02                       ` Paolo Bonzini
2012-07-17 13:26                       ` Michael S. Tsirkin
2012-07-17 13:26                       ` Michael S. Tsirkin
2012-07-18  8:47                       ` Asias He
2012-07-18  8:47                       ` Asias He
2012-07-18  8:47                         ` Asias He
2012-07-17 12:48                   ` Michael S. Tsirkin
2012-07-17 11:54               ` Michael S. Tsirkin
2012-07-18  8:12           ` Asias He
2012-07-18  8:12             ` Asias He
2012-07-18  8:26             ` Stefan Hajnoczi
2012-07-18  8:26               ` Stefan Hajnoczi
2012-07-18  8:12           ` Asias He
2012-07-17 11:11         ` Stefan Hajnoczi
2012-07-18  9:46         ` Ronen Hod
2012-07-18  9:46         ` Ronen Hod
2012-07-18  9:46           ` Ronen Hod
2012-07-17  9:45       ` Michael S. Tsirkin
2012-07-17  9:45         ` Michael S. Tsirkin
2012-07-17 10:14         ` Paolo Bonzini [this message]
2012-07-17 10:14           ` Paolo Bonzini
2012-07-17 10:49           ` Michael S. Tsirkin
2012-07-17 10:49             ` Michael S. Tsirkin
2012-07-17 10:56             ` Paolo Bonzini
2012-07-17 10:56               ` Paolo Bonzini
2012-07-17 11:09               ` Michael S. Tsirkin
2012-07-17 11:09               ` Michael S. Tsirkin
2012-07-17 11:09                 ` Michael S. Tsirkin
2012-07-17  9:45       ` Michael S. Tsirkin
2012-07-17  8:52     ` Paolo Bonzini
2012-07-17 11:36     ` Stefan Hajnoczi
2012-07-17 11:36     ` Stefan Hajnoczi
2012-07-17 11:36       ` Stefan Hajnoczi
2012-07-17  8:29   ` Asias He

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=50053B09.2060703@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=bcrl@kvack.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    --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.