From: Jakub Kicinski <kuba@kernel.org>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Andrew Lunn <andrew@lunn.ch>,
Michael Chan <michael.chan@broadcom.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>,
Tariq Toukan <tariqt@nvidia.com>, Gal Pressman <gal@nvidia.com>,
intel-wired-lan@lists.osuosl.org,
Donald Hunter <donald.hunter@gmail.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [RFC PATCH] ethtool: add FEC bins histogramm report
Date: Tue, 29 Jul 2025 18:51:46 -0700 [thread overview]
Message-ID: <20250729185146.513504e0@kernel.org> (raw)
In-Reply-To: <424e38be-127d-49d8-98bf-1b4a2075d710@linux.dev>
On Tue, 29 Jul 2025 19:07:59 +0100 Vadim Fedorenko wrote:
> On 29/07/2025 18:31, Andrew Lunn wrote:
> >> The only one bin will have negative value is the one to signal the end
> >> of the list of the bins, which is not actually put into netlink message.
> >> It actually better to change spec to have unsigned values, I believe.
> >
> > Can any of these NICs send runt packets? Can any send packets without
> > an ethernet header and FCS?
> >
> > Seems to me, the bin (0,0) is meaningless, so can could be considered
> > the end marker. You then have unsigned everywhere, keeping it KISS.
>
> I had to revisit the 802.3df-2024, and it looks like you are right:
> "FEC_codeword_error_bin_i, where i=1 to 15, are optional 32-bit
> counters. While align_status is true, for each codeword received with
> exactly i correctable 10-bit symbols"
>
> That means bin (0,0) doesn't exist according to standard, so we can use
> it as a marker even though some vendors provide this bin as part of
> histogram.
IDK, 0,0 means all symbols were completely correct.
It may be useful for calculating bit error rate?
A workaround for having the {-1, -1} sentinel could also be to skip
the first entry:
if (i && !ranges[i].low && !ranges[i].high)
break;
next prev parent reply other threads:[~2025-07-30 1:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 10:23 [RFC PATCH] ethtool: add FEC bins histogramm report Vadim Fedorenko
2025-07-29 13:48 ` Andrew Lunn
2025-07-29 16:01 ` Vadim Fedorenko
2025-07-29 16:17 ` Andrew Lunn
2025-07-29 16:36 ` Vadim Fedorenko
2025-07-29 17:31 ` Andrew Lunn
2025-07-29 18:07 ` Vadim Fedorenko
2025-07-30 1:51 ` Jakub Kicinski [this message]
2025-07-30 5:39 ` Gal Pressman
2025-07-30 12:59 ` Andrew Lunn
2025-07-30 13:54 ` Gal Pressman
2025-07-30 9:18 ` Vadim Fedorenko
2025-07-30 13:44 ` Jakub Kicinski
2025-07-30 14:39 ` Vadim Fedorenko
2025-07-30 1:45 ` Jakub Kicinski
2025-07-30 9:22 ` Vadim Fedorenko
2025-07-30 13:45 ` Jakub Kicinski
2025-07-30 1:48 ` Jakub Kicinski
2025-07-30 5:54 ` Gal Pressman
2025-07-30 9:29 ` Vadim Fedorenko
2025-07-30 10:42 ` Gal Pressman
2025-07-30 11:32 ` Vadim Fedorenko
2025-07-30 13:47 ` Gal Pressman
2025-07-30 14:15 ` Andrew Lunn
2025-07-30 12:08 ` Carolina Jubran
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=20250729185146.513504e0@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=donald.hunter@gmail.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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