From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Stanislav Fomichev <sdf@google.com>
Subject: [PATCH net-next 0/4] ynl: fill in some gaps of ethtool spec
Date: Fri, 17 Mar 2023 17:23:36 -0700 [thread overview]
Message-ID: <20230318002340.1306356-1-sdf@google.com> (raw)
I was trying to fill in the spec while exploring ethtool API for some
related work. I don't think I'll have the patience to fill in the rest,
so decided to share whatever I currently have.
Patches 1-2 add the be16 + spec.
Patches 3-4 implement an ethtool-like python tool to test the spec.
Patches 3-4 are there because it felt more fun do the tool instead
of writing the actual tests; feel free to drop it; sharing mostly
to show that the spec is not a complete nonsense.
The spec is not 100% complete, see patch 2 for what's missing.
I was hoping to finish the stats-get message, but I'm too dump
to implement bitmask marshaling (multi-attr).
Stanislav Fomichev (4):
ynl: support be16 in schemas
ynl: populate most of the ethtool spec
ynl: replace print with NlError
ynl: ethtool testing tool
Documentation/netlink/genetlink-c.yaml | 2 +-
Documentation/netlink/genetlink-legacy.yaml | 4 +-
Documentation/netlink/genetlink.yaml | 2 +-
Documentation/netlink/specs/ethtool.yaml | 1473 +++++++++++++++++--
tools/net/ynl/ethtool | 424 ++++++
tools/net/ynl/lib/nlspec.py | 9 +
tools/net/ynl/lib/ynl.py | 31 +-
7 files changed, 1827 insertions(+), 118 deletions(-)
create mode 100755 tools/net/ynl/ethtool
--
2.40.0.rc1.284.g88254d51c5-goog
next reply other threads:[~2023-03-18 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 0:23 Stanislav Fomichev [this message]
2023-03-18 0:23 ` [PATCH net-next 1/4] ynl: support be16 in schemas Stanislav Fomichev
2023-03-18 4:18 ` Jakub Kicinski
2023-03-20 18:03 ` Stanislav Fomichev
2023-03-18 0:23 ` [PATCH net-next 2/4] ynl: populate most of the ethtool spec Stanislav Fomichev
2023-03-18 4:33 ` Jakub Kicinski
2023-03-20 18:03 ` Stanislav Fomichev
2023-03-20 18:59 ` Jakub Kicinski
2023-03-18 0:23 ` [PATCH net-next 3/4] ynl: replace print with NlError Stanislav Fomichev
2023-03-18 4:21 ` Jakub Kicinski
2023-03-20 18:03 ` Stanislav Fomichev
2023-03-20 18:53 ` Jakub Kicinski
2023-03-18 0:23 ` [PATCH net-next 4/4] ynl: ethtool testing tool Stanislav Fomichev
2023-03-18 4:23 ` Jakub Kicinski
2023-03-20 18:03 ` Stanislav Fomichev
2023-03-18 4:24 ` Jakub Kicinski
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=20230318002340.1306356-1-sdf@google.com \
--to=sdf@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).