From: Paolo Bonzini <pbonzini@redhat.com>
To: Luke Gorrie <luke@snabb.co>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Rik van Riel <riel@redhat.com>,
virtualization@lists.linux-foundation.org,
virtio-comment@lists.oasis-open.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [virtio-dev] Zerocopy VM-to-VM networking using virtio-net
Date: Fri, 24 Apr 2015 10:20:28 +0200 [thread overview]
Message-ID: <5539FCCC.60708@redhat.com> (raw)
In-Reply-To: <CAA2XHbd_Wxs3O6ChSGouF3ZGH-SA0Lzw7OFVfvnuAXZmLAkZoA@mail.gmail.com>
On 24/04/2015 10:12, Luke Gorrie wrote:
>
> I think this approach could be fruitful in bringing virtio-net to
> VM-to-VM networking use cases. Unless virtio-net is extended for this
> use case, I'm afraid DPDK and OpenDataPlane communities might steer
> clear of VIRTIO.
>
>
> Questions:
>
> - How fast is needed?
>
> - How fast is the vhost-user support that shipped in DPDK 2.0?
vhost-user is fast. The problem is not the speed, it's the desire of a
more peer-to-peer operation.
virtio by design has very distinct roles for driver and device, so for
VM2VM communication the virtio design requires two devices in the guest
and two drivers, comprising a "switch", in the host.
The switch could be using vhost-user indeed, but my understanding is
that in some cases this switch component is undesirable. However, my
understanding does not include _why_ it is undesirable. This is where
we need to gather more information from the DPDK folks.
Paolo
next prev parent reply other threads:[~2015-04-24 8:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150422170138.GA8388@stefanha-thinkpad.redhat.com>
2015-04-22 17:46 ` Zerocopy VM-to-VM networking using virtio-net Cornelia Huck
[not found] ` <20150422194603.1e650ec7.cornelia.huck@de.ibm.com>
2015-04-22 18:00 ` Stefan Hajnoczi
2015-04-23 16:54 ` Cornelia Huck
2015-04-24 8:12 ` [virtio-dev] " Luke Gorrie
2015-04-24 8:20 ` Paolo Bonzini [this message]
2015-04-24 9:47 ` Stefan Hajnoczi
2015-04-24 9:50 ` Stefan Hajnoczi
2015-04-24 12:17 ` Luke Gorrie
2015-04-24 13:10 ` Luke Gorrie
2015-04-24 13:23 ` Stefan Hajnoczi
2015-04-24 13:22 ` Stefan Hajnoczi
2015-04-26 13:24 ` Luke Gorrie
2015-04-27 10:17 ` Stefan Hajnoczi
2015-04-27 10:36 ` Michael S. Tsirkin
2015-04-27 12:35 ` Jan Kiszka
2015-04-27 12:55 ` Jan Kiszka
2015-04-27 13:01 ` Stefan Hajnoczi
2015-04-27 13:08 ` Muli Ben-Yehuda
2015-04-27 14:30 ` Jan Kiszka
2015-04-27 14:36 ` Luke Gorrie
2015-04-27 14:38 ` Jan Kiszka
2015-04-27 14:40 ` Michael S. Tsirkin
2015-04-27 12:57 ` Stefan Hajnoczi
2015-04-27 13:17 ` Michael S. Tsirkin
2015-04-24 12:34 ` Luke Gorrie
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=5539FCCC.60708@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=luke@snabb.co \
--cc=mst@redhat.com \
--cc=riel@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox