From: "Michael S. Tsirkin" <mst@redhat.com>
To: Asias He <asias@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Benjamin LaHaise <bcrl@kvack.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Jeff Moyer <jmoyer@redhat.com>,
kvm@vger.kernel.org, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH RESEND 0/5] Add vhost-blk support
Date: Fri, 20 Jul 2012 22:30:35 +0300 [thread overview]
Message-ID: <20120720193035.GA20031@redhat.com> (raw)
In-Reply-To: <1342169711-12386-1-git-send-email-asias@redhat.com>
On Fri, Jul 13, 2012 at 04:55:06PM +0800, Asias He wrote:
>
> Hi folks,
>
> [I am resending to fix the broken thread in the previous one.]
>
> This patchset adds vhost-blk support. vhost-blk is a in kernel virito-blk
> device accelerator. Compared to userspace virtio-blk implementation, vhost-blk
> gives about 5% to 15% performance improvement.
>
> Asias He (5):
> aio: Export symbols and struct kiocb_batch for in kernel aio usage
> eventfd: Export symbol eventfd_file_create()
> vhost: Make vhost a separate module
> vhost-net: Use VHOST_NET_FEATURES for vhost-net
> vhost-blk: Add vhost-blk support
OK so given the state it's in, and assuming you think it is helpful
to let it mature in tree and not out of tree, I think it's
reasonable to try to do it like tcm_vhost is going to do it:
- send me changes to vhost core ASAP (and keep it minimal, e.g.
use your own header file to export to userspace)
- for other stuff - put in drivers/staging, and ask Greg to merge
--
MST
prev parent reply other threads:[~2012-07-20 19:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 8:55 [PATCH RESEND 0/5] Add vhost-blk support Asias He
2012-07-13 8:55 ` [PATCH RESEND 1/5] aio: Export symbols and struct kiocb_batch for in kernel aio usage Asias He
2012-07-13 8:55 ` [PATCH RESEND 2/5] eventfd: Export symbol eventfd_file_create() Asias He
2012-07-13 8:55 ` [PATCH RESEND 3/5] vhost: Make vhost a separate module Asias He
2012-07-13 8:55 ` [PATCH RESEND 4/5] vhost-net: Use VHOST_NET_FEATURES for vhost-net Asias He
2012-07-13 8:55 ` [PATCH RESEND 5/5] vhost-blk: Add vhost-blk support Asias He
2012-07-17 19:10 ` Jeff Moyer
2012-07-18 1:22 ` Asias He
2012-07-18 14:31 ` Jeff Moyer
2012-07-18 14:45 ` Asias He
2012-07-19 13:05 ` Anthony Liguori
2012-07-19 13:09 ` Michael S. Tsirkin
2012-07-19 13:09 ` Michael S. Tsirkin
2012-07-20 10:31 ` Stefan Hajnoczi
2012-07-20 20:56 ` Anthony Liguori
2012-07-21 1:07 ` Asias He
2012-07-14 7:49 ` [PATCH RESEND 0/5] " Christoph Hellwig
2012-07-16 9:05 ` Asias He
2012-07-17 15:09 ` Michael S. Tsirkin
2012-07-18 2:09 ` Asias He
2012-07-18 11:42 ` Stefan Hajnoczi
2012-07-20 19:30 ` Michael S. Tsirkin [this message]
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=20120720193035.GA20031@redhat.com \
--to=mst@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=asias@redhat.com \
--cc=bcrl@kvack.org \
--cc=gregkh@linuxfoundation.org \
--cc=jmoyer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).