From: Stefano Garzarella <sgarzare@redhat.com>
To: Arseny Krasnov <arseny.krasnov@kaspersky.com>
Cc: Andra Paraschiv <andraprs@amazon.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, oxffffaa@gmail.com,
Norbert Slusarek <nslusarek@gmx.net>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Colin Ian King <colin.king@canonical.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH v1 0/7] virtio/vsock: introduce MSG_EOR flag for SEQPACKET
Date: Tue, 27 Jul 2021 09:59:48 +0200 [thread overview]
Message-ID: <20210727075948.yl4w3foqa6rp4obg@steredhat> (raw)
In-Reply-To: <20210726163137.2589102-1-arseny.krasnov@kaspersky.com>
On Mon, Jul 26, 2021 at 07:31:33PM +0300, Arseny Krasnov wrote:
> 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.
At this point it's probably better to rename the old flag, so we stay
compatible.
What happens if one of the two peers does not support MSG_EOR handling,
while the other does?
I'll do a closer review in the next few days.
Thanks,
Stefano
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next parent reply other threads:[~2021-07-27 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210726163137.2589102-1-arseny.krasnov@kaspersky.com>
2021-07-27 7:59 ` Stefano Garzarella [this message]
[not found] ` <2df68589-96b9-abd4-ad1c-e25918b908a9@kaspersky.com>
2021-07-27 9:58 ` [MASSMAIL KLMS] Re: [RFC PATCH v1 0/7] virtio/vsock: introduce MSG_EOR flag for SEQPACKET Stefano Garzarella
2021-08-04 12:57 ` Stefano Garzarella
[not found] ` <8e44442c-4cac-dcbc-a88d-17d9878e7d32@kaspersky.com>
2021-08-05 9:06 ` Stefano Garzarella
[not found] ` <8bd80d3f-3e00-5e31-42a1-300ff29100ae@kaspersky.com>
2021-08-06 7:16 ` [!!Mass Mail KSE][MASSMAIL KLMS] " Stefano Garzarella
[not found] ` <20210726163307.2589516-1-arseny.krasnov@kaspersky.com>
2021-08-06 7:18 ` [RFC PATCH v1 1/7] virtio/vsock: add 'VIRTIO_VSOCK_SEQ_EOM' bit Stefano Garzarella
[not found] ` <20210726163328.2589649-1-arseny.krasnov@kaspersky.com>
2021-08-06 7:20 ` [RFC PATCH v1 2/7] vsock: rename implementation from 'record' to 'message' Stefano Garzarella
[not found] ` <20210726163341.2589759-1-arseny.krasnov@kaspersky.com>
2021-08-06 7:28 ` [RFC PATCH v1 3/7] vhost/vsock: support MSG_EOR bit processing Stefano Garzarella
[not found] ` <40a1d508-c841-23b7-58d5-f539b2d98ae1@kaspersky.com>
2021-08-06 8:47 ` 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=20210727075948.yl4w3foqa6rp4obg@steredhat \
--to=sgarzare@redhat.com \
--cc=andraprs@amazon.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--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=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: 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