From: Jakub Kicinski <kuba@kernel.org>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Vadim Fedorenko <vadfed@meta.com>, 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:45:19 -0700 [thread overview]
Message-ID: <20250730064519.38abc0c3@kernel.org> (raw)
In-Reply-To: <15ca2392-1dbd-4f4d-a478-3d8edc32bc90@linux.dev>
On Wed, 30 Jul 2025 10:22:36 +0100 Vadim Fedorenko wrote:
> >> + name: fec-hist
> >> + subset-of: fec-stat
> >
> > no need to make this a subset, better to make it its own attr set
>
> like a set for general histogram? or still fec-specific?
You can make it a general histogram, I guess 🤔️
No strong preference.
> >> + attributes:
> >> + -
> >> + name: fec-hist-bin-low
> >> + -
> >> + name: fec-hist-bin-high
> >> + -
> >> + name: fec-hist-bin-val
> >> -
> >> name: fec
> >> attr-cnt-name: __ethtool-a-fec-cnt
> >
> >> +static const struct ethtool_fec_hist_range netdevsim_fec_ranges[] = {
> >> + { 0, 0},
> >> + { 1, 3},
> >> + { 4, 7},
> >> + { -1, -1}
> >> +};
> >
> > Let's add a define for the terminating element?
>
> I believe it's about (-1, -1) case. If we end up using (0, 0) then there
> is no need to define anything, right?
Yup, 0,0 is better written as {} so no need for a define.
next prev parent reply other threads:[~2025-07-30 13:45 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
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 [this message]
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=20250730064519.38abc0c3@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=vadfed@meta.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