Thread (1 message) 1 message, 1 author, 2017-12-01

Re: [PATCH] vsock.7: document VSOCK socket address family

From: Stefan Hajnoczi <hidden>
Date: 2017-12-01 13:09:01
Also in: netdev

On Thu, Nov 30, 2017 at 01:21:26PM +0000, Jorgen S. Hansen wrote:
quoted
On Nov 30, 2017, at 12:21 PM, Stefan Hajnoczi [off-list ref] wrote:
Thanks for the quick review!

I forgot to ask you: Is SOCK_DGRAM reliable and in-order over VMCI?
quoted
+.PP
+Valid socket types are
+.B SOCK_STREAM
+and
+.B SOCK_DGRAM .
The space here results in a space between SOCK_DGRAM and the “.” in the formatted text. Is that intentional?
I haven't figured out the groff syntax to avoid the space :(.  Any
ideas?
quoted
+.PP
+There are several special addresses:
+.B VMADDR_CID_ANY
+(-1U)
+means any address for binding;
+.B VMADDR_CID_HYPERVISOR
We use VMADDR_CID_HYPERVISOR for communicating with services in the hypervisor, so you could describe this as “an address reserved for services built into the hypervisor”.
Will fix.
quoted
+.SH VERSIONS
+Support for VMware has been available since Linux 3.9.  KVM (virtio) is
VMware (VMCI) for clarity.
Will fix.
Apart from the nits, this looks great.
Please let me know if there are any other topics that we should cover in
the man page.

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help