From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next 0/6] refactor MPTCP socket option handling
Date: Tue, 12 Aug 2025 16:17:15 +0800 [thread overview]
Message-ID: <cover.1754986557.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
This series restructures MPTCP socket option implementation to improve
maintainability and consistency. We introduce dedicated helper functions
for different option levels (SOL_SOCKET, SOL_IP, SOL_IPV6, SOL_TCP) and
propagation scopes (first subflow vs. all subflows), addressing current
code fragmentation.
Geliang Tang (6):
mptcp: add helper for setsockopt on first subflow only
mptcp: handle SOL_SOCKET options on first subflow only
mptcp: refactor IP socket option handling for first subflow
mptcp: extract IPv6 socket option handling for first subflow
mptcp: handle SOL_TCP options on all subflows
mptcp: handle IP socket options on all subflows
net/mptcp/sockopt.c | 215 +++++++++++++++++++++++++++++---------------
1 file changed, 145 insertions(+), 70 deletions(-)
--
2.48.1
next reply other threads:[~2025-08-12 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:17 Geliang Tang [this message]
2025-08-12 8:17 ` [PATCH mptcp-next 1/6] mptcp: add helper for setsockopt on first subflow only Geliang Tang
2025-08-12 8:17 ` [PATCH mptcp-next 2/6] mptcp: handle SOL_SOCKET options " Geliang Tang
2025-08-12 8:17 ` [PATCH mptcp-next 3/6] mptcp: refactor IP socket option handling for first subflow Geliang Tang
2025-08-12 8:17 ` [PATCH mptcp-next 4/6] mptcp: extract IPv6 " Geliang Tang
2025-08-12 8:17 ` [PATCH mptcp-next 5/6] mptcp: handle SOL_TCP options on all subflows Geliang Tang
2025-08-12 8:17 ` [PATCH mptcp-next 6/6] mptcp: handle IP socket " Geliang Tang
2025-08-12 10:39 ` [PATCH mptcp-next 0/6] refactor MPTCP socket option handling MPTCP CI
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.1754986557.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 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.