From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next 0/4] mptcp: add MSG_ZEROCOPY support
Date: Sat, 11 Jul 2026 21:07:48 +0800 [thread overview]
Message-ID: <cover.1783774784.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
This series adds MSG_ZEROCOPY support for MPTCP sockets, allowing
userspace to transmit data without intermediate kernel copies, and
provides corresponding selftests to exercise the new path.
The first patch is a small cleanup that introduces a local 'tp'
variable in mptcp_sendmsg_frag() to avoid repeated tcp_sk()
dereferencing, preparing for the subsequent zero-copy changes.
The second patch implements the core MSG_ZEROCOPY support. The design
follows TCP's reference-counting model, with a single ubuf_info per
sendmsg tracked by three reference buckets: one held by sendmsg itself,
one per MPTCP dfrag in the retransmission queue, and one per subflow
skb. Completion is reported only after all bytes are acknowledged at
both MPTCP and subflow levels. The feature is silently downgraded to
regular copy in cases where zero-copy cannot be safely performed
(MSG_FASTOPEN, fallback mode, or memory pressure).
The third and fourth patches add a new 'zerocopy' I/O mode to the
mptcp_connect selftest, and a wrapper script to run it as part of the
regular test suite, ensuring the zero-copy path is exercised in CI.
Geliang Tang (4):
mptcp: use local variable tp in sendmsg_frag
mptcp: add msg zerocopy support
selftests: mptcp: connect: add zerocopy io mode
selftests: mptcp: connect: cover zerocopy mode
net/mptcp/protocol.c | 104 ++++++++++++++++--
net/mptcp/protocol.h | 1 +
tools/testing/selftests/net/mptcp/Makefile | 1 +
.../selftests/net/mptcp/mptcp_connect.c | 63 ++++++++++-
.../net/mptcp/mptcp_connect_zerocopy.sh | 5 +
5 files changed, 163 insertions(+), 11 deletions(-)
create mode 100755 tools/testing/selftests/net/mptcp/mptcp_connect_zerocopy.sh
--
2.53.0
next reply other threads:[~2026-07-11 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 13:07 Geliang Tang [this message]
2026-07-11 13:07 ` [PATCH mptcp-next 1/4] mptcp: use local variable tp in sendmsg_frag Geliang Tang
2026-07-11 13:07 ` [PATCH mptcp-next 2/4] mptcp: add msg zerocopy support Geliang Tang
2026-07-11 13:07 ` [PATCH mptcp-next 3/4] selftests: mptcp: connect: add zerocopy io mode Geliang Tang
2026-07-11 13:07 ` [PATCH mptcp-next 4/4] selftests: mptcp: connect: cover zerocopy mode Geliang Tang
2026-07-11 14:13 ` [PATCH mptcp-next 0/4] mptcp: add MSG_ZEROCOPY support 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.1783774784.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