From: Kenta Akagi <k@mgml.me>
To: Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, Kenta Akagi <k@mgml.me>
Subject: [PATCH RFC mlx5-next 0/1] net/mlx5e: Expose physical received bits counters to ethtool
Date: Mon, 12 Jan 2026 16:03:23 +0900 [thread overview]
Message-ID: <20260112070324.38819-1-k@mgml.me> (raw)
Hi,
I would like to measure the cable BER on ConnectX.
According to the documentation[1][2], there are counters that can be used
for this purpose: rx_corrected_bits_phy, rx_pcs_symbol_err_phy and
rx_bits_phy. However, rx_bits_phy does not show up in ethtool
statistics.
This patch exposes the PPCNT phy_received_bits as rx_bits_phy.
On a ConnectX-5 with 25Gbase connection, it works as expected.
On the other hand, although I have not verified it, in an 800Gbps
environment rx_bits_phy would likely overflow after about 124 days.
Since I cannot judge whether this is acceptable, I am posting this as an
RFC first.
[1] commit 8ce3b586faa4 ("net/mlx5: Add counter information to mlx5
driver documentation")
[2] https://docs.kernel.org/networking/device_drivers/ethernet/mellanox/mlx5/counters.html
Kenta Akagi (1):
net/mlx5e: Expose physical received bits counters to ethtool
drivers/net/ethernet/mellanox/mlx5/core/en_stats.c | 1 +
1 file changed, 1 insertion(+)
--
2.50.1
next reply other threads:[~2026-01-12 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 7:03 Kenta Akagi [this message]
2026-01-12 7:03 ` [PATCH RFC mlx5-next 1/1] net/mlx5e: Expose physical received bits counters to ethtool Kenta Akagi
2026-01-13 6:31 ` [PATCH RFC mlx5-next 0/1] " Tariq Toukan
2026-01-13 6:43 ` Tariq Toukan
2026-01-13 11:04 ` Kenta Akagi
2026-01-28 7:14 ` 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=20260112070324.38819-1-k@mgml.me \
--to=k@mgml.me \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@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