From: Stefano Garzarella <sgarzare@redhat.com>
To: Arseniy Krasnov <avkrasnov@sberdevices.ru>
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>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Bobby Eshleman <bobby.eshleman@bytedance.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 v3 00/17] vsock: MSG_ZEROCOPY flag support
Date: Fri, 26 May 2023 12:30:11 +0200 [thread overview]
Message-ID: <y5tgyj5awrd4hvlrsxsvrern6pd2sby2mdtskah2qp5hemmo2a@72nhcpilg7v2> (raw)
In-Reply-To: <76270fab-8af7-7597-9193-64cb553a543e@sberdevices.ru>
On Thu, May 25, 2023 at 06:56:42PM +0300, Arseniy Krasnov wrote:
>
>
>On 22.05.2023 10:39, Arseniy Krasnov wrote:
>
>This patchset is unstable with SOCK_SEQPACKET. I'll fix it.
Thanks for let us know!
I'm thinking if we should start split this series in two, because it
becomes too big.
But let keep this for RFC, we can decide later. An idea is to send
the first 7 patches with a preparation series, and the next ones with a
second series.
Thanks,
Stefano
WARNING: multiple messages have this Message-ID (diff)
From: Stefano Garzarella <sgarzare@redhat.com>
To: Arseniy Krasnov <avkrasnov@sberdevices.ru>
Cc: Bobby Eshleman <bobby.eshleman@bytedance.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,
Eric Dumazet <edumazet@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
kernel@sberdevices.ru, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH v3 00/17] vsock: MSG_ZEROCOPY flag support
Date: Fri, 26 May 2023 12:30:11 +0200 [thread overview]
Message-ID: <y5tgyj5awrd4hvlrsxsvrern6pd2sby2mdtskah2qp5hemmo2a@72nhcpilg7v2> (raw)
In-Reply-To: <76270fab-8af7-7597-9193-64cb553a543e@sberdevices.ru>
On Thu, May 25, 2023 at 06:56:42PM +0300, Arseniy Krasnov wrote:
>
>
>On 22.05.2023 10:39, Arseniy Krasnov wrote:
>
>This patchset is unstable with SOCK_SEQPACKET. I'll fix it.
Thanks for let us know!
I'm thinking if we should start split this series in two, because it
becomes too big.
But let keep this for RFC, we can decide later. An idea is to send
the first 7 patches with a preparation series, and the next ones with a
second series.
Thanks,
Stefano
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-05-26 10:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 7:39 [RFC PATCH v3 00/17] vsock: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 01/17] vsock/virtio: read data from non-linear skb Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 02/17] vhost/vsock: " Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 03/17] vsock/virtio: support to send " Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 04/17] vsock/virtio: non-linear skb handling for tap Arseniy Krasnov
2023-05-22 13:13 ` Simon Horman
2023-05-22 13:15 ` Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 05/17] vsock/virtio: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-05-22 13:11 ` Simon Horman
2023-05-22 13:09 ` Arseniy Krasnov
2023-05-23 5:46 ` Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 06/17] vsock: check error queue to set EPOLLERR Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 07/17] vsock: read from socket's error queue Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 08/17] vsock: check for MSG_ZEROCOPY support Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 09/17] vsock: enable SOCK_SUPPORT_ZC bit Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 10/17] vhost/vsock: support MSG_ZEROCOPY for transport Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 11/17] vsock/virtio: " Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 12/17] vsock/loopback: " Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 13/17] net/sock: enable setting SO_ZEROCOPY for PF_VSOCK Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 14/17] docs: net: description of MSG_ZEROCOPY for AF_VSOCK Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 15/17] test/vsock: MSG_ZEROCOPY flag tests Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 16/17] test/vsock: MSG_ZEROCOPY support for vsock_perf Arseniy Krasnov
2023-05-22 7:39 ` [RFC PATCH v3 17/17] test/vsock: io_uring rx/tx tests Arseniy Krasnov
2023-05-25 15:56 ` [RFC PATCH v3 00/17] vsock: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-05-26 10:30 ` Stefano Garzarella [this message]
2023-05-26 10:30 ` Stefano Garzarella
2023-05-26 11:36 ` Arseniy Krasnov
2023-05-26 12:23 ` Stefano Garzarella
2023-05-26 12:23 ` Stefano Garzarella
2023-05-26 12:28 ` 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=y5tgyj5awrd4hvlrsxsvrern6pd2sby2mdtskah2qp5hemmo2a@72nhcpilg7v2 \
--to=sgarzare@redhat.com \
--cc=avkrasnov@sberdevices.ru \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kernel@sberdevices.ru \
--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=oxffffaa@gmail.com \
--cc=pabeni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.