From: Arseniy Krasnov <avkrasnov@sberdevices.ru>
To: Stefano Garzarella <sgarzare@redhat.com>,
Bobby Eshleman <bobby.eshleman@bytedance.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@sberdevices.ru>, <oxffffaa@gmail.com>
Subject: Re: [RFC PATCH v4 0/4] several updates to virtio/vsock
Date: Fri, 10 Mar 2023 12:42:13 +0300 [thread overview]
Message-ID: <15b9df26-bdc1-e139-8df7-62f966c719ed@sberdevices.ru> (raw)
In-Reply-To: <20230310090937.s55af2fx56zn4ewu@sgarzare-redhat>
On 10.03.2023 12:09, Stefano Garzarella wrote:
> Hi Arseniy,
>
> On Thu, Mar 09, 2023 at 11:24:42PM +0300, Arseniy Krasnov wrote:
>> Hello,
>>
>> this patchset evolved from previous v2 version (see link below). It does
>> several updates to virtio/vsock:
>> 1) Changes 'virtio_transport_inc/dec_rx_pkt()' interface. Now instead of
>> using skbuff state ('head' and 'data' pointers) to update 'fwd_cnt'
>> and 'rx_bytes', integer value is passed as an input argument. This
>> makes code more simple, because in this case we don't need to update
>> skbuff state before calling 'virtio_transport_inc/dec_rx_pkt()'. In
>> more common words - we don't need to change skbuff state to update
>> 'rx_bytes' and 'fwd_cnt' correctly.
>> 2) For SOCK_STREAM, when copying data to user fails, current skbuff is
>> not dropped. Next read attempt will use same skbuff and last offset.
>> Instead of 'skb_dequeue()', 'skb_peek()' + '__skb_unlink()' are used.
>> This behaviour was implemented before skbuff support.
>> 3) For SOCK_SEQPACKET it removes unneeded 'skb_pull()' call, because for
>> this type of socket each skbuff is used only once: after removing it
>> from socket's queue, it will be freed anyway.
>
> thanks for the fixes, I would wait a few days to see if there are any
> comments and then I think you can send it on net without RFC.
>
> @Bobby if you can take a look, your ack would be appreciated :-)
Ok, thanks for review. I'll wait for several days and also wait until
net-next will be opened. Then i'll resend this patchset with net-next
Thanks, Arseniy
>
> Thanks,
> Stefano
>
next prev parent reply other threads:[~2023-03-10 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 20:24 [RFC PATCH v4 0/4] several updates to virtio/vsock Arseniy Krasnov
2023-03-09 20:26 ` [RFC PATCH v4 1/4] virtio/vsock: don't use skbuff state to account credit Arseniy Krasnov
2023-03-10 9:04 ` Stefano Garzarella
2023-03-09 20:27 ` [RFC PATCH v4 2/4] virtio/vsock: remove redundant 'skb_pull()' call Arseniy Krasnov
2023-03-10 9:05 ` Stefano Garzarella
2023-03-09 20:28 ` [RFC PATCH v4 3/4] virtio/vsock: don't drop skbuff on copy failure Arseniy Krasnov
2023-03-10 9:05 ` Stefano Garzarella
2023-03-09 20:29 ` [RFC PATCH v4 4/4] test/vsock: copy to user failure test Arseniy Krasnov
2023-03-10 9:09 ` [RFC PATCH v4 0/4] several updates to virtio/vsock Stefano Garzarella
2023-03-10 9:42 ` Arseniy Krasnov [this message]
2023-03-10 11:40 ` Stefano Garzarella
2023-03-10 12:40 ` Arseniy Krasnov
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=15b9df26-bdc1-e139-8df7-62f966c719ed@sberdevices.ru \
--to=avkrasnov@sberdevices.ru \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.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: 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