From: Stephen Hemminger <stephen@networkplumber.org>
To: Shani Peretz <shperetz@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Aman Singh <aman.deep.singh@intel.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [RFC PATCH] ethdev: add new API for enable/disable xstat counters by ID
Date: Tue, 24 Dec 2024 09:19:02 -0800 [thread overview]
Message-ID: <20241224091902.6c73340a@fedora> (raw)
In-Reply-To: <SA1PR12MB94917E63FE910BB6F5DC4F37BF022@SA1PR12MB9491.namprd12.prod.outlook.com>
On Mon, 23 Dec 2024 10:46:59 +0000
Shani Peretz <shperetz@nvidia.com> wrote:
> Sorry if it wasn't clear, in mlx5 there is limited number of counters, so if there are X counters and 2X queues, there won't be enough counters to get statistics for all queues at the same time.
> In this case we thought the best approach would be to allow the user to choose which queues they want statistics from.
> If the counters are exceeded, the user would have the option to disable the counter, thereby freeing up the resource for reuse elsewhere.
>
Ok, other hardware may have same issue.
Why not do it per-queue (not the id stuff).
Kind of related to the existing queue stat counters that need rework.
The ixgbe has similar mapping problem.
Let's solve this once across multiple devices.
prev parent reply other threads:[~2024-12-24 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 15:38 Shani Peretz
2024-12-22 16:46 ` Stephen Hemminger
2024-12-23 10:46 ` Shani Peretz
2024-12-24 17:19 ` Stephen Hemminger [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=20241224091902.6c73340a@fedora \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).