public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 30 Jul 2025 06:44:19 -0700	[thread overview]
Message-ID: <20250730064419.2588a5e3@kernel.org> (raw)
In-Reply-To: <bb66c931-ac17-4a70-ba11-2a109794b9e2@linux.dev>

On Wed, 30 Jul 2025 10:18:46 +0100 Vadim Fedorenko wrote:
> > IDK, 0,0 means all symbols were completely correct.
> > It may be useful for calculating bit error rate?  
> 
> The standard doesn't have this bin, its value can be potentially
> deducted from all packets counter.

We have a number of counters outside of the standard. Here the
extension is pretty trivial, so I don't see why we'd deprive
the user of the information HW collects. The translation between
bytes and symbols is not exact. Not sure we care about exactness
but, again, trivial to keep the 0,0 bin.

> > 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;  
> 
> I was thinking of this way, the problem is that in the core we rely on
> the driver to provide at least 2 bins and we cannot add any compile-time
> checks because it's all dynamic.

1 bin is no binning, its not a legit use of the histogram API. 
We have a counter for corrected symbols already, that's the "1 bin".

  reply	other threads:[~2025-07-30 13:44 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
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 [this message]
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=20250730064419.2588a5e3@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