From: Alexander Duyck <alexander.duyck@gmail.com>
To: edumazet@google.com
Cc: alexander.duyck@gmail.com, davem@davemloft.net,
eric.dumazet@gmail.com, kuba@kernel.org, lixiaoyan@google.com,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: [PATCH 0/2] Replacements for patches 2 and 7 in Big TCP series
Date: Mon, 09 May 2022 11:17:24 -0700 [thread overview]
Message-ID: <165212006050.5729.9059171256935942562.stgit@localhost.localdomain> (raw)
In-Reply-To: <CANn89iJW9GCUWBRtutv1=KHYn0Gpj8ue6bGWMO9LLGXqvgWhmQ@mail.gmail.com>
This patch set is meant to replace patches 2 and 7 in the Big TCP series.
From what I can tell it looks like they can just be dropped from the series
and these two patches could be added to the end of the set.
With these patches I have verified that both the loopback and mlx5 drivers
are able to send and receive IPv6 jumbogram frames when configured with a
g[sr]o_max_size value larger than 64K.
Note I had to make one minor change to iproute2 to allow submitting a value
larger than 64K in that I removed a check that was limiting gso_max_size to
no more than 65536. In the future an alternative might be to fetch the
IFLA_TSO_MAX_SIZE attribute if it exists and use that, and if not then use
65536 as the limit.
---
Alexander Duyck (2):
net: Allow gso_max_size to exceed 65536
net: Allow gro_max_size to exceed 65536
drivers/net/ethernet/amd/xgbe/xgbe.h | 3 ++-
drivers/net/ethernet/mellanox/mlx5/core/en_rx.c | 2 +-
drivers/net/ethernet/sfc/ef100_nic.c | 3 ++-
drivers/net/ethernet/sfc/falcon/tx.c | 3 ++-
drivers/net/ethernet/sfc/tx_common.c | 3 ++-
drivers/net/ethernet/synopsys/dwc-xlgmac.h | 3 ++-
drivers/net/hyperv/rndis_filter.c | 2 +-
drivers/scsi/fcoe/fcoe.c | 2 +-
include/linux/netdevice.h | 6 ++++--
include/net/ipv6.h | 2 +-
net/bpf/test_run.c | 2 +-
net/core/dev.c | 7 ++++---
net/core/gro.c | 8 ++++++++
net/core/rtnetlink.c | 10 +---------
net/core/sock.c | 4 ++++
net/ipv4/tcp_bbr.c | 2 +-
net/ipv4/tcp_output.c | 2 +-
net/sctp/output.c | 3 ++-
18 files changed, 40 insertions(+), 27 deletions(-)
--
next prev parent reply other threads:[~2022-05-09 18:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:30 [PATCH v4 net-next 00/12] tcp: BIG TCP implementation Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 01/12] net: add IFLA_TSO_{MAX_SIZE|SEGS} attributes Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 02/12] ipv6: add IFLA_GSO_IPV6_MAX_SIZE Eric Dumazet
2022-05-06 20:48 ` Alexander H Duyck
2022-05-06 21:20 ` Eric Dumazet
2022-05-06 21:37 ` Alexander Duyck
2022-05-06 21:50 ` Eric Dumazet
2022-05-06 22:16 ` Alexander Duyck
2022-05-06 22:25 ` Eric Dumazet
2022-05-06 22:26 ` Jakub Kicinski
2022-05-06 22:46 ` Alexander Duyck
2022-05-06 15:30 ` [PATCH v4 net-next 03/12] tcp_cubic: make hystart_ack_delay() aware of BIG TCP Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 04/12] ipv6: add struct hop_jumbo_hdr definition Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 05/12] ipv6/gso: remove temporary HBH/jumbo header Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 06/12] ipv6/gro: insert " Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 07/12] ipv6: add IFLA_GRO_IPV6_MAX_SIZE Eric Dumazet
2022-05-06 21:06 ` Alexander H Duyck
2022-05-06 21:22 ` Eric Dumazet
2022-05-06 22:01 ` Alexander Duyck
2022-05-06 22:08 ` Eric Dumazet
2022-05-09 18:17 ` Alexander Duyck [this message]
2022-05-09 18:17 ` [PATCH 1/2] net: Allow gso_max_size to exceed 65536 Alexander Duyck
2022-05-09 18:17 ` [PATCH 2/2] net: Allow gro_max_size " Alexander Duyck
2022-05-09 18:54 ` [PATCH 0/2] Replacements for patches 2 and 7 in Big TCP series Eric Dumazet
2022-05-09 20:21 ` Alexander H Duyck
2022-05-09 20:31 ` Eric Dumazet
2022-05-09 21:05 ` Alexander Duyck
2022-05-06 15:30 ` [PATCH v4 net-next 08/12] ipv6: Add hop-by-hop header to jumbograms in ip6_output Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 09/12] net: loopback: enable BIG TCP packets Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 10/12] veth: " Eric Dumazet
2022-05-06 22:33 ` Jakub Kicinski
2022-05-06 15:30 ` [PATCH v4 net-next 11/12] mlx4: support " Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 12/12] mlx5: " Eric Dumazet
2022-05-06 22:34 ` Jakub Kicinski
2022-05-07 0:32 ` Eric Dumazet
2022-05-07 1:54 ` Jakub Kicinski
2022-05-07 1:54 ` Jakub Kicinski
2022-05-07 2:10 ` Eric Dumazet
2022-05-07 2:37 ` Jakub Kicinski
2022-05-07 2:43 ` Eric Dumazet
2022-05-07 7:16 ` Kees Cook
2022-05-07 7:23 ` Kees Cook
2022-05-07 6:57 ` Kees Cook
2022-05-07 7:46 ` Kees Cook
2022-05-07 11:19 ` Eric Dumazet
2022-05-09 8:05 ` David Laight
2022-05-09 23:20 ` Kees Cook
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=165212006050.5729.9059171256935942562.stgit@localhost.localdomain \
--to=alexander.duyck@gmail.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