From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, moshe@nvidia.com, saeedm@nvidia.com,
idosch@nvidia.com, petrm@nvidia.com
Subject: Re: [patch net-next v4 00/13] devlink: introduce selective dumps
Date: Fri, 11 Aug 2023 18:02:53 -0700 [thread overview]
Message-ID: <20230811180253.0114d307@kernel.org> (raw)
In-Reply-To: <20230811155714.1736405-1-jiri@resnulli.us>
On Fri, 11 Aug 2023 17:57:01 +0200 Jiri Pirko wrote:
> For SFs, one devlink instance per SF is created. There might be
> thousands of these on a single host. When a user needs to know port
> handle for specific SF, he needs to dump all devlink ports on the host
> which does not scale good.
Acked-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2023-08-12 1:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 15:57 [patch net-next v4 00/13] devlink: introduce selective dumps Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 01/13] devlink: parse linecard attr in doit() callbacks Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 02/13] devlink: parse rate attrs " Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 03/13] devlink: introduce devlink_nl_pre_doit_port*() helper functions Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 04/13] devlink: rename doit callbacks for per-instance dump commands Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 05/13] devlink: introduce dumpit callbacks for split ops Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 06/13] devlink: pass flags as an arg of dump_one() callback Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 07/13] netlink: specs: devlink: add commands that do per-instance dump Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 08/13] devlink: remove duplicate temporary netlink callback prototypes Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 09/13] devlink: remove converted commands from small ops Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 10/13] devlink: allow user to narrow per-instance dumps by passing handle attrs Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 11/13] netlink: specs: devlink: extend per-instance dump commands to accept instance attributes Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 12/13] devlink: extend health reporter dump selector by port index Jiri Pirko
2023-08-11 15:57 ` [patch net-next v4 13/13] netlink: specs: devlink: extend health reporter dump attributes " Jiri Pirko
2023-08-12 1:02 ` Jakub Kicinski [this message]
2023-08-14 18:50 ` [patch net-next v4 00/13] devlink: introduce selective dumps 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=20230811180253.0114d307@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--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 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).