From: Gregory Haskins <gregory.haskins@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
akpm@linux-foundation.org, hpa@zytor.com
Subject: Re: [PATCHv2 0/2] vhost: a kernel-level virtio server
Date: Tue, 11 Aug 2009 19:49:37 -0400 [thread overview]
Message-ID: <4A820391.1090404@gmail.com> (raw)
In-Reply-To: <20090811212743.GA26309@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Michael S. Tsirkin wrote:
> This implements vhost: a kernel-level backend for virtio,
> The main motivation for this work is to reduce virtualization
> overhead for virtio by removing system calls on data path,
> without guest changes. For virtio-net, this removes up to
> 4 system calls per packet: vm exit for kick, reentry for kick,
> iothread wakeup for packet, interrupt injection for packet.
>
> Some more detailed description attached to the patch itself.
>
> The patches are against 2.6.31-rc4. I'd like them to go into linux-next
> and down the road 2.6.32 if possible. Please comment.
I will add this series to my benchmark run in the next day or so. Any
specific instructions on how to set it up and run?
Regards,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2009-08-11 23:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 21:27 [PATCHv2 0/2] vhost: a kernel-level virtio server Michael S. Tsirkin
2009-08-11 21:27 ` Michael S. Tsirkin
2009-08-11 21:27 ` Michael S. Tsirkin
2009-08-11 23:49 ` Gregory Haskins [this message]
2009-08-12 7:16 ` Michael S. Tsirkin
2009-08-12 7:16 ` Michael S. Tsirkin
2009-08-12 7:16 ` Michael S. Tsirkin
2009-08-12 11:56 ` Gregory Haskins
2009-08-12 12:05 ` Michael S. Tsirkin
2009-08-12 12:05 ` Michael S. Tsirkin
2009-08-12 12:41 ` Gregory Haskins
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 12:52 ` Arnd Bergmann
2009-08-12 13:06 ` Michael S. Tsirkin
2009-08-12 13:06 ` Michael S. Tsirkin
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:40 ` Arnd Bergmann
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:42 ` Michael S. Tsirkin
2009-08-12 13:51 ` Gregory Haskins
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 16:13 ` Gregory Haskins
2009-08-12 16:37 ` Michael S. Tsirkin
2009-08-12 16:37 ` Michael S. Tsirkin
2009-08-12 16:37 ` Michael S. Tsirkin
2009-08-12 16:13 ` Gregory Haskins
2009-08-12 14:02 ` Michael S. Tsirkin
2009-08-12 13:51 ` Gregory Haskins
2009-08-12 13:06 ` Michael S. Tsirkin
2009-08-12 13:04 ` Michael S. Tsirkin
2009-08-12 13:04 ` Michael S. Tsirkin
2009-08-12 13:04 ` Michael S. Tsirkin
2009-08-12 12:41 ` Gregory Haskins
2009-08-12 12:05 ` Michael S. Tsirkin
2009-08-12 11:56 ` Gregory Haskins
2009-08-11 23:49 ` Gregory Haskins
-- strict thread matches above, loose matches on Subject: below --
2009-08-11 21:27 Michael S. Tsirkin
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=4A820391.1090404@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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.