From: Cathy Avery <cavery@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Jorgen Hansen <jhansen@vmware.com>
Cc: netdev@vger.kernel.org
Subject: Re: AF_VSOCK loopback
Date: Thu, 10 Nov 2016 11:17:55 -0500 [thread overview]
Message-ID: <58249DB3.7050601@redhat.com> (raw)
In-Reply-To: <20161110144329.GA19683@stefanha-x1.localdomain>
I had trouble with loopback on the esx host. Using the nc-vsock (
AF_VSOCK 56 ) the server and the client connected but they both
terminated without error when I attempted to send characters over. It
might be due to something other than vsock. I haven't pursued it yet.
On 11/10/2016 09:43 AM, Stefan Hajnoczi wrote:
> Hi Jorgen,
> Cathy Avery found that the AF_VSOCK VMCI transport does loopback inside
> the guest (but not on the host?). The virtio transport currently does
> no loopback.
>
> The loopback scenario I'm thinking of is where process A listens on port
> 1234 and process B on the same machine connects to port 1234 both with
> the same CID.
>
> I'd like to make the virtio transport compatible with VMCI transport
> semantics so AF_VSOCK behaves the same regardless of the transport.
> This means loopback must be added to virtio-vsock.
>
> The core net/vmware/af_vsock.c code does not implement loopback. How
> does VMCI do loopback? Are the loopback packets reflected back from the
> host? Or does the guest driver notice the loopback and avoid passing
> packets to the host in the first place?
>
> Maybe we can make the loopback code common in af_vsock.c if that avoids
> code duplication.
>
> Thanks,
> Stefan
next prev parent reply other threads:[~2016-11-10 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 14:43 AF_VSOCK loopback Stefan Hajnoczi
2016-11-10 16:17 ` Cathy Avery [this message]
2016-11-11 14:14 ` Jorgen S. Hansen
2016-11-14 19:14 ` Stefan Hajnoczi
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=58249DB3.7050601@redhat.com \
--to=cavery@redhat.com \
--cc=jhansen@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.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.