From: Asias He <asias@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Michael S. Tsirkin" <mst@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: Wed, 18 Jul 2012 16:47:27 +0800 [thread overview]
Message-ID: <5006781F.1060900@redhat.com> (raw)
In-Reply-To: <50056275.6000407@redhat.com>
On 07/17/2012 09:02 PM, Paolo Bonzini wrote:
> Il 17/07/2012 14:48, Michael S. Tsirkin ha scritto:
>> On Tue, Jul 17, 2012 at 01:03:39PM +0100, Stefan Hajnoczi wrote:
>>> On Tue, Jul 17, 2012 at 12:54 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>>>>> Knowing the answer to that is important before anyone can say whether
>>>>> this approach is good or not.
>>>>>
>>>>> Stefan
>>>>
>>>> Why is it?
>>>
>>> Because there might be a fix to kvmtool which closes the gap. It
>>> would be embarassing if vhost-blk was pushed just because no one
>>> looked into what is actually going on.
>>
>> Embarrasing to whom? Is someone working on an optimization that
>> makes the work in question redundant, with posting just around
>> the corner? Then maybe the thing to do is just wait a bit.
>
> Of course there is work going on to make QEMU perform better. Not sure
> about lkvm.
Of course for lkvm also.
>>> And on the flipside, hard evidence of an overhead that cannot be
>>> resolved could be good reason to do more vhost devices in the future.
>>
>> How can one have hard evidence of an overhead that cannot be resolved?
>
> Since we do have two completely independent userspaces (lkvm and
> data-plane QEMU), you can build up some compelling evidence of an
> overhead that cannot be resolved in user space.
This does not build the hard evidence either. How can one prove that
userspace lkvm and data-plane QEMU can not be improved further? The same
for vhost-blk.
>>> Either way, it's useful to do this before going further.
>>
>> I think each work should be discussed on its own merits. Maybe
>> vhost-blk is just well written. So? What is your conclusion?
>
> If it's just that vhost-blk is written well, my conclusion is that lkvm
> people should look into improving their virtio-blk userspace. We take
> hints from each other all the time, for example virtio-scsi will have
> unlocked kick in 3.6.
>
> Why can't vhost-* just get into staging, and we call it a day?
OK. I'm fine with staging.
--
Asias
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
WARNING: multiple messages have this Message-ID (diff)
From: Asias He <asias@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Michael S. Tsirkin" <mst@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: Wed, 18 Jul 2012 16:47:27 +0800 [thread overview]
Message-ID: <5006781F.1060900@redhat.com> (raw)
In-Reply-To: <50056275.6000407@redhat.com>
On 07/17/2012 09:02 PM, Paolo Bonzini wrote:
> Il 17/07/2012 14:48, Michael S. Tsirkin ha scritto:
>> On Tue, Jul 17, 2012 at 01:03:39PM +0100, Stefan Hajnoczi wrote:
>>> On Tue, Jul 17, 2012 at 12:54 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>>>>> Knowing the answer to that is important before anyone can say whether
>>>>> this approach is good or not.
>>>>>
>>>>> Stefan
>>>>
>>>> Why is it?
>>>
>>> Because there might be a fix to kvmtool which closes the gap. It
>>> would be embarassing if vhost-blk was pushed just because no one
>>> looked into what is actually going on.
>>
>> Embarrasing to whom? Is someone working on an optimization that
>> makes the work in question redundant, with posting just around
>> the corner? Then maybe the thing to do is just wait a bit.
>
> Of course there is work going on to make QEMU perform better. Not sure
> about lkvm.
Of course for lkvm also.
>>> And on the flipside, hard evidence of an overhead that cannot be
>>> resolved could be good reason to do more vhost devices in the future.
>>
>> How can one have hard evidence of an overhead that cannot be resolved?
>
> Since we do have two completely independent userspaces (lkvm and
> data-plane QEMU), you can build up some compelling evidence of an
> overhead that cannot be resolved in user space.
This does not build the hard evidence either. How can one prove that
userspace lkvm and data-plane QEMU can not be improved further? The same
for vhost-blk.
>>> Either way, it's useful to do this before going further.
>>
>> I think each work should be discussed on its own merits. Maybe
>> vhost-blk is just well written. So? What is your conclusion?
>
> If it's just that vhost-blk is written well, my conclusion is that lkvm
> people should look into improving their virtio-blk userspace. We take
> hints from each other all the time, for example virtio-scsi will have
> unlocked kick in 3.6.
>
> Why can't vhost-* just get into staging, and we call it a day?
OK. I'm fine with staging.
--
Asias
next prev parent reply other threads:[~2012-07-18 8:47 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 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 15:35 ` 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: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 11:11 ` Stefan Hajnoczi
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 [this message]
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-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
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=5006781F.1060900@redhat.com \
--to=asias@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=pbonzini@redhat.com \
--cc=stefanha@gmail.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.