All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	robh@kernel.org, johannes@sipsolutions.net,
	stephen@networkplumber.org, ecree.xilinx@gmail.com,
	sdf@google.com, f.fainelli@gmail.com, fw@strlen.de,
	linux-doc@vger.kernel.org, razor@blackwall.org,
	nicolas.dichtel@6wind.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v4 0/8] Netlink protocol specs
Date: Fri, 20 Jan 2023 09:50:33 -0800	[thread overview]
Message-ID: <20230120175041.342573-1-kuba@kernel.org> (raw)

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: https://lore.kernel.org/all/20220930023418.1346263-1-kuba@kernel.org/
v3: https://lore.kernel.org/all/20230119003613.111778-1-kuba@kernel.org/1

v4:
 - spec improvements (patch 2)
 - Python cleanup (patch 3)
 - rename auto-gen files and use the right comment style

Jakub Kicinski (8):
  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
  tools: ynl: add a completely generic client

 Documentation/core-api/index.rst              |    1 +
 Documentation/core-api/netlink.rst            |  101 +
 Documentation/netlink/genetlink-c.yaml        |  333 +++
 Documentation/netlink/genetlink-legacy.yaml   |  356 +++
 Documentation/netlink/genetlink.yaml          |  298 +++
 Documentation/netlink/specs/fou.yaml          |  128 +
 .../userspace-api/netlink/c-code-gen.rst      |  107 +
 .../netlink/genetlink-legacy.rst              |   96 +
 Documentation/userspace-api/netlink/index.rst |    5 +
 Documentation/userspace-api/netlink/specs.rst |  422 +++
 MAINTAINERS                                   |    3 +
 include/uapi/linux/fou.h                      |   54 +-
 net/ipv4/Makefile                             |    1 +
 net/ipv4/{fou.c => fou_core.c}                |   47 +-
 net/ipv4/fou_nl.c                             |   48 +
 net/ipv4/fou_nl.h                             |   25 +
 tools/net/ynl/samples/cli.py                  |   47 +
 tools/net/ynl/samples/ynl.py                  |  534 ++++
 tools/net/ynl/ynl-gen-c.py                    | 2373 +++++++++++++++++
 tools/net/ynl/ynl-regen.sh                    |   30 +
 20 files changed, 4941 insertions(+), 68 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
 rename net/ipv4/{fou.c => fou_core.c} (94%)
 create mode 100644 net/ipv4/fou_nl.c
 create mode 100644 net/ipv4/fou_nl.h
 create mode 100755 tools/net/ynl/samples/cli.py
 create mode 100644 tools/net/ynl/samples/ynl.py
 create mode 100755 tools/net/ynl/ynl-gen-c.py
 create mode 100755 tools/net/ynl/ynl-regen.sh

-- 
2.39.0


             reply	other threads:[~2023-01-20 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 17:50 Jakub Kicinski [this message]
2023-01-20 17:50 ` [PATCH net-next v4 1/8] docs: add more netlink docs (incl. spec docs) Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 2/8] netlink: add schemas for YAML specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 3/8] net: add basic C code generators for Netlink Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 4/8] netlink: add a proto specification for FOU Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 5/8] net: fou: regenerate the uAPI from the spec Jakub Kicinski
2023-01-24 17:49   ` Alexander Lobakin
2023-01-24 18:50     ` Johannes Berg
2023-01-25  0:40       ` Jakub Kicinski
2023-01-25 10:16         ` Alexander Lobakin
2023-01-20 17:50 ` [PATCH net-next v4 6/8] net: fou: rename the source for linking Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 7/8] net: fou: use policy and operation tables generated from the spec Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 8/8] tools: ynl: add a completely generic client Jakub Kicinski
2023-01-24 10:29 ` [PATCH net-next v4 0/8] Netlink protocol specs Paolo Abeni
2023-01-24 10:40 ` patchwork-bot+netdevbpf

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=20230120175041.342573-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=robh@kernel.org \
    --cc=sdf@google.com \
    --cc=stephen@networkplumber.org \
    /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.