From: Donald Hunter <donald.hunter@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, jiri@resnulli.us,
alessandromarcolini99@gmail.com
Subject: Re: [PATCH net-next] tools: ynl: add --list-ops and --list-msgs to CLI
Date: Fri, 03 May 2024 11:17:37 +0100 [thread overview]
Message-ID: <m2fruzfbcu.fsf@gmail.com> (raw)
In-Reply-To: <20240502164043.2130184-1-kuba@kernel.org> (Jakub Kicinski's message of "Thu, 2 May 2024 09:40:43 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> I often forget the exact naming of ops and have to look at
> the spec to find it. Add support for listing the operations:
>
> $ ./cli.py --spec .../netdev.yaml --list-ops
> dev-get [ do, dump ]
> page-pool-get [ do, dump ]
> page-pool-stats-get [ do, dump ]
> queue-get [ do, dump ]
> napi-get [ do, dump ]
> qstats-get [ dump ]
>
> For completeness also support listing all ops (including
> notifications:
>
> # ./cli.py --spec .../netdev.yaml --list-msgs
> dev-get [ dump, do ]
> dev-add-ntf [ notify ]
> dev-del-ntf [ notify ]
> dev-change-ntf [ notify ]
> page-pool-get [ dump, do ]
> page-pool-add-ntf [ notify ]
> page-pool-del-ntf [ notify ]
> page-pool-change-ntf [ notify ]
> page-pool-stats-get [ dump, do ]
> queue-get [ dump, do ]
> napi-get [ dump, do ]
> qstats-get [ dump ]
>
> Use double space after the name for slightly easier to read
> output.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Donald Hunter <donald.hunter@gmail.com>
next prev parent reply other threads:[~2024-05-03 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 16:40 [PATCH net-next] tools: ynl: add --list-ops and --list-msgs to CLI Jakub Kicinski
2024-05-02 16:57 ` Jiri Pirko
2024-05-03 10:17 ` Donald Hunter [this message]
2024-05-03 22: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=m2fruzfbcu.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=alessandromarcolini99@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--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 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.