diff options
author | Alexander Duyck <alexanderduyck@fb.com> | 2022-05-13 11:33:57 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2022-05-16 10:18:55 +0100 |
commit | 7c4e983c4f3cf94fcd879730c6caa877e0768a4d (patch) | |
tree | 2cdd11e3c643ddf1bd7a15e5c8eecaf2e1d18f22 /lib/bitfield_kunit.c | |
parent | 89527be8d8d672773eeaec910118a6e84fb597e3 (diff) | |
download | linux-7c4e983c4f3cf94fcd879730c6caa877e0768a4d.tar.bz2 |
net: allow gso_max_size to exceed 65536
The code for gso_max_size was added originally to allow for debugging and
workaround of buggy devices that couldn't support TSO with blocks 64K in
size. The original reason for limiting it to 64K was because that was the
existing limits of IPv4 and non-jumbogram IPv6 length fields.
With the addition of Big TCP we can remove this limit and allow the value
to potentially go up to UINT_MAX and instead be limited by the tso_max_size
value.
So in order to support this we need to go through and clean up the
remaining users of the gso_max_size value so that the values will cap at
64K for non-TCPv6 flows. In addition we can clean up the GSO_MAX_SIZE value
so that 64K becomes GSO_LEGACY_MAX_SIZE and UINT_MAX will now be the upper
limit for GSO_MAX_SIZE.
v6: (edumazet) fixed a compile error if CONFIG_IPV6=n,
in a new sk_trim_gso_size() helper.
netif_set_tso_max_size() caps the requested TSO size
with GSO_MAX_SIZE.
Signed-off-by: Alexander Duyck <alexanderduyck@fb.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/bitfield_kunit.c')
0 files changed, 0 insertions, 0 deletions