[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f1198daa6d068c76b8ce692ad313698c34d0d1a3.camel@redhat.com>
Date: Wed, 20 Sep 2023 13:06:48 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>, Stefano Garzarella
<sgarzare@...hat.com>
Cc: Arseniy Krasnov <avkrasnov@...utedevices.com>, Stefan Hajnoczi
<stefanha@...hat.com>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Jason Wang
<jasowang@...hat.com>, Bobby Eshleman <bobby.eshleman@...edance.com>,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...rdevices.ru, oxffffaa@...il.com
Subject: Re: [PATCH net-next v9 0/4] vsock/virtio/vhost: MSG_ZEROCOPY
preparations
On Tue, 2023-09-19 at 22:38 -0400, Michael S. Tsirkin wrote:
> 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:
> >
> > > 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?
Yes, that was off-list co-ordination.
> 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.
Since there is agreement on that route, we will take it (likely
tomorrow).
Cheers,
Paolo
Powered by blists - more mailing lists