From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, moshe@nvidia.com, saeedm@nvidia.com,
idosch@nvidia.com, petrm@nvidia.com
Subject: [patch net-next v3 00/12] devlink: use spec to generate split ops
Date: Thu, 3 Aug 2023 13:13:28 +0200 [thread overview]
Message-ID: <20230803111340.1074067-1-jiri@resnulli.us> (raw)
From: Jiri Pirko <jiri@nvidia.com>
This is an outcome of the discussion in the following thread:
https://lore.kernel.org/netdev/20230720121829.566974-1-jiri@resnulli.us/
It serves as a dependency on the linked selector patchset.
There is an existing spec for devlink used for userspace part
generation. There are two commands supported there.
This patchset extends the spec so kernel split ops code could
be generated from it.
---
v2->v3:
- reordered a bit to avoid build break, small changes to fix that
- see individual patches for changelog
v1->v2:
- see individual patches for changelog
Jiri Pirko (12):
netlink: specs: add dump-strict flag for dont-validate property
ynl-gen-c.py: filter rendering of validate field values for split ops
ynl-gen-c.py: allow directional model for kernel mode
ynl-gen-c.py: render netlink policies static for split ops
devlink: rename devlink_nl_ops to devlink_nl_small_ops
devlink: rename couple of doit netlink callbacks to match generated
names
devlink: introduce couple of dumpit callbacks for split ops
devlink: un-static devlink_nl_pre/post_doit()
netlink: specs: devlink: add info-get dump op
devlink: add split ops generated according to spec
devlink: include the generated netlink header
devlink: use generated split ops and remove duplicated commands from
small ops
Documentation/netlink/genetlink-c.yaml | 2 +-
Documentation/netlink/genetlink-legacy.yaml | 2 +-
Documentation/netlink/genetlink.yaml | 2 +-
Documentation/netlink/specs/devlink.yaml | 14 ++++-
net/devlink/Makefile | 2 +-
net/devlink/dev.c | 26 ++++-----
net/devlink/devl_internal.h | 20 +++----
net/devlink/leftover.c | 16 +-----
net/devlink/netlink.c | 35 ++++++------
net/devlink/netlink_gen.c | 59 +++++++++++++++++++++
net/devlink/netlink_gen.h | 29 ++++++++++
tools/net/ynl/generated/devlink-user.c | 53 ++++++++++++++++++
tools/net/ynl/generated/devlink-user.h | 10 ++++
tools/net/ynl/ynl-gen-c.py | 20 +++++--
14 files changed, 230 insertions(+), 60 deletions(-)
create mode 100644 net/devlink/netlink_gen.c
create mode 100644 net/devlink/netlink_gen.h
--
2.41.0
next reply other threads:[~2023-08-03 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 11:13 Jiri Pirko [this message]
2023-08-03 11:13 ` [patch net-next v3 01/12] netlink: specs: add dump-strict flag for dont-validate property Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 02/12] ynl-gen-c.py: filter rendering of validate field values for split ops Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 03/12] ynl-gen-c.py: allow directional model for kernel mode Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 04/12] ynl-gen-c.py: render netlink policies static for split ops Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 05/12] devlink: rename devlink_nl_ops to devlink_nl_small_ops Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 06/12] devlink: rename couple of doit netlink callbacks to match generated names Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 07/12] devlink: introduce couple of dumpit callbacks for split ops Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 08/12] devlink: un-static devlink_nl_pre/post_doit() Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 09/12] netlink: specs: devlink: add info-get dump op Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 10/12] devlink: add split ops generated according to spec Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 11/12] devlink: include the generated netlink header Jiri Pirko
2023-08-03 11:13 ` [patch net-next v3 12/12] devlink: use generated split ops and remove duplicated commands from small ops Jiri Pirko
2023-08-04 1:23 ` [patch net-next v3 00/12] devlink: use spec to generate split ops Jakub Kicinski
2023-08-04 21:10 ` 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=20230803111340.1074067-1-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.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.