From: "Michael S. Tsirkin" <mst@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org, dlstevens@us.ibm.com
Subject: [PATCH RFC 0/3] qemu/vhost-net: mergeable buffers support
Date: Fri, 16 Jul 2010 12:04:34 +0300 [thread overview]
Message-ID: <cover.1279270823.git.mst@redhat.com> (raw)
This adds mergeable buffers support in vhost-net in qemu.
With this patch, sending raw packets while vhost-net is active should
work as well: important for migration. Compile-tested only for now.
David, could you please review and maybe try this out?
The kernel side is in vhost-net-next. I intend for it to got into
net-next and then into 2.6.36.
TODO: basic test. migration test, send pull request.
Michael S. Tsirkin (3):
tap: generalize code for different vnet header len
tap: add APIs for vnet header length
vhost_net: mergeable buffers support
hw/vhost_net.c | 23 ++++++++++++++++++++++-
net/tap-aix.c | 9 +++++++++
net/tap-bsd.c | 9 +++++++++
net/tap-linux.c | 29 +++++++++++++++++++++++++++++
net/tap-linux.h | 8 ++++++++
net/tap-solaris.c | 9 +++++++++
net/tap-win32.c | 9 +++++++++
net/tap.c | 49 +++++++++++++++++++++++++++++++++++--------------
net/tap.h | 4 ++++
9 files changed, 134 insertions(+), 15 deletions(-)
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org, dlstevens@us.ibm.com
Subject: [Qemu-devel] [PATCH RFC 0/3] qemu/vhost-net: mergeable buffers support
Date: Fri, 16 Jul 2010 12:04:34 +0300 [thread overview]
Message-ID: <cover.1279270823.git.mst@redhat.com> (raw)
This adds mergeable buffers support in vhost-net in qemu.
With this patch, sending raw packets while vhost-net is active should
work as well: important for migration. Compile-tested only for now.
David, could you please review and maybe try this out?
The kernel side is in vhost-net-next. I intend for it to got into
net-next and then into 2.6.36.
TODO: basic test. migration test, send pull request.
Michael S. Tsirkin (3):
tap: generalize code for different vnet header len
tap: add APIs for vnet header length
vhost_net: mergeable buffers support
hw/vhost_net.c | 23 ++++++++++++++++++++++-
net/tap-aix.c | 9 +++++++++
net/tap-bsd.c | 9 +++++++++
net/tap-linux.c | 29 +++++++++++++++++++++++++++++
net/tap-linux.h | 8 ++++++++
net/tap-solaris.c | 9 +++++++++
net/tap-win32.c | 9 +++++++++
net/tap.c | 49 +++++++++++++++++++++++++++++++++++--------------
net/tap.h | 4 ++++
9 files changed, 134 insertions(+), 15 deletions(-)
--
MST
next reply other threads:[~2010-07-16 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 9:04 Michael S. Tsirkin [this message]
2010-07-16 9:04 ` [Qemu-devel] [PATCH RFC 0/3] qemu/vhost-net: mergeable buffers support Michael S. Tsirkin
2010-07-16 9:04 ` [PATCH RFC 1/3] tap: generalize code for different vnet header len Michael S. Tsirkin
2010-07-16 9:04 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-16 9:04 ` [PATCH RFC 2/3] tap: add APIs for vnet header length Michael S. Tsirkin
2010-07-16 9:04 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-16 9:04 ` [PATCH RFC 3/3] vhost_net: mergeable buffers support Michael S. Tsirkin
2010-07-16 9:04 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-16 9:19 ` [PATCH RFC 0/3] qemu/vhost-net: " Michael S. Tsirkin
2010-07-16 9:19 ` [Qemu-devel] " 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=cover.1279270823.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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.