From: Avi Kivity <avi@redhat.com>
To: Liu Yuan <namei.unix@gmail.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Khoa Huynh <khoa@us.ibm.com>,
Badari Pulavarty <pbadari@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC PATCH]vhost-blk: In-kernel accelerator for virtio block device
Date: Mon, 01 Aug 2011 12:37:39 +0300 [thread overview]
Message-ID: <4E3673E3.6020100@redhat.com> (raw)
In-Reply-To: <4E366F4A.1030704@gmail.com>
On 08/01/2011 12:18 PM, Liu Yuan wrote:
>> Agree. vhost-net works around the lack of async zero copy networking
>> interface. Block I/O on the other hand does have such an interface,
>> and in addition transaction rates are usually lower. All we're
>> saving is the syscall overhead.
>>
>
> Personally I too agree with Sasha Levin. But vhost-blk is the first
> fast prototype that is supposed to act as a code base to do further
> optimisation, which I plan to utilize kernel's internal stuff like
> BIO layer, that can not be accessed from user space, to maximize the
> performance for raw disk based block IO.
Is there anything in the bio layer which is not exposed by linux-aio?
Or is linux-aio slow in translating from vfs ops to bio ops?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-01 9:37 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
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 [this message]
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=4E3673E3.6020100@redhat.com \
--to=avi@redhat.com \
--cc=hch@infradead.org \
--cc=khoa@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=namei.unix@gmail.com \
--cc=pbadari@us.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@gmail.com \
/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).