From: Liu Yuan <namei.unix@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] vhost-blk: An in-kernel accelerator for virtio-blk
Date: Fri, 29 Jul 2011 19:19:39 +0800 [thread overview]
Message-ID: <4E32974B.6060605@gmail.com> (raw)
In-Reply-To: <20110728144740.GA26744@infradead.org>
On 07/28/2011 10:47 PM, Christoph Hellwig wrote:
> On Thu, Jul 28, 2011 at 10:29:05PM +0800, Liu Yuan wrote:
>> From: Liu Yuan<tailai.ly@taobao.com>
>>
>> Vhost-blk driver is an in-kernel accelerator, intercepting the
>> IO requests from KVM virtio-capable guests. It is based on the
>> vhost infrastructure.
>>
>> This is supposed to be a module over latest kernel tree, but it
>> needs some symbols from fs/aio.c and fs/eventfd.c to compile with.
>> So currently, after applying the patch, you need to *recomplie*
>> the kernel.
>>
>> Usage:
>> $kernel-src: make M=drivers/vhost
>> $kernel-src: sudo insmod drivers/vhost/vhost_blk.ko
>>
>> After insmod, you'll see /dev/vhost-blk created. done!
> You'll need to send the changes for existing code separately.
>
Thanks for reminding.
> If you're going mostly for raw blockdevice access just calling
> submit_bio will shave even more overhead off, and simplify the
> code a lot.
Yes, sounds cool, I'll give it a try.
Yuan
next prev parent reply other threads:[~2011-07-29 11:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 14:29 [RFC PATCH]vhost-blk: In-kernel accelerator for virtio block device Liu Yuan
2011-07-28 14:29 ` [RFC PATCH] vhost-blk: An in-kernel accelerator for virtio-blk Liu Yuan
2011-07-28 14:47 ` Christoph Hellwig
2011-07-29 11:19 ` Liu Yuan [this message]
2011-07-28 15:18 ` Stefan Hajnoczi
2011-07-28 15:22 ` Michael S. Tsirkin
2011-07-29 15:09 ` Liu Yuan
2011-08-01 6:25 ` Liu Yuan
2011-08-01 8:12 ` Michael S. Tsirkin
2011-08-01 8:55 ` Liu Yuan
2011-08-01 10:26 ` Michael S. Tsirkin
2011-08-11 19:59 ` Dongsu Park
2011-08-12 8:56 ` Alan Cox
2011-07-28 14:29 ` [RFC PATCH] vhost: Enable vhost-blk support Liu Yuan
2011-07-28 15:44 ` [RFC PATCH]vhost-blk: In-kernel accelerator for virtio block device Stefan Hajnoczi
2011-07-29 4:48 ` Stefan Hajnoczi
2011-07-29 7:59 ` Liu Yuan
2011-07-29 10:55 ` Christoph Hellwig
2011-07-29 7:22 ` Liu Yuan
2011-07-29 9:06 ` Stefan Hajnoczi
2011-07-29 12:01 ` Liu Yuan
2011-07-29 12:29 ` Stefan Hajnoczi
2011-07-29 12:50 ` Stefan Hajnoczi
2011-07-29 14:45 ` Liu Yuan
2011-07-29 14:50 ` Liu Yuan
2011-07-29 15:25 ` Sasha Levin
2011-08-01 8:17 ` Avi Kivity
2011-08-01 9:18 ` Liu Yuan
2011-08-01 9:37 ` Avi Kivity
2011-07-29 18:12 ` Badari Pulavarty
2011-08-01 5:46 ` Liu Yuan
2011-08-01 8:12 ` Christoph Hellwig
2011-08-04 21:58 ` Badari Pulavarty
2011-08-05 7:56 ` Liu Yuan
2011-08-05 11:04 ` Liu Yuan
2011-08-05 18:02 ` Badari Pulavarty
2011-08-08 1:35 ` Liu Yuan
2011-08-08 5:04 ` Badari Pulavarty
2011-08-08 7:31 ` Liu Yuan
2011-08-08 17:16 ` Badari Pulavarty
2011-08-10 2:19 ` Liu Yuan
2011-08-10 20:37 ` 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=4E32974B.6060605@gmail.com \
--to=namei.unix@gmail.com \
--cc=avi@redhat.com \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
/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).