From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: hare@kernel.org, Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next 0/2] implement mptcp read_sock
Date: Thu, 22 May 2025 17:21:31 +0800 [thread overview]
Message-ID: <cover.1747904572.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
I have good news! I recently added MPTCP support to "NVME over TCP".
And my RFC patches are under review by NVME maintainer Hannes.
Replacing "NVME over TCP" with MPTCP is very simple. I used IPPROTO_MPTCP
instead of IPPROTO_TCP to create MPTCP sockets on both target and host
sides, these sockets are created in Kernel space.
nvmet_tcp_add_port:
ret = sock_create(port->addr.ss_family, SOCK_STREAM,
IPPROTO_MPTCP, &port->sock);
nvme_tcp_alloc_queue:
ret = sock_create_kern(current->nsproxy->net_ns,
ctrl->addr.ss_family, SOCK_STREAM,
IPPROTO_MPTCP, &queue->sock);
nvme_tcp_try_recv() needs to call .read_sock interface of struct
proto_ops, but it is not implemented in MPTCP. So I implemented it
with reference to __mptcp_recvmsg_mskq().
Since the NVME part patches are still under reviewing, I only send the
MPTCP part patches in this set to MPTCP ML for your opinions.
Thanks,
-Geliang
Geliang Tang (2):
mptcp: use sk_eat_skb in recvmsg_mskq
mptcp: implement .read_sock
net/mptcp/protocol.c | 57 ++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 55 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2025-05-22 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 9:21 Geliang Tang [this message]
2025-05-22 9:21 ` [PATCH mptcp-next 1/2] mptcp: use sk_eat_skb in recvmsg_mskq Geliang Tang
2025-05-22 9:21 ` [PATCH mptcp-next 2/2] mptcp: implement .read_sock Geliang Tang
2025-05-23 15:04 ` Matthieu Baerts
2025-05-22 10:42 ` [PATCH mptcp-next 0/2] implement mptcp read_sock 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.1747904572.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=hare@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.