From: Asias He <asias@redhat.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Benjamin LaHaise <bcrl@kvack.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Michael S. Tsirkin" <mst@redhat.com>,
linux-aio@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add vhost-blk support
Date: Fri, 13 Jul 2012 09:19:55 +0800 [thread overview]
Message-ID: <4FFF77BB.2040605@redhat.com> (raw)
In-Reply-To: <x498vepklqu.fsf@segfault.boston.devel.redhat.com>
Hello Jeff,
On 07/13/2012 12:06 AM, Jeff Moyer wrote:
> Asias He <asias@redhat.com> writes:
>
>> Hi folks,
>>
>> 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
>
> I only saw patches 0 and 1. Where are the other 4? If the answer is,
> "not on lkml," then please resend them, CC'ing lkml.
I did send all the 0-5 patches to lkml, but I somehow messed up the
thread. Will CC you next time.
> I'd like to be able to see the usage of the aio routines.
OK. It'd be nice if you could review. Thanks.
--
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>
next prev parent reply other threads:[~2012-07-13 1:19 UTC|newest]
Thread overview: 31+ 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 ` [PATCH 1/5] aio: Export symbols and struct kiocb_batch for in kernel aio usage Asias He
2012-07-12 17:50 ` James Bottomley
2012-07-13 1:40 ` Asias He
2012-07-12 16:06 ` [PATCH 0/5] Add vhost-blk support Jeff Moyer
2012-07-13 1:19 ` Asias He [this message]
2012-07-16 11:58 ` Stefan Hajnoczi
2012-07-17 8:29 ` Asias He
2012-07-17 8:52 ` Paolo Bonzini
2012-07-17 9:21 ` Asias He
2012-07-17 9:32 ` Paolo Bonzini
2012-07-17 9:51 ` Michael S. Tsirkin
2012-07-17 11:11 ` Stefan Hajnoczi
2012-07-17 11:26 ` Michael S. Tsirkin
2012-07-17 11:42 ` Stefan Hajnoczi
2012-07-17 11:51 ` Stefan Hajnoczi
2012-07-17 11:54 ` Michael S. Tsirkin
2012-07-17 12:03 ` Stefan Hajnoczi
2012-07-17 12:48 ` Michael S. Tsirkin
2012-07-17 13:02 ` Paolo Bonzini
2012-07-17 13:26 ` Michael S. Tsirkin
2012-07-18 8:47 ` Asias He
2012-07-18 8:12 ` Asias He
2012-07-18 8:26 ` Stefan Hajnoczi
2012-07-18 9:46 ` Ronen Hod
2012-07-17 9:45 ` Michael S. Tsirkin
2012-07-17 10:14 ` Paolo Bonzini
2012-07-17 10:49 ` Michael S. Tsirkin
2012-07-17 10:56 ` Paolo Bonzini
2012-07-17 11:09 ` Michael S. Tsirkin
2012-07-17 11:36 ` Stefan Hajnoczi
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=4FFF77BB.2040605@redhat.com \
--to=asias@redhat.com \
--cc=bcrl@kvack.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=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 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).