From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH RFC 0/4] mptcp: let the in kernel PM control the MPC
Date: Fri, 24 Jun 2022 18:38:06 +0200 [thread overview]
Message-ID: <cover.1656088406.git.pabeni@redhat.com> (raw)
this is follow-up to the last public mtg and:
https://github.com/multipath-tcp/mptcp_net-next/issues/285
implementing the idea described in the last comment from the above isse
It's just a proof of concept, only compile tested, to better describe
the idea.
While implementing the above I found a fews bugs fixed in patch
1/4, 2/4 and 4/4.
If there is agreement on this kind of changes, next week I plan to cook
a formal submission, including a few additional self-tests.
Paolo Abeni (4):
mptcp: fix local endpoint acconting.
mptcp: introduce and use mptcp_pm_send_ack()
mptcp: allow the in kernel PM to set MPC subflow priority
mptcp: more accurate MPC endpoint tracking
net/mptcp/pm_netlink.c | 103 ++++++++++++++++++++++-------------------
net/mptcp/protocol.c | 11 +++--
net/mptcp/protocol.h | 3 +-
3 files changed, 65 insertions(+), 52 deletions(-)
--
2.35.3
next reply other threads:[~2022-06-24 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 16:38 Paolo Abeni [this message]
2022-06-24 16:38 ` [PATCH RFC 1/4] mptcp: fix local endpoint acconting Paolo Abeni
2022-06-24 16:38 ` [PATCH RFC 2/4] mptcp: introduce and use mptcp_pm_send_ack() Paolo Abeni
2022-06-28 23:28 ` Mat Martineau
2022-06-29 10:10 ` Paolo Abeni
2022-06-29 15:59 ` Mat Martineau
2022-06-24 16:38 ` [PATCH RFC 3/4] mptcp: allow the in kernel PM to set MPC subflow priority Paolo Abeni
2022-06-29 0:11 ` Mat Martineau
2022-06-29 10:55 ` Paolo Abeni
2022-06-29 16:07 ` Mat Martineau
2022-06-24 16:38 ` [PATCH RFC 4/4] mptcp: more accurate MPC endpoint tracking Paolo Abeni
2022-06-24 16:49 ` mptcp: more accurate MPC endpoint tracking: Build Failure MPTCP CI
2022-06-24 18:36 ` mptcp: more accurate MPC endpoint tracking: Tests Results 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.1656088406.git.pabeni@redhat.com \
--to=pabeni@redhat.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).