From: Geliang Tang <geliangtang@gmail.com>
To: mptcp@lists.linux.dev, geliangtang@gmail.com
Cc: Geliang Tang <geliangtang@xiaomi.com>
Subject: [PATCH mptcp-next 0/6] The infinite mapping support
Date: Mon, 6 Sep 2021 15:58:01 +0800 [thread overview]
Message-ID: <cover.1630914699.git.geliangtang@xiaomi.com> (raw)
From: Geliang Tang <geliangtang@xiaomi.com>
v1:
- add noncontiguous flag
- add the mibs check
- tag: export/20210904T080009
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/216
Geliang Tang (6):
mptcp: add noncontiguous flag
mptcp: infinite mapping sending
mptcp: infinite mapping receiving
mptcp: add a mib for the infinite mapping sending
selftests: mptcp: add infinite map mibs check
DO-NOT-MERGE: mptcp: mp_fail test
net/mptcp/mib.c | 1 +
net/mptcp/mib.h | 1 +
net/mptcp/options.c | 8 +++
net/mptcp/pm.c | 6 ++
net/mptcp/protocol.c | 40 ++++++++++++-
net/mptcp/protocol.h | 4 ++
net/mptcp/subflow.c | 18 +++---
.../testing/selftests/net/mptcp/mptcp_join.sh | 56 +++++++++++++++++++
8 files changed, 124 insertions(+), 10 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-06 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 7:58 Geliang Tang [this message]
2021-09-06 7:58 ` [PATCH mptcp-next 1/6] mptcp: add noncontiguous flag Geliang Tang
2021-09-08 23:39 ` Mat Martineau
2021-09-06 7:58 ` [PATCH mptcp-next 2/6] mptcp: infinite mapping sending Geliang Tang
2021-09-09 0:01 ` Mat Martineau
2021-09-06 7:58 ` [PATCH mptcp-next 3/6] mptcp: infinite mapping receiving Geliang Tang
2021-09-09 0:04 ` Mat Martineau
2021-09-06 7:58 ` [PATCH mptcp-next 4/6] mptcp: add a mib for the infinite mapping sending Geliang Tang
2021-09-06 7:58 ` [PATCH mptcp-next 5/6] selftests: mptcp: add infinite map mibs check Geliang Tang
2021-09-06 7:58 ` [PATCH mptcp-next 6/6] DO-NOT-MERGE: mptcp: mp_fail test Geliang Tang
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.1630914699.git.geliangtang@xiaomi.com \
--to=geliangtang@gmail.com \
--cc=geliangtang@xiaomi.com \
--cc=mptcp@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).