From: Alexander H Duyck <alexander.duyck@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev <netdev@vger.kernel.org>,
Alexander Duyck <alexanderduyck@fb.com>,
Coco Li <lixiaoyan@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH v6 net-next 00/13] tcp: BIG TCP implementation
Date: Tue, 10 May 2022 12:49:02 -0700 [thread overview]
Message-ID: <d7d32ee0ce420233d641fc9fb7cef27b0ee271c3.camel@gmail.com> (raw)
In-Reply-To: <20220510033219.2639364-1-eric.dumazet@gmail.com>
On Mon, 2022-05-09 at 20:32 -0700, Eric Dumazet wrote:
> 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_max_size 185000 gso_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.
>
> v6: fix a compilation error for CONFIG_IPV6=n in
> "net: allow gso_max_size to exceed 65536", reported by kernel bots.
>
> v5: Replaced two patches (that were adding new attributes) with patches
> from Alexander Duyck. Idea is to reuse existing gso_max_size/gro_max_size
>
> v4: Rebased on top of Jakub series (Merge branch 'tso-gso-limit-split')
> max_tso_size is now family independent.
>
> 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.
>
>
> Alexander Duyck (2):
> net: allow gso_max_size to exceed 65536
> net: allow gro_max_size to exceed 65536
>
> Coco Li (2):
> ipv6: Add hop-by-hop header to jumbograms in ip6_output
> mlx5: support BIG TCP packets
>
> Eric Dumazet (9):
> net: add IFLA_TSO_{MAX_SIZE|SEGS} attributes
> net: limit GSO_MAX_SIZE to 524280 bytes
> tcp_cubic: make hystart_ack_delay() aware of BIG TCP
> ipv6: add struct hop_jumbo_hdr definition
> ipv6/gso: remove temporary HBH/jumbo header
> ipv6/gro: insert temporary HBH/jumbo header
> net: loopback: enable BIG TCP packets
> veth: enable BIG TCP packets
> mlx4: support BIG TCP packets
Looked over the changes to my patches and they all look good (sorry for
not catching that myself). This approach addresses all the concerns I
had.
For the series:
Acked-by: Alexander Duyck <alexanderduyck@fb.com>
prev parent reply other threads:[~2022-05-10 19:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 3:32 [PATCH v6 net-next 00/13] tcp: BIG TCP implementation Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 01/13] net: add IFLA_TSO_{MAX_SIZE|SEGS} attributes Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 02/13] net: allow gso_max_size to exceed 65536 Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 03/13] net: limit GSO_MAX_SIZE to 524280 bytes Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 04/13] tcp_cubic: make hystart_ack_delay() aware of BIG TCP Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 05/13] ipv6: add struct hop_jumbo_hdr definition Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 06/13] ipv6/gso: remove temporary HBH/jumbo header Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 07/13] ipv6/gro: insert " Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 08/13] net: allow gro_max_size to exceed 65536 Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 09/13] ipv6: Add hop-by-hop header to jumbograms in ip6_output Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 10/13] net: loopback: enable BIG TCP packets Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 11/13] veth: " Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 12/13] mlx4: support " Eric Dumazet
2022-05-10 3:32 ` [PATCH v6 net-next 13/13] mlx5: " Eric Dumazet
2022-05-12 8:40 ` Saeed Mahameed
2022-05-12 9:02 ` Paolo Abeni
2022-05-13 4:29 ` Saeed Mahameed
2022-05-13 4:34 ` Eric Dumazet
2022-05-13 5:49 ` Saeed Mahameed
2022-05-13 13:05 ` Eric Dumazet
2022-05-13 17:04 ` Jakub Kicinski
2022-05-13 17:12 ` Eric Dumazet
2022-05-10 19:49 ` Alexander H Duyck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7d32ee0ce420233d641fc9fb7cef27b0ee271c3.camel@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).