MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v2 0/3] Add TCP_MAXSEG socket option support
Date: Wed, 23 Apr 2025 17:40:39 +0800	[thread overview]
Message-ID: <cover.1745401025.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

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 (3):
  tcp: add tcp_sock_set_maxseg
  mptcp: add TCP_MAXSEG sockopt support
  selftests: mptcp: sockopt: add TCP_MAXSEG sockopt tests

 include/linux/tcp.h                           |  1 +
 net/ipv4/tcp.c                                | 24 ++++++++++++-------
 net/mptcp/protocol.h                          |  1 +
 net/mptcp/sockopt.c                           | 24 +++++++++++++++++++
 .../selftests/net/mptcp/mptcp_sockopt.c       | 22 +++++++++++++++++
 5 files changed, 63 insertions(+), 9 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-04-23  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23  9:40 Geliang Tang [this message]
2025-04-23  9:40 ` [PATCH mptcp-next v2 1/3] tcp: add tcp_sock_set_maxseg Geliang Tang
2025-04-29 11:17   ` Matthieu Baerts
2025-04-23  9:40 ` [PATCH mptcp-next v2 2/3] mptcp: add TCP_MAXSEG sockopt support Geliang Tang
2025-04-29 11:17   ` Matthieu Baerts
2025-04-23  9:40 ` [PATCH mptcp-next v2 3/3] selftests: mptcp: sockopt: add TCP_MAXSEG sockopt tests Geliang Tang
2025-04-29 11:17   ` Matthieu Baerts
2025-04-29 11:11 ` [PATCH mptcp-next v2 0/3] Add TCP_MAXSEG socket option support 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.1745401025.git.tanggeliang@kylinos.cn \
    --to=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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