From: "Michael S. Tsirkin" <mst@redhat•com>
To: Stefano Garzarella <sgarzare@redhat•com>
Cc: Paolo Abeni <pabeni@redhat•com>,
Arseniy Krasnov <avkrasnov@salutedevices•com>,
Stefan Hajnoczi <stefanha@redhat•com>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>,
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: Tue, 19 Sep 2023 22:38:33 -0400 [thread overview]
Message-ID: <20230919223700-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <hq67e2b3ljfjikvbaneczdve3fzg3dl5ziyc7xtujyqesp6dzm@fh5nqkptpb4n>
On Tue, Sep 19, 2023 at 03:35:51PM +0200, Stefano Garzarella wrote:
> On Tue, Sep 19, 2023 at 03:19:54PM +0200, Paolo Abeni wrote:
> > On Tue, 2023-09-19 at 09:54 +0200, Stefano Garzarella wrote:
> > > On Mon, Sep 18, 2023 at 07:56:00PM +0300, Arseniy Krasnov wrote:
> > > > Hi Stefano,
> > > >
> > > > thanks for review! So when this patchset will be merged to net-next,
> > > > I'll start sending next part of MSG_ZEROCOPY patchset, e.g. AF_VSOCK +
> > > > Documentation/ patches.
> > >
> > > Ack, if it is not a very big series, maybe better to include also the
> > > tests so we can run them before merge the feature.
> >
> > I understand that at least 2 follow-up series are waiting for this, one
> > of them targeting net-next and the bigger one targeting the virtio
> > tree. Am I correct?
>
> IIUC the next series will touch only the vsock core
> (net/vmw_vsock/af_vsock.c), tests, and documentation.
>
> The virtio part should be fully covered by this series.
>
> @Arseniy feel free to correct me!
>
> >
> > DaveM suggests this should go via the virtio tree, too. Any different
> > opinion?
>
> For this series should be fine, I'm not sure about the next series.
> Merging this with the virtio tree, then it forces us to do it for
> followup as well right?
>
> In theory followup is more on the core, so better with net-next, but
> it's also true that for now only virtio transports support it, so it
> might be okay to continue with virtio.
>
> @Michael WDYT?
>
> Thanks,
> Stefano
I didn't get DaveM's mail - was this off-list?
I think net-next is easier because the follow up belongs in net-next.
But if not I can take it, sure. Let me know.
--
MST
next prev parent reply other threads:[~2023-09-20 2:38 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 [this message]
2023-09-20 11:06 ` Paolo Abeni
2023-09-18 17:27 ` Michael S. Tsirkin
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=20230919223700-mutt-send-email-mst@kernel.org \
--to=mst@redhat$(echo .)com \
--cc=avkrasnov@salutedevices$(echo .)com \
--cc=bobby.eshleman@bytedance$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=kernel@sberdevices$(echo .)ru \
--cc=kuba@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oxffffaa@gmail$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=sgarzare@redhat$(echo .)com \
--cc=stefanha@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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