From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH v2 0/9] add locking to PM APis, implement PM netlink
Date: Fri, 21 Feb 2020 17:17:21 +0100 [thread overview]
Message-ID: <cover.1582297149.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
This implement the locking required by the PM to allow concurent subflow
accessing the msk PM data in a safe way. Such data is protected via a msk-level
spinlock. It relies on the Double checked locking to avoid contention in the
most common scenarion (no or very little PM "actions").
Additionally changes more than a bit the PM hooks/APIs, to be hopefully simpler
and avoiding duplicate code (no v4/v6 variant, work queue management done by the
core PM infra).
It also introduce the PM netlink - it replace the current basic ones, the
related patch has been dropped locally.
git tree available at:
https://github.com/pabeni/mptcp/tree/mptcp_net-next_part3_6
changes from v1:
- 2 new patches: mp_join self-tests (9/9) and a specific mp_join fix (6/9)
- fixed several bugs as pointed out by the above tests
- added support for bind to interface
changes from RFC:
- cleanup uAPIs
- added self-tests for the uAPIs
- fixed ton of bugs
- included feedback from Mat
include/uapi/linux/mptcp.h | 53 +
net/mptcp/Makefile | 3
net/mptcp/options.c | 60 -
net/mptcp/pm.c | 353 +++------
net/mptcp/pm_netlink.c | 828 ++++++++++++++++++++++
net/mptcp/protocol.c | 14
net/mptcp/protocol.h | 113 +--
net/mptcp/subflow.c | 65 +
tools/testing/selftests/net/mptcp/Makefile | 5
tools/testing/selftests/net/mptcp/mptcp_connect.c | 19
tools/testing/selftests/net/mptcp/mptcp_join.sh | 295 +++++++
tools/testing/selftests/net/mptcp/pm_netlink.sh | 123 +++
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 600 +++++++++++++++
13 files changed, 2218 insertions(+), 313 deletions(-)
reply other threads:[~2020-02-21 16:17 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.1582297149.git.pabeni@redhat.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.