--- v2
+++ v3
@@ -5,7 +5,7 @@
etc. It has fixed maximum length, and it bounds are visible using
return from receive calls: 'read()', 'recv()', 'recvmsg()' etc.
Current implementation based on message definition above.
- Record has unlimited length, it consists of multiple messages,
+ Record has unlimited length, it consists of multiple message,
and bounds of record are visible via MSG_EOR flag returned from
'recvmsg()' call. Sender passes MSG_EOR to sending system call and
receiver will see MSG_EOR when corresponding message will be processed.
@@ -25,10 +25,11 @@
is used to mark 'MSG_EOR' bit passed from userspace.
This patchset includes simple test for MSG_EOR.
- Arseny Krasnov(5):
- virtio/vsock: add 'VIRTIO_VSOCK_SEQ_EOM' bit
+ Arseny Krasnov(6):
+ virtio/vsock: rename 'EOR' to 'EOM' bit.
+ virtio/vsock: add 'VIRTIO_VSOCK_SEQ_EOR' bit.
vhost/vsock: support MSG_EOR bit processing
- virito/vsock: support MSG_EOR bit processing
+ virtio/vsock: support MSG_EOR bit processing
af_vsock: rename variables in receive loop
vsock_test: update message bounds test for MSG_EOR
@@ -38,6 +39,15 @@
net/vmw_vsock/virtio_transport_common.c | 23 +++++++++++++++--------
tools/testing/vsock/vsock_test.c | 8 +++++++-
5 files changed, 42 insertions(+), 24 deletions(-)
+
+ v2 -> v3:
+ - 'virtio/vsock: rename 'EOR' to 'EOM' bit.' - commit message updated.
+ - 'VIRTIO_VSOCK_SEQ_EOR' bit add moved to separate patch.
+ - 'vhost/vsock: support MSG_EOR bit processing' - commit message
+ updated.
+ - 'vhost/vsock: support MSG_EOR bit processing' - removed unneeded
+ 'le32_to_cpu()', because input argument was already in CPU
+ endianness.
v1 -> v2:
- 'VIRTIO_VSOCK_SEQ_EOR' is renamed to 'VIRTIO_VSOCK_SEQ_EOM', to