[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <uhrf5ctkvc6ic7frpfndtdf66u66lonhfgane7bigb72damukf@mjavswunu7ve>
Date: Tue, 6 Aug 2024 18:45:51 +0200
From: Stefano Garzarella <sgarzare@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: luigi.leonardi@...look.com, mst@...hat.com,
Stefan Hajnoczi <stefanha@...hat.com>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, kvm@...r.kernel.org,
virtualization@...ts.linux.dev, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Marco Pinna <marco.pinn95@...il.com>
Subject: Re: [PATCH net-next v4 0/2] vsock: avoid queuing on intermediate
queue if possible
On Tue, Aug 06, 2024 at 09:02:57AM GMT, Jakub Kicinski wrote:
>On Mon, 5 Aug 2024 10:39:23 +0200 Stefano Garzarella wrote:
>> this series is marked as "Not Applicable" for the net-next tree:
>> https://patchwork.kernel.org/project/netdevbpf/patch/20240730-pinna-v4-2-5c9179164db5@outlook.com/
>>
>> Actually this is more about the virtio-vsock driver, so can you queue
>> this on your tree?
>
>We can revive it in our patchwork, too, if that's easier.
That's perfectly fine with me, if Michael hasn't already queued it.
>Not entirely sure why it was discarded, seems borderline.
>
Yes, even to me it's not super clear when to expect net and when virtio.
Usually the other vsock transports (VMCI and HyperV) go with net, so
virtio-vsock is a bit of an exception.
I don't have any particular preferences, so how it works best for you
and Michael is fine with me.
Thanks,
Stefano
Powered by blists - more mailing lists