Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Pei Lee Ling <pei.lee.ling@intel.com>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, shubham.das@intel.com,
	siddaraju.dh@intel.com, balaji.chintalapalle@intel.com
Subject: Re: [RFC PATCH net-next 0/1] Add Clear fec-stats ethtool handler
Date: Mon, 21 Sep 2026 13:13:35 -0700	[thread overview]
Message-ID: <20260921131335.7f2dc18e@kernel.org> (raw)
In-Reply-To: <20260921154637.2376544-1-pei.lee.ling@intel.com>

On Mon, 21 Sep 2026 10:46:36 -0500 Pei Lee Ling wrote:
> ethtool: Add Clear fec-stats ethtool handler 
> 
> During optical cable re-seating, transceiver swaps, or Bit Error Rate (BER) 
> troubleshooting on 25G/100G/400G+ links, operators need to establish 
> a clean baseline for physical-layer FEC error counters (corrected/uncorrectable blocks).
> 
> Introduce a standardized netlink fec-clear operation using the ETHTOOL_MSG_FEC_SET 
> message type with an ETHTOOL_A_FEC_STATS_CLEAR attribute. This provides a consistent and
> non-disruptive management interface that can be uniformly supported 
> across all required drivers.

What do you really needs this for? Some local testing?
Any real deployment will be computing deltas for counters
so resettings counters would be meaningless or worse it will
make deltas negative. Perhaps you can fix your tests ?

      parent reply	other threads:[~2026-09-21 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 15:46 [RFC PATCH net-next 0/1] Add Clear fec-stats ethtool handler Pei Lee Ling
2026-09-21 15:46 ` [RFC PATCH net-next 1/1] ethtool: Add Clear-fec-stats " Pei Lee Ling
2026-09-21 18:48 ` [RFC PATCH net-next 0/1] Add Clear fec-stats " Andrew Lunn
2026-09-21 20:13 ` Jakub Kicinski [this message]

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=20260921131335.7f2dc18e@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=balaji.chintalapalle@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pei.lee.ling@intel.com \
    --cc=shubham.das@intel.com \
    --cc=siddaraju.dh@intel.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