public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev, nilay@linux.ibm.com, ming.lei@redhat.com,
	hare@suse.de
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [RFC mptcp-next v4 0/8] NVME over MPTCP
Date: Thu,  5 Mar 2026 12:05:18 +0800	[thread overview]
Message-ID: <cover.1772683110.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v4:
 - a new patch to set nvme iopolicy as Nilay suggested.
 - resend all set to trigger AI review.

v3:
 - update the implementation of sock_set_nodelay: originally it only set
the first subflow, but now it sets every subflow.
 - use sk_is_msk helper in this set.
 - update the selftest to perform testing under a multi-interface
environment.

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
been merged into net-next recently.

Depends on: mptcp: fix stall because of data_ready
Without this fix, NVMe-over-MPTCP test will probabilistically fail.
Based-on: <20260228011511.440437-1-gang.yan@linux.dev>

Geliang Tang (8):
  mptcp: add sk_is_msk helper
  nvmet-tcp: add mptcp support
  nvme-tcp: add mptcp support
  mptcp: add sock_set_nodelay
  mptcp: add sock_set_reuseaddr
  mptcp: add sock_set_syncnt
  selftests: mptcp: add NVMe-over-MPTCP test
  selftests: mptcp: nvme: set iopolicy

 drivers/nvme/host/tcp.c                       |  26 ++-
 drivers/nvme/target/configfs.c                |   1 +
 drivers/nvme/target/tcp.c                     |  38 +++-
 include/linux/nvme.h                          |   1 +
 include/net/mptcp.h                           |  27 +++
 net/mptcp/protocol.c                          |  51 +++++
 tools/testing/selftests/net/mptcp/config      |   7 +
 .../testing/selftests/net/mptcp/mptcp_nvme.sh | 187 ++++++++++++++++++
 8 files changed, 335 insertions(+), 3 deletions(-)
 create mode 100755 tools/testing/selftests/net/mptcp/mptcp_nvme.sh

-- 
2.53.0


             reply	other threads:[~2026-03-05  4:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  4:05 Geliang Tang [this message]
2026-03-05  4:05 ` [RFC mptcp-next v4 1/8] mptcp: add sk_is_msk helper Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 2/8] nvmet-tcp: add mptcp support Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 3/8] nvme-tcp: " Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 4/8] mptcp: add sock_set_nodelay Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 5/8] mptcp: add sock_set_reuseaddr Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 6/8] mptcp: add sock_set_syncnt Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 7/8] selftests: mptcp: add NVMe-over-MPTCP test Geliang Tang
2026-03-05  4:05 ` [RFC mptcp-next v4 8/8] selftests: mptcp: nvme: set iopolicy Geliang Tang
2026-03-05  6:13 ` [RFC mptcp-next v4 0/8] 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.1772683110.git.tanggeliang@kylinos.cn \
    --to=geliang@kernel.org \
    --cc=hare@suse.de \
    --cc=ming.lei@redhat.com \
    --cc=mptcp@lists.linux.dev \
    --cc=nilay@linux.ibm.com \
    --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