From: Simon Horman <horms@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Carolina Jubran <cjubran@nvidia.com>, Aya Levin <ayal@nvidia.com>
Subject: Re: [PATCH net-next 5/8] net/mlx5e: Expose the VF/SF RX drop counter on the representor
Date: Thu, 28 Mar 2024 11:18:31 +0000 [thread overview]
Message-ID: <20240328111831.GA403975@kernel.org> (raw)
In-Reply-To: <20240326222022.27926-6-tariqt@nvidia.com>
On Wed, Mar 27, 2024 at 12:20:19AM +0200, Tariq Toukan wrote:
> From: Carolina Jubran <cjubran@nvidia.com>
>
> Q counters are device-level counters that track specific
> events, among which are out_of_buffer events. These events
> occur when packets are dropped due to a lack of receive
> buffer in the RX queue.
>
> Expose the total number of out_of_buffer events on the
> VF/SF to their respective representor, using the
> "ethtool -S" under the name of "rx_vport_out_of_buffer".
>
> The "rx_vport_out_of_buffer" equals the sum of all
> Q counters out_of_buffer values allocated on the VF/SF.
Hi Carolina and Tariq,
I am wondering if any consideration was given to making this
a generic counter. Buffer exhaustion sounds like something that
other NICs may report too.
>
> Signed-off-by: Carolina Jubran <cjubran@nvidia.com>
> Reviewed-by: Gal Pressman <gal@nvidia.com>
> Reviewed-by: Aya Levin <ayal@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
...
next prev parent reply other threads:[~2024-03-28 11:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 22:20 [PATCH net-next 0/8] mlx5e misc patches Tariq Toukan
2024-03-26 22:20 ` [PATCH net-next 1/8] net/mlx5e: Use ethtool_sprintf/puts() to fill priv flags strings Tariq Toukan
2024-03-28 11:19 ` Simon Horman
2024-03-26 22:20 ` [PATCH net-next 2/8] net/mlx5e: Use ethtool_sprintf/puts() to fill selftests strings Tariq Toukan
2024-03-28 11:18 ` Simon Horman
2024-03-26 22:20 ` [PATCH net-next 3/8] net/mlx5e: Use ethtool_sprintf/puts() to fill stats strings Tariq Toukan
2024-03-28 11:20 ` Simon Horman
2024-03-26 22:20 ` [PATCH net-next 4/8] net/mlx5e: Make stats group fill_stats callbacks consistent with the API Tariq Toukan
2024-03-28 11:20 ` Simon Horman
2024-03-26 22:20 ` [PATCH net-next 5/8] net/mlx5e: Expose the VF/SF RX drop counter on the representor Tariq Toukan
2024-03-28 11:18 ` Simon Horman [this message]
2024-03-28 16:21 ` Jakub Kicinski
2024-03-31 18:52 ` Tariq Toukan
2024-04-01 15:03 ` Jakub Kicinski
2024-04-02 18:02 ` Rahul Rameshbabu
2024-03-26 22:20 ` [PATCH net-next 6/8] net/mlx5e: debugfs, Add reset option for command interface stats Tariq Toukan
2024-03-28 11:20 ` Simon Horman
2024-03-26 22:20 ` [PATCH net-next 7/8] net/mlx5e: XDP, Fix an inconsistent comment Tariq Toukan
2024-03-28 11:17 ` Simon Horman
2024-03-26 22:20 ` [PATCH net-next 8/8] net/mlx5: Convert uintX_t to uX Tariq Toukan
2024-03-28 11:20 ` Simon Horman
2024-03-28 16:25 ` [PATCH net-next 0/8] mlx5e misc patches Jakub Kicinski
2024-03-28 22:28 ` Tariq Toukan
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=20240328111831.GA403975@kernel.org \
--to=horms@kernel.org \
--cc=ayal@nvidia.com \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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).