Displaying 2 results from an estimated 2 matches for "irtio_vsock_op_attach".
Did you mean:
virtio_vsock_op_attach
2013 Jun 28
1
[RFC 0/5] Introduce VM Sockets virtio transport
...ts,
but Asias can clarify.
> > Virtio VM socket connection creation:
> > 1) Client sends VIRTIO_VSOCK_OP_REQUEST to server
> > 2) Server reponses with VIRTIO_VSOCK_OP_NEGOTIATE to client
> > 3) Client sends VIRTIO_VSOCK_OP_OFFER to server
> > 4) Server responses with VIRTIO_VSOCK_OP_ATTACH to client
>
> What's the reason for a 4 stage setup? Most transports
> make do with 3.
I'm guessing that's also based on the original vSockets/VMCI
implementation, where the NEGOTIATE/OFFER stages are used to
negotiate the underlying transport buffer size (in VMCI, the
queuep...
2013 Jun 28
1
[RFC 0/5] Introduce VM Sockets virtio transport
...ts,
but Asias can clarify.
> > Virtio VM socket connection creation:
> > 1) Client sends VIRTIO_VSOCK_OP_REQUEST to server
> > 2) Server reponses with VIRTIO_VSOCK_OP_NEGOTIATE to client
> > 3) Client sends VIRTIO_VSOCK_OP_OFFER to server
> > 4) Server responses with VIRTIO_VSOCK_OP_ATTACH to client
>
> What's the reason for a 4 stage setup? Most transports
> make do with 3.
I'm guessing that's also based on the original vSockets/VMCI
implementation, where the NEGOTIATE/OFFER stages are used to
negotiate the underlying transport buffer size (in VMCI, the
queuep...