From: David Miller <davem@davemloft.net>
To: idosch@idosch.org
Cc: netdev@vger.kernel.org, kuba@kernel.org, jiri@mellanox.com,
mlxsw@mellanox.com, idosch@mellanox.com
Subject: Re: [PATCH net-next 0/9] mlxsw: spectrum_cnt: Expose counter resources
Date: Wed, 18 Mar 2020 16:46:36 -0700 (PDT) [thread overview]
Message-ID: <20200318.164636.2101956120165364730.davem@davemloft.net> (raw)
In-Reply-To: <20200318134857.1003018-1-idosch@idosch.org>
From: Ido Schimmel <idosch@idosch.org>
Date: Wed, 18 Mar 2020 15:48:48 +0200
> From: Ido Schimmel <idosch@mellanox.com>
>
> Jiri says:
>
> Capacity and utilization of existing flow and RIF counters are currently
> unavailable to be seen by the user. Use the existing devlink resources
> API to expose the information:
>
> $ sudo devlink resource show pci/0000:00:10.0 -v
> pci/0000:00:10.0:
> name kvd resource_path /kvd size 524288 unit entry dpipe_tables none
> name span_agents resource_path /span_agents size 8 occ 0 unit entry dpipe_tables none
> name counters resource_path /counters size 79872 occ 44 unit entry dpipe_tables none
> resources:
> name flow resource_path /counters/flow size 61440 occ 4 unit entry dpipe_tables none
> name rif resource_path /counters/rif size 18432 occ 40 unit entry dpipe_tables none
Series applied, thanks everyone.
prev parent reply other threads:[~2020-03-18 23:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 13:48 [PATCH net-next 0/9] mlxsw: spectrum_cnt: Expose counter resources Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 1/9] mlxsw: spectrum_cnt: Query bank size from FW resources Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 2/9] selftests: spectrum-2: Adjust tc_flower_scale limit according to current counter count Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 3/9] mlxsw: spectrum_cnt: Move sub_pools under per-instance pool struct Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 4/9] mlxsw: spectrum_cnt: Add entry_size_res_id for each subpool and use it to query entry size Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 5/9] mlxsw: spectrum_cnt: Expose subpool sizes over devlink resources Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 6/9] mlxsw: spectrum_cnt: Move config validation along with resource register Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 7/9] mlxsw: spectrum_cnt: Consolidate subpools initialization Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 8/9] mlxsw: spectrum_cnt: Expose devlink resource occupancy for counters Ido Schimmel
2020-03-18 13:48 ` [PATCH net-next 9/9] selftests: mlxsw: Add tc action hw_stats tests Ido Schimmel
2020-03-18 20:50 ` [PATCH net-next 0/9] mlxsw: spectrum_cnt: Expose counter resources Jakub Kicinski
2020-03-18 23:46 ` David Miller [this message]
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=20200318.164636.2101956120165364730.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox