Re: [PATCH v4 net-next 00/14] tcp: BIG TCP implementation
From: Alexander Duyck <hidden>
Date: 2022-03-15 17:20:50
On Tue, Mar 15, 2022 at 9:33 AM Eric Dumazet [off-list ref] wrote:
On Tue, Mar 15, 2022 at 9:17 AM Alexander Duyck [off-list ref] wrote:quoted
On Tue, Mar 15, 2022 at 8:50 AM Eric Dumazet [off-list ref] wrote:quoted
On Fri, Mar 11, 2022 at 9:13 AM Alexander H Duyck [off-list ref] wrote:quoted
On Wed, 2022-03-09 at 21:46 -0800, Eric Dumazet wrote:quoted
From: Eric Dumazet <edumazet@google.com> This series implements BIG TCP as presented in netdev 0x15: https://netdevconf.info/0x15/session.html?BIG-TCP Jonathan Corbet made a nice summary: https://lwn.net/Articles/884104/ Standard TSO/GRO packet limit is 64KB With BIG TCP, we allow bigger TSO/GRO packet sizes for IPv6 traffic. Note that this feature is by default not enabled, because it might break some eBPF programs assuming TCP header immediately follows IPv6 header. While tcpdump recognizes the HBH/Jumbo header, standard pcap filters are unable to skip over IPv6 extension headers. Reducing number of packets traversing networking stack usually improves performance, as shown on this experiment using a 100Gbit NIC, and 4K MTU. 'Standard' performance with current (74KB) limits. for i in {1..10}; do ./netperf -t TCP_RR -H iroa23 -- -r80000,80000 -O MIN_LATENCY,P90_LATENCY,P99_LATENCY,THROUGHPUT|tail -1; done 77 138 183 8542.19 79 143 178 8215.28 70 117 164 9543.39 80 144 176 8183.71 78 126 155 9108.47 80 146 184 8115.19 71 113 165 9510.96 74 113 164 9518.74 79 137 178 8575.04 73 111 171 9561.73 Now enable BIG TCP on both hosts. ip link set dev eth0 gro_ipv6_max_size 185000 gso_ipv6_max_size 185000 for i in {1..10}; do ./netperf -t TCP_RR -H iroa23 -- -r80000,80000 -O MIN_LATENCY,P90_LATENCY,P99_LATENCY,THROUGHPUT|tail -1; done 57 83 117 13871.38 64 118 155 11432.94 65 116 148 11507.62 60 105 136 12645.15 60 103 135 12760.34 60 102 134 12832.64 62 109 132 10877.68 58 82 115 14052.93 57 83 124 14212.58 57 82 119 14196.01 We see an increase of transactions per second, and lower latencies as well. v4: fix compile error for CONFIG_MLX5_CORE_IPOIB=y in mlx5 (Jakub) v3: Fixed a typo in RFC number (Alexander) Added Reviewed-by: tags from Tariq on mlx4/mlx5 parts. v2: Removed the MAX_SKB_FRAGS change, this belongs to a different series. Addressed feedback, for Alexander and nvidia folks.One concern with this patch set is the addition of all the max_size netdev attributes for tsov6, gsov6, and grov6. For the gsov6 and grov6 maxes I really think these make more sense as sysctl values since it feels more like a protocol change rather than a netdev specific one. If I recall correctly the addition of gso_max_size and gso_max_segs were added as a workaround for NICs that couldn't handle offloading frames larger than a certain size. This feels like increasing the scope of the workaround rather than adding a new feature. I didn't see the patch that went by for gro_max_size but I am not a fan of the way it was added since it would make more sense as a sysctl which controlled the stack instead of something that is device specific since as far as the device is concerned it received MTU size frames, and GRO happens above the device. I suppose it makes things symmetric with gso_max_size, but at the same time it isn't really a device specific attribute since the work happens in the stack above the device.We already have per device gso_max_size and gso_max_segs. GRO max size being per device is nice. There are cases where a host has multiple NIC, one of them being used for incoming traffic that needs to be forwarded. Maybe the changelog was not clear enough, but being able to lower gro_max_size is also a way to prevent frag_list being used, so that most NIC support TSO just fine.The point is gso_max_size and gso_max_segs were workarounds for devices. Basically they weren't added until it was found that specific NICs were having issues with segmenting frames either larger than a specific size or number of segments.These settings are used in our tests, when we want to precisely control size of TSO. There are not only used by drivers.
Yes, but what I am getting at is that for most drivers they are always set to 64K. I get that you are using them to test things, and you still could still use them after the change. All I am asking for is us not to fork them into 3 different things where each one has a specific protocol it supports.
quoted
I suppose we can keep gro_max_size in place if we are wanting to say that it ties back into the device. There may be some benefit there if we end up with some devices allocating skbs that can aggregate more segments than others, however in that case that seems more like a segment limit than a size limit. Maybe something like gro_max_segs would make more sense, or I suppose we end up with both eventually.quoted
quoted
Do we need to add the IPv6 specific version of the tso_ipv6_max_size? Could we instead just allow setting the gso_max_size value larger than 64K? Then it would just be a matter of having a protocol specific max size check to pull us back down to GSO_MAX_SIZE in the case of non-ipv6 frames.Not sure why adding attributes is an issue really, more flexibility seems better to me. One day, if someone adds LSOv2 to IPv4, I prefer being able to selectively turn on this support, after tests have concluded nothing broke. Having to turn off LSOv2 in emergency because of some bug in LSOv2 IPv4 implementation would be bad.You already have a means of turning off LSOv2 in the form of gso_max_size. Remember it was put there as a workaround for broken devices that couldn't fully support LSOv1. In my mind we would reuse the gso_max_size, and I suppose gro_max_size to control the GSO types supported by the device. If it is set for 64K or less then it only supports LSOv1, if it is set higher, then it can support GSOv2. I'm not sure it makes sense to split gso_max_size into two versions. If a device supports GSO larger than 64K then what is the point in having gso_max_size around when it will always be set to 64K because the device isn't broken. Otherwise we are going to end up creating a bunch of duplications.OK, but if a buggy user script is currently doing this: ip link set dev eth1 gso_max_size 70000 Old kernels were ignoring this request. Suddenly a new kernel comes, and user ends up with a broken setup.
That could already happen. Recall that I mentioned this was added as a workaround. So I would argue the code was already broken as there were devices that didn't support 64K and somehow we are allowing that. We probably need to add a function call to the drivers in order to control the setting of this as there are some drivers that cannot support the current limit of 64K. Then if it isn't set we just default to 64K. For the drivers that support larger we can then overwrite the function when setting up the jumbogram segmentation support value.
quoted
What I am getting at is that it would be nice to have a stack level control and then a device level control. The device control is there to say what size drivers support when segmenting, whereas the stack level control says if the protocol wants to try sending down frames larger than 64K. So essentially all non-IPv6 protocols will cap at 64K, whereas IPv6 can go beyond that with huge frames. Then you get the best of both worlds.Can you explain how the per ipvlan setting would be allowed ? To me sysctls are the old ways of controlling things, not mentioning adding more of them slow down netns creation and dismantles.
So what I am suggesting is splitting it into two pieces. One being gso_max_size which can be set to values larger than 64K if that is what we want to support on that device. The other being a protocol specific value where you can configure things to use a value greater than 64K if that is supported by the protocol. That way if there is a problem in the stack you can turn it off in one place, and if there is a problem in the device you can turn it off in another.