From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev, hare@suse.de, hare@kernel.org
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [RFC mptcp-next v2 0/7] NVME over MPTCP
Date: Wed, 26 Nov 2025 18:39:57 +0800 [thread overview]
Message-ID: <cover.1764152990.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v2:
- Patch 1 fixes the timeout issue reported in v1, thanks to Paolo and Gang
Yan for their help.
- Patch 5 implements an MPTCP-specific sock_set_syncnt helper.
This series (previously named "MPTCP support to 'NVME over TCP'") had three
RFC versions sent to Hannes in May, with subsequent revisions based on his
input. Following that, I initiated the process of upstreaming the dependent
"implement mptcp read_sock" series to the main MPTCP repository, which has
now largely taken shape.
Depends on: implement mptcp read_sock, v14
Based-on: <cover.1763974740.git.tanggeliang@kylinos.cn>
Geliang Tang (7):
mptcp: allow overridden write_space to be invoked
mptcp: add sock_set_reuseaddr
mptcp: add sock_set_nodelay
nvmet-tcp: add mptcp support
mptcp: add sock_set_syncnt
nvme-tcp: add mptcp support
selftests: mptcp: add NVMe-over-MPTCP test
drivers/nvme/host/tcp.c | 28 +++-
drivers/nvme/target/configfs.c | 1 +
drivers/nvme/target/tcp.c | 38 +++++-
include/linux/nvme.h | 1 +
include/net/mptcp.h | 15 +++
net/mptcp/protocol.c | 52 ++++++++
net/mptcp/protocol.h | 2 +-
tools/testing/selftests/net/mptcp/config | 7 +
.../testing/selftests/net/mptcp/mptcp_nvme.sh | 120 ++++++++++++++++++
9 files changed, 260 insertions(+), 4 deletions(-)
create mode 100755 tools/testing/selftests/net/mptcp/mptcp_nvme.sh
--
2.51.0
next reply other threads:[~2025-11-26 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:39 Geliang Tang [this message]
2025-11-26 10:39 ` [RFC mptcp-next v2 1/7] mptcp: allow overridden write_space to be invoked Geliang Tang
2025-11-26 10:39 ` [RFC mptcp-next v2 2/7] mptcp: add sock_set_reuseaddr Geliang Tang
2025-11-26 10:40 ` [RFC mptcp-next v2 3/7] mptcp: add sock_set_nodelay Geliang Tang
2025-11-26 10:40 ` [RFC mptcp-next v2 4/7] nvmet-tcp: add mptcp support Geliang Tang
2025-11-26 10:40 ` [RFC mptcp-next v2 5/7] mptcp: add sock_set_syncnt Geliang Tang
2025-11-26 10:40 ` [RFC mptcp-next v2 6/7] nvme-tcp: add mptcp support Geliang Tang
2025-11-26 10:40 ` [RFC mptcp-next v2 7/7] selftests: mptcp: add NVMe-over-MPTCP test Geliang Tang
2025-11-26 12:29 ` [RFC mptcp-next v2 0/7] 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.1764152990.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--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