From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][RFC PATCH mptcp-next 0/6] MP_PRIO support
Date: Thu, 05 Nov 2020 18:50:17 +0800 [thread overview]
Message-ID: <cover.1604572610.git.geliangtang@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
This patchset implements the MP_PRIO logic according to the following lines
in RFC8684:
"""
Another use of the MP_PRIO option is to set the "B" flag on a subflow to
cleanly "retire" its use before closing it and removing it with RM_ADDR.
"""
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/51
Geliang Tang (6):
mptcp: add the outgoing MP_PRIO support
mptcp: add the incoming MP_PRIO support
mptcp: add prio_changed flag
mptcp: send out MP_PRIO before RM_ADDR
mptcp: add the mib for MP_PRIO
selftests: mptcp: add MP_PRIO check in chk_rm_nr
include/net/mptcp.h | 1 +
net/mptcp/mib.c | 1 +
net/mptcp/mib.h | 1 +
net/mptcp/options.c | 53 +++++++++++++++++++
net/mptcp/pm.c | 11 ++++
net/mptcp/pm_netlink.c | 32 +++++++++++
net/mptcp/protocol.c | 4 +-
net/mptcp/protocol.h | 14 +++++
.../testing/selftests/net/mptcp/mptcp_join.sh | 34 ++++++++----
9 files changed, 139 insertions(+), 12 deletions(-)
--
2.26.2
reply other threads:[~2020-11-05 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1604572610.git.geliangtang@gmail.com \
--to=unknown@example.com \
/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.