From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang@kernel.org>
Subject: [PATCH mptcp-next v3 0/2] Add TCP_MAXSEG socket option support
Date: Wed, 30 Apr 2025 13:49:43 +0800 [thread overview]
Message-ID: <cover.1745991978.git.geliang@kernel.org> (raw)
v3:
- drop "EXPORT_SYMBOL(tcp_sock_set_maxseg)" as Matt suggested.
- use mptcp_getsockopt_first_sf_only instead of mptcp_put_int_option.
- drop selftest
- add a packetdrill test.
v2:
- add a new helper tcp_sock_set_maxseg.
- add maxseg member of struct mptcp_sock.
- add mptcp_setsockopt_all_subflows helper.
- invoke mptcp_setsockopt_all_subflows under the msk socket lock.
- drop mptcp_getsockopt_sol_tcp_maxseg, use mptcp_put_int_option
instead.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/515
Geliang Tang (2):
tcp: add tcp_sock_set_maxseg
mptcp: add TCP_MAXSEG sockopt support
include/linux/tcp.h | 1 +
net/ipv4/tcp.c | 23 ++++++++++++++---------
net/mptcp/protocol.h | 1 +
net/mptcp/sockopt.c | 25 +++++++++++++++++++++++++
4 files changed, 41 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-30 5:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 5:49 Geliang Tang [this message]
2025-04-30 5:49 ` [PATCH mptcp-next v3 1/2] tcp: add tcp_sock_set_maxseg Geliang Tang
2025-04-30 5:49 ` [PATCH mptcp-next v3 2/2] mptcp: add TCP_MAXSEG sockopt support Geliang Tang
2025-04-30 8:55 ` Matthieu Baerts
2025-05-06 2:36 ` Geliang Tang
2025-04-30 9:06 ` Matthieu Baerts
2025-04-30 5:49 ` [PATCH mptcp-next] mptcp: validate maxseg sockopt Geliang Tang
2025-04-30 7:15 ` MPTCP CI
2025-04-30 7:31 ` MPTCP CI
2025-04-30 9:42 ` Matthieu Baerts
2025-05-08 7:21 ` Geliang Tang
2025-05-08 9:05 ` Matthieu Baerts
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=cover.1745991978.git.geliang@kernel.org \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.