-----Original Message-----
From: Cindy Lu <redacted>
Sent: Friday, July 18, 2025 1:29 AM
To: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
[off-list ref]; Wei Liu [off-list ref]; Dexuan Cui
[off-list ref]; Andrew Lunn [off-list ref]; David S.
Miller [off-list ref]; Eric Dumazet [off-list ref]; Jakub
Kicinski [off-list ref]; Paolo Abeni [off-list ref]; Simon Horman
[off-list ref]; Michael Kelley [off-list ref]; Shradha Gupta
[off-list ref]; Kees Cook [off-list ref]; Saurabh
Sengar [off-list ref]; Stanislav Fomichev [off-list ref];
Kuniyuki Iwashima [off-list ref]; Alexander Lobakin
[off-list ref]; Guillaume Nault [off-list ref]; Joe
Damato [off-list ref]; Ahmed Zaki [off-list ref]; open
list:Hyper-V/Azure CORE AND DRIVERS [off-list ref]; open
list:NETWORKING DRIVERS [off-list ref]; open list <linux-
kernel@vger.kernel.org>; lulu@redhat.com; jasowang@redhat.com
Subject: [EXTERNAL] [PATCH v2] netvsc: transfer lower device max tso size

From: Jason Wang <jasowang@redhat.com>

When netvsc is accelerated by the lower device, we can advertise the lower
device max tso size in order to get better performance.

One example is that when 802.3ad encap is enabled by netvsc, it has a lower max
tso size than 64K. This will lead to software segmentation of forwarding GSO
packet (e.g the one from VM/tap).

This patch help to recover the performance.

Signed-off-by: Jason Wang <jasowang@redhat.com>
Tested-by: Cindy Lu <redacted>
Signed-off-by: Cindy Lu <redacted>

Reviewed-by: Long Li <longli@microsoft.com>