From: Gang Yan <gang.yan@linux.dev>
To: mptcp@lists.linux.dev
Cc: Gang Yan <yangang@kylinos.cn>
Subject: [PATCH mptcp-next v2 0/2] mptcp: preserve MSG_EOR semantics in sendmsg path
Date: Tue, 31 Mar 2026 17:08:07 +0800 [thread overview]
Message-ID: <cover.1774947296.git.yangang@kylinos.cn> (raw)
From: Gang Yan <yangang@kylinos.cn>
Hi, Matt:
With this v2 version, the packetdrill scripts also updated at
https://github.com/multipath-tcp/packetdrill/pull/189.
I removed the 'mptcp_eor_subflows.pkt', and made some improvements in
'mptcp_eor_no_collapse.pkt'.
Thanks,
Gang
---
Changelog:
v2:
- Split the change into two independent patches:
Patch 1 changes overhead to u8 (with BUILD_BUG_ON).
Patch 2 implements the actual MSG_EOR handling.
This split makes the series easier to review.
- Added a !df->eor check in mptcp_frag_can_collapse_to() to prevent
appending new data after a dfrag with the EOR flag set.
- Improved comments at the new BUILD_BUG_ON check.
v1:
- Link: https://patchwork.kernel.org/project/mptcp/patch/20260309025431.125943-1-gang.yan@linux.dev/
Gang Yan (2):
mptcp: reduce 'overhead' from u16 to u8
mptcp: preserve MSG_EOR semantics in sendmsg path
net/mptcp/protocol.c | 28 +++++++++++++++++++++++++---
net/mptcp/protocol.h | 4 +++-
2 files changed, 28 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-31 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 9:08 Gang Yan [this message]
2026-03-31 9:08 ` [PATCH mptcp-next v2 1/2] mptcp: reduce 'overhead' from u16 to u8 Gang Yan
2026-04-01 17:50 ` Matthieu Baerts
2026-03-31 9:08 ` [PATCH mptcp-next v2 2/2] mptcp: preserve MSG_EOR semantics in sendmsg path Gang Yan
2026-04-01 17:50 ` Matthieu Baerts
2026-03-31 10:37 ` [PATCH mptcp-next v2 0/2] " MPTCP CI
2026-04-02 12:19 ` Matthieu Baerts
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.1774947296.git.yangang@kylinos.cn \
--to=gang.yan@linux.dev \
--cc=mptcp@lists.linux.dev \
--cc=yangang@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.