From: Dave Taht <dave.taht@gmail.com>
To: libreqos@lists.bufferbloat.net, Jakub Kicinski <kuba@kernel.org>
Subject: [LibreQoS] Fwd: [PATCH net-next v2 0/7] Netlink protocol specs
Date: Thu, 13 Oct 2022 13:04:17 -0700 [thread overview]
Message-ID: <CAA93jw4BAPsWKXFiQw_hhMNh8FV6jq-aSs-=L9tTBCx-02xEGg@mail.gmail.com> (raw)
In-Reply-To: <20220930023418.1346263-1-kuba@kernel.org>
I am told 3+ people are trying to turn the yaml netlink spec into
rust. It would be good to co-ordinate and leverage their work for
libreqos.io but I don't know who or where they are doing that work.
---------- Forwarded message ---------
From: Jakub Kicinski <kuba@kernel.org>
Date: Thu, Sep 29, 2022 at 7:37 PM
Subject: [PATCH net-next v2 0/7] Netlink protocol specs
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <edumazet@google.com>,
<pabeni@redhat.com>, <robh@kernel.org>, <johannes@sipsolutions.net>,
<ecree.xilinx@gmail.com>, <stephen@networkplumber.org>,
<sdf@google.com>, <f.fainelli@gmail.com>, <fw@strlen.de>,
<linux-doc@vger.kernel.org>, <razor@blackwall.org>,
<nicolas.dichtel@6wind.com>, <gnault@redhat.com>, Jakub Kicinski
<kuba@kernel.org>
Hi!
I think the Netlink proto specs are far along enough to merge.
Filling in all attribute types and quirks will be an ongoing
effort but we have enough to cover FOU so it's somewhat complete.
I fully intend to continue polishing the code but at the same
time I'd like to start helping others base their work on the
specs (e.g. DPLL) and need to start working on some new families
myself.
That's the progress / motivation for merging. The RFC [1] has more
of a high level blurb, plus I created a lot of documentation, I'm
not going to repeat it here. There was also the talk at LPC [2].
[1] https://lore.kernel.org/all/20220811022304.583300-1-kuba@kernel.org/
[2] https://youtu.be/9QkXIQXkaQk?t=2562
v2:
- update docs
- change comment format in uAPI from // to /* */
- rename fou.c to make linker happy
Jakub Kicinski (7):
docs: add more netlink docs (incl. spec docs)
netlink: add schemas for YAML specs
net: add basic C code generators for Netlink
netlink: add a proto specification for FOU
net: fou: regenerate the uAPI from the spec
net: fou: rename the source for linking
net: fou: use policy and operation tables generated from the spec
Documentation/core-api/index.rst | 1 +
Documentation/core-api/netlink.rst | 99 +
Documentation/netlink/genetlink-c.yaml | 287 +++
Documentation/netlink/genetlink-legacy.yaml | 313 +++
Documentation/netlink/genetlink.yaml | 252 +++
Documentation/netlink/specs/fou.yaml | 128 ++
.../userspace-api/netlink/c-code-gen.rst | 104 +
.../netlink/genetlink-legacy.rst | 96 +
Documentation/userspace-api/netlink/index.rst | 5 +
Documentation/userspace-api/netlink/specs.rst | 410 ++++
MAINTAINERS | 3 +
include/uapi/linux/fou.h | 54 +-
net/ipv4/Makefile | 1 +
net/ipv4/fou-nl.c | 48 +
net/ipv4/fou-nl.h | 25 +
net/ipv4/{fou.c => fou_core.c} | 51 +-
tools/net/ynl/ynl-gen-c.py | 1998 +++++++++++++++++
tools/net/ynl/ynl-regen.sh | 30 +
18 files changed, 3835 insertions(+), 70 deletions(-)
create mode 100644 Documentation/core-api/netlink.rst
create mode 100644 Documentation/netlink/genetlink-c.yaml
create mode 100644 Documentation/netlink/genetlink-legacy.yaml
create mode 100644 Documentation/netlink/genetlink.yaml
create mode 100644 Documentation/netlink/specs/fou.yaml
create mode 100644 Documentation/userspace-api/netlink/c-code-gen.rst
create mode 100644 Documentation/userspace-api/netlink/genetlink-legacy.rst
create mode 100644 Documentation/userspace-api/netlink/specs.rst
create mode 100644 net/ipv4/fou-nl.c
create mode 100644 net/ipv4/fou-nl.h
rename net/ipv4/{fou.c => fou_core.c} (94%)
create mode 100755 tools/net/ynl/ynl-gen-c.py
create mode 100755 tools/net/ynl/ynl-regen.sh
--
2.37.3
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-10-13 20:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220930023418.1346263-1-kuba@kernel.org>]
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
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4BAPsWKXFiQw_hhMNh8FV6jq-aSs-=L9tTBCx-02xEGg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=kuba@kernel.org \
--cc=libreqos@lists.bufferbloat.net \
/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