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 0/6] NVME over MPTCP
Date: Fri, 7 Nov 2025 11:37:31 +0800 [thread overview]
Message-ID: <cover.1762485513.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
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.
Currently, the biggest problem I'm facing is in Patch 6, where I'm unsure how
to handle MSG_DONTWAIT. That's why I've sent this RFC version to get your
opinions.
Based-on: <cover.1761198660.git.geliang@kernel.org>
Geliang Tang (6):
mptcp: add sock_set_nodelay
nvmet-tcp: add mptcp support
mptcp: add sock_set_reuseaddr
nvme-tcp: add mptcp support
selftests: mptcp: add NVMe-over-MPTCP test
nvmet-tcp: clear MSG_DONTWAIT for MPTCP (TODO: HELP WANTED)
drivers/nvme/host/tcp.c | 27 ++++++++-
drivers/nvme/target/configfs.c | 1 +
drivers/nvme/target/tcp.c | 54 ++++++++++++++++--
include/linux/nvme.h | 1 +
include/net/mptcp.h | 8 +++
net/mptcp/protocol.c | 33 +++++++++++
tools/testing/selftests/net/mptcp/config | 7 +++
.../testing/selftests/net/mptcp/mptcp_nvme.sh | 57 +++++++++++++++++++
8 files changed, 180 insertions(+), 8 deletions(-)
create mode 100755 tools/testing/selftests/net/mptcp/mptcp_nvme.sh
--
2.43.0
next reply other threads:[~2025-11-07 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:37 Geliang Tang [this message]
2025-11-07 3:37 ` [RFC mptcp-next 1/6] mptcp: add sock_set_nodelay Geliang Tang
2025-11-07 3:37 ` [RFC mptcp-next 2/6] nvmet-tcp: add mptcp support Geliang Tang
2025-11-07 3:37 ` [RFC mptcp-next 3/6] mptcp: add sock_set_reuseaddr Geliang Tang
2025-11-07 3:37 ` [RFC mptcp-next 4/6] nvme-tcp: add mptcp support Geliang Tang
2025-11-07 3:37 ` [RFC mptcp-next 5/6] selftests: mptcp: add NVMe-over-MPTCP test Geliang Tang
2025-11-07 3:37 ` [RFC mptcp-next 6/6] nvmet-tcp: clear MSG_DONTWAIT for MPTCP (TODO: HELP WANTED) Geliang Tang
2025-11-26 9:42 ` Geliang Tang
2025-11-07 4:15 ` [RFC mptcp-next 0/6] NVME over MPTCP MPTCP CI
2025-11-07 6:13 ` 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.1762485513.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