From: "Michael S. Tsirkin" <mst@redhat.com>
To: Arseniy Krasnov <avkrasnov@salutedevices.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@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: [PATCH net-next v9 0/4] vsock/virtio/vhost: MSG_ZEROCOPY preparations
Date: Mon, 18 Sep 2023 13:27:41 -0400 [thread overview]
Message-ID: <20230918132726-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230916130918.4105122-1-avkrasnov@salutedevices.com>
On Sat, Sep 16, 2023 at 04:09:14PM +0300, Arseniy Krasnov wrote:
> Hello,
>
> this patchset is first of three parts of another big patchset for
> MSG_ZEROCOPY flag support:
> https://lore.kernel.org/netdev/20230701063947.3422088-1-AVKrasnov@sberdevices.ru/
>
> During review of this series, Stefano Garzarella <sgarzare@redhat.com>
> suggested to split it for three parts to simplify review and merging:
>
> 1) virtio and vhost updates (for fragged skbs) <--- this patchset
> 2) AF_VSOCK updates (allows to enable MSG_ZEROCOPY mode and read
> tx completions) and update for Documentation/.
> 3) Updates for tests and utils.
>
> This series enables handling of fragged skbs in virtio and vhost parts.
> Newly logic won't be triggered, because SO_ZEROCOPY options is still
> impossible to enable at this moment (next bunch of patches from big
> set above will enable it).
Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> I've included changelog to some patches anyway, because there were some
> comments during review of last big patchset from the link above.
>
> Head for this patchset is:
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f2fa1c812c91e99d0317d1fc7d845e1e05f39716
>
> Link to v1:
> https://lore.kernel.org/netdev/20230717210051.856388-1-AVKrasnov@sberdevices.ru/
> Link to v2:
> https://lore.kernel.org/netdev/20230718180237.3248179-1-AVKrasnov@sberdevices.ru/
> Link to v3:
> https://lore.kernel.org/netdev/20230720214245.457298-1-AVKrasnov@sberdevices.ru/
> Link to v4:
> https://lore.kernel.org/netdev/20230727222627.1895355-1-AVKrasnov@sberdevices.ru/
> Link to v5:
> https://lore.kernel.org/netdev/20230730085905.3420811-1-AVKrasnov@sberdevices.ru/
> Link to v6:
> https://lore.kernel.org/netdev/20230814212720.3679058-1-AVKrasnov@sberdevices.ru/
> Link to v7:
> https://lore.kernel.org/netdev/20230827085436.941183-1-avkrasnov@salutedevices.com/
> Link to v8:
> https://lore.kernel.org/netdev/20230911202234.1932024-1-avkrasnov@salutedevices.com/
> Changelog:
> v3 -> v4:
> * Patchset rebased and tested on new HEAD of net-next (see hash above).
> v4 -> v5:
> * See per-patch changelog after ---.
> v5 -> v6:
> * Patchset rebased and tested on new HEAD of net-next (see hash above).
> * See per-patch changelog after ---.
> v6 -> v7:
> * Patchset rebased and tested on new HEAD of net-next (see hash above).
> * See per-patch changelog after ---.
> v7 -> v8:
> * Patchset rebased and tested on new HEAD of net-next (see hash above).
> * See per-patch changelog after ---.
> v8 -> v9:
> * Patchset rebased and tested on new HEAD of net-next (see hash above).
> * See per-patch changelog after ---.
>
> Arseniy Krasnov (4):
> vsock/virtio/vhost: read data from non-linear skb
> vsock/virtio: support to send non-linear skb
> vsock/virtio: non-linear skb handling for tap
> vsock/virtio: MSG_ZEROCOPY flag support
>
> drivers/vhost/vsock.c | 14 +-
> include/linux/virtio_vsock.h | 10 +
> .../events/vsock_virtio_transport_common.h | 12 +-
> net/vmw_vsock/virtio_transport.c | 92 +++++-
> net/vmw_vsock/virtio_transport_common.c | 307 ++++++++++++++----
> 5 files changed, 348 insertions(+), 87 deletions(-)
>
> --
> 2.25.1
next prev parent reply other threads:[~2023-09-18 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 13:09 [PATCH net-next v9 0/4] vsock/virtio/vhost: MSG_ZEROCOPY preparations Arseniy Krasnov
2023-09-16 13:09 ` [PATCH net-next v9 1/4] vsock/virtio/vhost: read data from non-linear skb Arseniy Krasnov
2023-09-16 13:09 ` [PATCH net-next v9 2/4] vsock/virtio: support to send " Arseniy Krasnov
2023-09-16 13:09 ` [PATCH net-next v9 3/4] vsock/virtio: non-linear skb handling for tap Arseniy Krasnov
2023-09-16 13:09 ` [PATCH net-next v9 4/4] vsock/virtio: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-09-18 14:50 ` Stefano Garzarella
2023-09-18 16:56 ` [PATCH net-next v9 0/4] vsock/virtio/vhost: MSG_ZEROCOPY preparations Arseniy Krasnov
2023-09-19 7:54 ` Stefano Garzarella
2023-09-19 7:50 ` Arseniy Krasnov
2023-09-19 13:19 ` Paolo Abeni
2023-09-19 13:35 ` Stefano Garzarella
2023-09-19 16:48 ` Arseniy Krasnov
2023-09-19 17:01 ` Arseniy Krasnov
2023-09-20 2:38 ` Michael S. Tsirkin
2023-09-20 11:06 ` Paolo Abeni
2023-09-18 17:27 ` Michael S. Tsirkin [this message]
2023-09-21 10:50 ` patchwork-bot+netdevbpf
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=20230918132726-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=avkrasnov@salutedevices.com \
--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=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;
as well as URLs for NNTP newsgroup(s).