From: Stefano Garzarella <sgarzare@redhat.com>
To: Arseny Krasnov <arseny.krasnov@kaspersky.com>
Cc: Andra Paraschiv <andraprs@amazon.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"stsp2@yandex.ru" <stsp2@yandex.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"oxffffaa@gmail.com" <oxffffaa@gmail.com>,
Norbert Slusarek <nslusarek@gmx.net>,
Stefan Hajnoczi <stefanha@redhat.com>,
Colin Ian King <colin.king@canonical.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jorgen Hansen <jhansen@vmware.com>,
Alexander Popov <alex.popov@linux.com>
Subject: Re: [RFC PATCH v8 00/19] virtio/vsock: introduce SOCK_SEQPACKET support
Date: Thu, 22 Apr 2021 12:02:17 +0200 [thread overview]
Message-ID: <20210422100217.jmpgevtrukqyukfo@steredhat> (raw)
In-Reply-To: <bfefdd94-a84f-8bed-331e-274654a7426f@kaspersky.com>
On Thu, Apr 22, 2021 at 12:40:17PM +0300, Arseny Krasnov wrote:
>On 22.04.2021 11:46, Stefano Garzarella wrote:
>> On Wed, Apr 21, 2021 at 06:06:28PM +0300, Arseny Krasnov wrote:
>>> Thank You, i'll prepare next version. Main question is: does this
>>> approach(no SEQ_BEGIN, SEQ_END, 'msg_len' and 'msg_id') considered
>>> good? In this case it will be easier to prepare final version, because
>>> is smaller and more simple than previous logic. Also patch to spec
>>> will be smaller.
>> Yes, it's definitely much better than before.
>>
>> The only problem I see is that we add some overhead per fragment
>> (header). We could solve that with the mergeable buffers that Jiang is
>> considering for DGRAM.
>
>If we are talking about receive, i think, i can reuse merge logic for
Yep, for TX the guest can potentially enqueue a big buffer.
Maybe it's still worth keeping a maximum size and fragmenting as we do
now.
>
>stream sockets, the only difference is that buffers are mergeable
>until previous EOR(e.g. previous message) bit is found in rx queue.
>
I got a little lost.
Can you elaborate more?
Thanks,
Stefano
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-04-22 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210413123954.3396314-1-arseny.krasnov@kaspersky.com>
[not found] ` <20210413124250.3400313-1-arseny.krasnov@kaspersky.com>
2021-04-21 8:37 ` [RFC PATCH v8 04/19] af_vsock: implement SEQPACKET receive loop Stefano Garzarella
[not found] ` <20210413124443.3403382-1-arseny.krasnov@kaspersky.com>
2021-04-21 8:56 ` [RFC PATCH v8 11/19] virtio/vsock: dequeue callback for SOCK_SEQPACKET Stefano Garzarella
[not found] ` <20210413124528.3404287-1-arseny.krasnov@kaspersky.com>
2021-04-21 9:12 ` [RFC PATCH v8 13/19] virtio/vsock: rest of SOCK_SEQPACKET support Stefano Garzarella
[not found] ` <20210413124552.3404877-1-arseny.krasnov@kaspersky.com>
2021-04-21 9:22 ` [RFC PATCH v8 14/19] virtio/vsock: enable SEQPACKET for transport Stefano Garzarella
[not found] ` <20210413124620.3405764-1-arseny.krasnov@kaspersky.com>
2021-04-21 9:31 ` [RFC PATCH v8 15/19] vhost/vsock: " Stefano Garzarella
[not found] ` <20210413124642.3406320-1-arseny.krasnov@kaspersky.com>
2021-04-21 9:34 ` [RFC PATCH v8 16/19] vsock/loopback: " Stefano Garzarella
[not found] ` <20210413124701.3407363-1-arseny.krasnov@kaspersky.com>
2021-04-21 9:35 ` [RFC PATCH v8 17/19] vsock_test: add SOCK_SEQPACKET tests Stefano Garzarella
[not found] ` <20210413124739.3408031-1-arseny.krasnov@kaspersky.com>
[not found] ` <7d433ed9-8d4c-707a-9149-ff0e65d7f943@kaspersky.com>
2021-04-21 9:38 ` [RFC PATCH v8 19/19] af_vsock: serialize writes to shared socket Stefano Garzarella
2021-04-21 9:52 ` [RFC PATCH v8 00/19] virtio/vsock: introduce SOCK_SEQPACKET support Stefano Garzarella
[not found] ` <2c3d0749-0f41-e064-0153-b6130268add2@kaspersky.com>
2021-04-22 8:46 ` Stefano Garzarella
[not found] ` <bfefdd94-a84f-8bed-331e-274654a7426f@kaspersky.com>
2021-04-22 10:02 ` Stefano Garzarella [this message]
[not found] ` <bc649d1b-80d8-835c-6f47-8a7d402dd0b7@kaspersky.com>
2021-04-22 10:48 ` 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=20210422100217.jmpgevtrukqyukfo@steredhat \
--to=sgarzare@redhat.com \
--cc=alex.popov@linux.com \
--cc=andraprs@amazon.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=jhansen@vmware.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=stefanha@redhat.com \
--cc=stsp2@yandex.ru \
--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