From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: mtk.manpages@gmail.com, netdev@vger.kernel.org,
linux-man@vger.kernel.org, Dexuan Cui <decui@microsoft.com>,
Jorgen Hansen <jhansen@vmware.com>
Subject: Re: [PATCH] vsock.7: add VMADDR_CID_LOCAL description
Date: Thu, 13 Feb 2020 09:17:48 +0000 [thread overview]
Message-ID: <20200213091748.GB542404@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200211102532.56795-1-sgarzare@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Tue, Feb 11, 2020 at 11:25:32AM +0100, Stefano Garzarella wrote:
Do you want to mention that loopback works in the guest and on the host
since Linux vX.Y and before that it only worked inside the guest?
> @@ -164,6 +164,16 @@ Consider using
> .B VMADDR_CID_ANY
> when binding instead of getting the local CID with
> .BR IOCTL_VM_SOCKETS_GET_LOCAL_CID .
> +.SS Local communication
> +The
> +.B VMADDR_CID_LOCAL
> +(1) can be used to address itself. In this case all packets are redirected
> +to the same host that generated them. Useful for testing and debugging.
This can be rephrased more naturally:
.B VMADDR_CID_LOCAL
(1) directs packets to the same host that generated them. This is useful
for testing applications on a single host and for debugging.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-13 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 10:25 [PATCH] vsock.7: add VMADDR_CID_LOCAL description Stefano Garzarella
2020-02-13 9:17 ` Stefan Hajnoczi [this message]
2020-02-13 9:44 ` Stefano Garzarella
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=20200213091748.GB542404@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=decui@microsoft.com \
--cc=jhansen@vmware.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).