From: Avi Kivity <avi@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: xiaohui.xin@intel.com, netdev@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@elte.hu,
mst@redhat.com, jdike@c2.user-mode-linux.org,
davem@davemloft.net
Subject: Re: [RFC][PATCH v2 0/3] Provide a zero-copy method on KVM virtio-net.
Date: Sat, 03 Apr 2010 19:32:33 +0300 [thread overview]
Message-ID: <4BB76DA1.4050904@redhat.com> (raw)
In-Reply-To: <1270252268.13897.14.camel@w-sridhar.beaverton.ibm.com>
On 04/03/2010 02:51 AM, Sridhar Samudrala wrote:
> On Fri, 2010-04-02 at 15:25 +0800, xiaohui.xin@intel.com wrote:
>
>> The idea is simple, just to pin the guest VM user space and then
>> let host NIC driver has the chance to directly DMA to it.
>> The patches are based on vhost-net backend driver. We add a device
>> which provides proto_ops as sendmsg/recvmsg to vhost-net to
>> send/recv directly to/from the NIC driver. KVM guest who use the
>> vhost-net backend may bind any ethX interface in the host side to
>> get copyless data transfer thru guest virtio-net frontend.
>>
> What is the advantage of this approach compared to PCI-passthrough
> of the host NIC to the guest?
>
swapping/ksm/etc
independence from host hardware
live migration
> Does this require pinning of the entire guest memory? Or only the
> send/receive buffers?
>
If done correctly, just the send/receive buffers.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-04-03 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 7:25 [RFC][PATCH v2 0/3] Provide a zero-copy method on KVM virtio-net xiaohui.xin
2010-04-02 23:51 ` Sridhar Samudrala
2010-04-03 16:32 ` Avi Kivity [this message]
2010-04-06 6:06 ` Xin, Xiaohui
2010-04-14 15:25 ` Michael S. Tsirkin
2010-04-15 9:36 ` Xin, Xiaohui
2010-04-15 10:05 ` Michael S. Tsirkin
2010-04-19 10:05 ` Xin, Xiaohui
2010-04-19 10:21 ` Michael S. Tsirkin
2010-04-20 2:21 ` Xin, Xiaohui
2010-04-21 8:35 ` Michael S. Tsirkin
2010-04-22 8:57 ` Xin, Xiaohui
2010-04-22 9:19 ` 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=4BB76DA1.4050904@redhat.com \
--to=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=jdike@c2.user-mode-linux.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=xiaohui.xin@intel.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 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.