From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next 0/6] Fix socket options used by NVMe over MPTCP
Date: Sat, 25 Jul 2026 21:13:37 +0800 [thread overview]
Message-ID: <cover.1784985085.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
NVMe over MPTCP relies on SO_LINGER, SO_PRIORITY, SO_REUSEADDR, TCP_SYNCNT,
TCP_NODELAY, IP_TOS, and SO_BINDTODEVICE. This series contains fixes to make
all of them work correctly. Patch 4 is a cleanup needed by patch 5. Patch 6
adds a selftest to cover these options.
Geliang Tang (6):
mptcp: copy the subflow's rcv_tos to the msk on accept
mptcp: don't reset dst when setting default 0 tos
mptcp: inherit sk_reuse on subflow creation
mptcp: handle TCP_MAXSEG getsockopt in common case
mptcp: add TCP_SYNCNT setsockopt/getsockopt
selftests: mptcp: sockopt: cover LINGER REUSEADDR PRIORITY NODELAY
SYNCNT
net/mptcp/protocol.c | 2 +
net/mptcp/sockopt.c | 28 ++++-
.../selftests/net/mptcp/mptcp_sockopt.c | 116 ++++++++++++++++++
3 files changed, 141 insertions(+), 5 deletions(-)
--
2.53.0
next reply other threads:[~2026-07-25 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 13:13 Geliang Tang [this message]
2026-07-25 13:13 ` [PATCH mptcp-next 1/6] mptcp: copy the subflow's rcv_tos to the msk on accept Geliang Tang
2026-07-25 13:13 ` [PATCH mptcp-next 2/6] mptcp: don't reset dst when setting default 0 tos Geliang Tang
2026-07-25 13:13 ` [PATCH mptcp-next 3/6] mptcp: inherit sk_reuse on subflow creation Geliang Tang
2026-07-25 13:13 ` [PATCH mptcp-next 4/6] mptcp: handle TCP_MAXSEG getsockopt in common case Geliang Tang
2026-07-25 13:13 ` [PATCH mptcp-next 5/6] mptcp: add TCP_SYNCNT setsockopt/getsockopt Geliang Tang
2026-07-25 13:13 ` [PATCH mptcp-next 6/6] selftests: mptcp: sockopt: cover LINGER REUSEADDR PRIORITY NODELAY SYNCNT Geliang Tang
2026-07-25 14:17 ` [PATCH mptcp-next 0/6] Fix socket options used by NVMe over MPTCP 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.1784985085.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