linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
	 Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	 Neal Cardwell <ncardwell@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	 David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	 "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
	 moyuanhao <moyuanhao3676@163.com>,
	Geliang Tang <geliang@kernel.org>
Subject: [PATCH net-next 0/4] mptcp: add TCP_MAXSEG sockopt support
Date: Wed, 16 Jul 2025 12:28:02 +0200	[thread overview]
Message-ID: <20250716-net-next-mptcp-tcp_maxseg-v1-0-548d3a5666f6@kernel.org> (raw)

The TCP_MAXSEG socket option was not supported by MPTCP, mainly because
it has never been requested before. But there are still valid use-cases,
e.g. with HAProxy.

- Patch 1 is a small cleanup patch in the MPTCP sockopt file.

- Patch 2 expose some code from TCP, to avoid duplicating it in MPTCP.

- Patch 3 adds TCP_MAXSEG sockopt support in MPTCP.

- Patch 4 is not related to the others, it fixes a typo in a comment.

Note that the new TCP_MAXSEG sockopt support has been validated by a new
packetdrill script on the MPTCP CI:

  https://github.com/multipath-tcp/packetdrill/pull/161

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Geliang Tang (3):
      mptcp: sockopt: drop redundant tcp_getsockopt
      tcp: add tcp_sock_set_maxseg
      mptcp: add TCP_MAXSEG sockopt support

moyuanhao (1):
      mptcp: fix typo in a comment

 include/linux/tcp.h  |  1 +
 net/ipv4/tcp.c       | 23 ++++++++++++++---------
 net/mptcp/protocol.c |  2 +-
 net/mptcp/protocol.h |  1 +
 net/mptcp/sockopt.c  | 33 +++++++++++++++++++++++++++++----
 5 files changed, 46 insertions(+), 14 deletions(-)
---
base-commit: c3886ccaadf8fdc2c91bfbdcdca36ccdc6ef8f70
change-id: 20250716-net-next-mptcp-tcp_maxseg-e7702891080d

Best regards,
-- 
Matthieu Baerts (NGI0) <matttbe@kernel.org>


             reply	other threads:[~2025-07-16 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 10:28 Matthieu Baerts (NGI0) [this message]
2025-07-16 10:28 ` [PATCH net-next 1/4] mptcp: sockopt: drop redundant tcp_getsockopt Matthieu Baerts (NGI0)
2025-07-16 10:28 ` [PATCH net-next 2/4] tcp: add tcp_sock_set_maxseg Matthieu Baerts (NGI0)
2025-07-17  1:25   ` Geliang Tang
2025-07-16 10:28 ` [PATCH net-next 3/4] mptcp: add TCP_MAXSEG sockopt support Matthieu Baerts (NGI0)
2025-07-16 10:28 ` [PATCH net-next 4/4] mptcp: fix typo in a comment Matthieu Baerts (NGI0)

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=20250716-net-next-mptcp-tcp_maxseg-v1-0-548d3a5666f6@kernel.org \
    --to=matttbe@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=moyuanhao3676@163.com \
    --cc=mptcp@lists.linux.dev \
    --cc=ncardwell@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).