[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210811151754.030a22a7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 11 Aug 2021 15:17:54 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jason Wang <jasowang@...hat.com>
Cc: mst@...hat.com, davem@...emloft.net,
virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, ivan@...stigetransportation.com,
xiangxia.m.yue@...il.com, willemb@...gle.com, edumazet@...gle.com
Subject: Re: [RFC PATCH] virtio-net: use NETIF_F_GRO_HW instead of
NETIF_F_LRO
On Wed, 11 Aug 2021 16:16:23 +0800 Jason Wang wrote:
> Try to fix this by using NETIF_F_GRO_HW instead so we're not
> guaranteed to be re-segmented as original.
This sentence may need rephrasing.
> Or we may want a new netdev
> feature like RX_GSO since the guest offloads for virtio-net is
> actually to receive GSO packet.
>
> Or we can try not advertise LRO is control guest offloads is not
> enabled. This solves the warning but will still slow down the traffic.
IMO gro-hw fits pretty well, patch looks good.
Powered by blists - more mailing lists