From: Davide Caratti <dcaratti@redhat.com>
To: mptcp@lists.linux.dev
Cc: pabeni@redhat.com, Matthieu Baerts <matthieu.baerts@tessares.net>
Subject: [PATCH mptcp-next v2 0/6] convert MPTCP to use YAML spec
Date: Fri, 1 Sep 2023 20:10:29 +0200 [thread overview]
Message-ID: <cover.1693591676.git.dcaratti@redhat.com> (raw)
this series converts most of the MPTCP netlink interface (plus uAPI bits)
to use sources generated by a YAML spec file. Patch 2/6 and 6/6 have been
individually verified with kselftests.
POC:
$ sudo ./tools/net/ynl/cli.py --spec \
> Documentation/netlink/specs/mptcp.yaml --do add_addr \
> --json '{"addr": {"addr4": 16909061, "family": 2, "flags": 4, "id": 10, "port": 0}}'
$ ip -j mptcp endpoint show id 10
[{"address":"1.2.3.5","id":10,"backup":true}]
v2:
- mptcp.yaml: only put values around enum "holes" (Paolo Abeni)
- _doit and _dumpit renames are done in a dedicate patch (Paolo Abeni)
- removed useless nla_policy passed through parse_entry() (Paolo Abeni)
- renamed mptcp_pm_address_nl_policy in patch 2 (Paolo Abeni)
- (hopefully) more comprehensible commit messages (Paolo Abeni)
Davide Caratti (6):
tools: ynl: add uns-admin-perm to genetlink legacy
mptcp: convert netlink from small_ops to ops
Documentation: netlink: add a YAML spec for mptcp
mptcp: uapi: use header file generated from YAML spec
net: mptcp: rename netlink handlers to
mptcp_pm_nl_<blah>_{doit,dumpit}
net: mptcp: use policy generated by YAML spec
Documentation/netlink/genetlink-legacy.yaml | 2 +-
Documentation/netlink/specs/mptcp.yaml | 394 ++++++++++++++++++++
include/uapi/linux/mptcp.h | 174 +--------
include/uapi/linux/mptcp_pm.h | 149 ++++++++
net/mptcp/Makefile | 3 +-
net/mptcp/mptcp_pm_gen.c | 179 +++++++++
net/mptcp/mptcp_pm_gen.h | 58 +++
net/mptcp/pm_netlink.c | 114 +-----
net/mptcp/pm_userspace.c | 8 +-
net/mptcp/protocol.h | 6 +-
10 files changed, 814 insertions(+), 273 deletions(-)
create mode 100644 Documentation/netlink/specs/mptcp.yaml
create mode 100644 include/uapi/linux/mptcp_pm.h
create mode 100644 net/mptcp/mptcp_pm_gen.c
create mode 100644 net/mptcp/mptcp_pm_gen.h
--
2.40.1
next reply other threads:[~2023-09-01 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:10 Davide Caratti [this message]
2023-09-01 18:10 ` [PATCH mptcp-next v2 1/6] tools: ynl: add uns-admin-perm to genetlink legacy Davide Caratti
2023-09-01 18:10 ` [PATCH mptcp-next v2 2/6] mptcp: convert netlink from small_ops to ops Davide Caratti
2023-09-04 9:13 ` Paolo Abeni
2023-09-04 15:20 ` Davide Caratti
2023-09-05 11:26 ` Paolo Abeni
2023-09-01 18:10 ` [PATCH mptcp-next v2 3/6] Documentation: netlink: add a YAML spec for mptcp Davide Caratti
2023-09-01 18:10 ` [PATCH mptcp-next v2 4/6] mptcp: uapi: use header file generated from YAML spec Davide Caratti
2023-09-01 18:10 ` [PATCH mptcp-next v2 5/6] net: mptcp: rename netlink handlers to mptcp_pm_nl_<blah>_{doit,dumpit} Davide Caratti
2023-09-01 18:10 ` [PATCH mptcp-next v2 6/6] net: mptcp: use policy generated by YAML spec Davide Caratti
2023-09-01 18:36 ` net: mptcp: use policy generated by YAML spec: Build Failure MPTCP CI
2023-09-01 19:22 ` net: mptcp: use policy generated by YAML spec: Tests Results MPTCP CI
2023-09-04 9:17 ` [PATCH mptcp-next v2 0/6] convert MPTCP to use YAML spec Paolo Abeni
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.1693591676.git.dcaratti@redhat.com \
--to=dcaratti@redhat.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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.