Netdev Archive on lore.kernel.org help / color / mirror / Atom feed
From: Arseny Krasnov <arseny.krasnov@kaspersky.com> To: Stefan Hajnoczi <stefanha@redhat.com>, Stefano Garzarella <sgarzare@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, Jason Wang <jasowang@redhat.com>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, Arseny Krasnov <arseny.krasnov@kaspersky.com>, Colin Ian King <colin.king@canonical.com>, Andra Paraschiv <andraprs@amazon.com>, Norbert Slusarek <nslusarek@gmx.net> Cc: <kvm@vger.kernel.org>, <virtualization@lists.linux-foundation.org>, <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <oxffffaa@gmail.com> Subject: [RFC PATCH v1 0/7] virtio/vsock: introduce MSG_EOR flag for SEQPACKET Date: Mon, 26 Jul 2021 19:31:33 +0300 [thread overview] Message-ID: <20210726163137.2589102-1-arseny.krasnov@kaspersky.com> (raw) This patchset implements support of MSG_EOR bit for SEQPACKET AF_VSOCK sockets over virtio transport. Idea is to distinguish concepts of 'messages' and 'records'. Message is result of sending calls: 'write()', 'send()', 'sendmsg()' 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 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. To support MSG_EOR new bit was added along with existing 'VIRTIO_VSOCK_SEQ_EOR': 'VIRTIO_VSOCK_SEQ_EOM'(end-of-message) - now it works in the same way as 'VIRTIO_VSOCK_SEQ_EOR'. But 'VIRTIO_VSOCK_SEQ_EOR' is used to mark 'MSG_EOR' bit passed from userspace. This patchset includes simple test for MSG_EOR. Also i've added new vsock test for '-EAGAIN' receive result. Arseny Krasnov(7): virtio/vsock: add 'VIRTIO_VSOCK_SEQ_EOM' bit vsock: rename implementation from 'record' to 'message' vhost/vsock: support MSG_EOR bit processing virito/vsock: support MSG_EOR bit processing af_vsock: rename variables in receive loop vsock_test: update message bounds test for MSG_EOR vsock_test: 'SO_RCVTIMEO' test for SEQPACKET drivers/vhost/vsock.c | 28 +++++++---- include/uapi/linux/virtio_vsock.h | 1 + net/vmw_vsock/af_vsock.c | 10 ++-- net/vmw_vsock/virtio_transport_common.c | 23 +++++---- tools/testing/vsock/vsock_test.c | 57 ++++++++++++++++++++++- 5 files changed, 96 insertions(+), 23 deletions(-) Signed-off-by: Arseny Krasnov <arseny.krasnov@kaspersky.com> -- 2.25.1
next reply other threads:[~2021-07-26 16:32 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-26 16:31 Arseny Krasnov [this message] 2021-07-26 16:33 ` [RFC PATCH v1 1/7] virtio/vsock: add 'VIRTIO_VSOCK_SEQ_EOM' bit Arseny Krasnov 2021-08-06 7:18 ` Stefano Garzarella 2021-07-26 16:33 ` [RFC PATCH v1 2/7] vsock: rename implementation from 'record' to 'message' Arseny Krasnov 2021-08-06 7:20 ` Stefano Garzarella 2021-07-26 16:33 ` [RFC PATCH v1 3/7] vhost/vsock: support MSG_EOR bit processing Arseny Krasnov 2021-08-06 7:28 ` Stefano Garzarella 2021-08-06 8:40 ` Arseny Krasnov 2021-08-06 8:47 ` Stefano Garzarella 2021-07-26 16:33 ` [RFC PATCH v1 4/7] virito/vsock: " Arseny Krasnov 2021-07-26 16:34 ` [RFC PATCH v1 5/7] af_vsock: rename variables in receive loop Arseny Krasnov 2021-07-26 16:34 ` [RFC PATCH v1 6/7] vsock_test: update message bounds test for MSG_EOR Arseny Krasnov 2021-07-26 16:34 ` [RFC PATCH v1 7/7] vsock_test: 'SO_RCVTIMEO' test for SEQPACKET Arseny Krasnov 2021-07-27 7:59 ` [RFC PATCH v1 0/7] virtio/vsock: introduce MSG_EOR flag " Stefano Garzarella 2021-07-27 9:34 ` [MASSMAIL KLMS] " Arseny Krasnov 2021-07-27 9:58 ` Stefano Garzarella 2021-07-27 12:35 ` [MASSMAIL KLMS] " Arseny Krasnov 2021-08-04 12:57 ` Stefano Garzarella 2021-08-05 8:33 ` Arseny Krasnov 2021-08-05 9:06 ` Stefano Garzarella 2021-08-05 9:21 ` [!!Mass Mail KSE][MASSMAIL KLMS] " Arseny Krasnov 2021-08-06 7:16 ` 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=20210726163137.2589102-1-arseny.krasnov@kaspersky.com \ --to=arseny.krasnov@kaspersky.com \ --cc=andraprs@amazon.com \ --cc=colin.king@canonical.com \ --cc=davem@davemloft.net \ --cc=jasowang@redhat.com \ --cc=kuba@kernel.org \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mst@redhat.com \ --cc=netdev@vger.kernel.org \ --cc=nslusarek@gmx.net \ --cc=oxffffaa@gmail.com \ --cc=sgarzare@redhat.com \ --cc=stefanha@redhat.com \ --cc=virtualization@lists.linux-foundation.org \ /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: linkBe 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).