diff options
| author |   Stefan Hajnoczi <stefanha@redhat.com> | 2016-11-21 13:56:31 +0000 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2016-11-24 11:53:15 -0500 |
| commit | b9116823189e85ccf3843c7d3ee3a361af0c3eb6 (patch) | |
| tree | 29f8d411eab94ef66fab1e0f50e700f97260285e /Makefile | |
| parent | Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (diff) | |
| download | linux-dev-b9116823189e85ccf3843c7d3ee3a361af0c3eb6.tar.xz linux-dev-b9116823189e85ccf3843c7d3ee3a361af0c3eb6.zip | |
VSOCK: add loopback to virtio_transport
The VMware VMCI transport supports loopback inside virtual machines.
This patch implements loopback for virtio-vsock.
Flow control is handled by the virtio-vsock protocol as usual. The
sending process stops transmitting on a connection when the peer's
receive buffer space is exhausted.
Cathy Avery <cavery@redhat.com> noticed this difference between VMCI and
virtio-vsock when a test case using loopback failed. Although loopback
isn't the main point of AF_VSOCK, it is useful for testing and
virtio-vsock must match VMCI semantics so that userspace programs run
regardless of the underlying transport.
My understanding is that loopback is not supported on the host side with
VMCI. Follow that by implementing it only in the guest driver, not the
vhost host driver.
Cc: Jorgen Hansen <jhansen@vmware.com>
Reported-by: Cathy Avery <cavery@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions