diff options
author | Shradha Gupta <shradhagupta@linux.microsoft.com> | 2025-02-17 06:42:42 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2025-02-19 12:42:52 +0300 |
commit | 685920920e3d5f68a8c50107b97747b0f8ce050f (patch) | |
tree | 4969865d72c48b0d48e3a78109a4cf4f45518871 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 27315836f4bcc8e4879d50dfc1fa6eb41e7952ef (diff) | |
download | linux-685920920e3d5f68a8c50107b97747b0f8ce050f.tar.xz |
hv_netvsc: Use VF's tso_max_size value when data path is VF
On Azure, increasing VF's gso/gro packet size to up-to GSO_MAX_SIZE
is not possible without allowing the same for netvsc NIC
(as the NICs are bonded together). For bonded NICs, the min of the max
aggregated pkt size of the members is propagated in the stack.
Therefore, we use netif_set_tso_max_size() to set max aggregated pkt size
to VF's packet size for netvsc too, when the data path is switched over
to the VF
Tested on azure env with Accelerated Networking enabled and disabled.
Signed-off-by: Shradha Gupta <shradhagupta@linux.microsoft.com>
Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions