summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/gecko.py
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2025-02-19 12:42:52 +0300
committerDavid S. Miller <davem@davemloft.net>2025-02-19 12:42:52 +0300
commit8e7d925b95ab6a1deb9b91ea8fae0312875f8bf5 (patch)
tree4969865d72c48b0d48e3a78109a4cf4f45518871 /tools/perf/scripts/python/gecko.py
parentaefd232de5eb2e77e3fc58c56486c7fe7426a228 (diff)
parent685920920e3d5f68a8c50107b97747b0f8ce050f (diff)
downloadlinux-8e7d925b95ab6a1deb9b91ea8fae0312875f8bf5.tar.xz
Merge branch 'net-mana-big-tcp'
Shradha Gupta says: ==================== net: Enable Big TCP for MANA devices Allow the max gso/gro aggregated pkt size to go up to GSO_MAX_SIZE for MANA NIC. On Azure, this not possible without allowing the same for netvsc NIC (as the NICs are bonded together). Therefore, we use netif_set_tso_max_size() to set max aggregated pkt size to VF's tso_max_size for netvsc too, when the data path is switched over to the VF The first patch allows MANA to configure aggregated pkt size of up-to GSO_MAX_SIZE The second patch enables the same on the netvsc NIC, if the data path for the bonded NIC is switched to the VF --- Changes in v3 * Add ipv6_hopopt_jumbo_remove() while sending Big TCP packets --- Changes in v2 * Instead of using 'tcp segment' throughout the patch used the words 'aggregated pkt size' ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions