Netdev List
 help / color / mirror / Atom feed
From: "Creeley, Brett" <bcreeley@amd.com>
To: Breno Leitao <leitao@debian.org>, Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	brett.creeley@amd.com, eric.joyner@amd.com
Subject: Re: [PATCH net-next] eth: ionic: delete the incorrect link_down_count reporting
Date: Mon, 15 Jun 2026 10:29:54 -0700	[thread overview]
Message-ID: <3193fb6f-d786-4b8a-ace3-d63264c95529@amd.com> (raw)
In-Reply-To: <ajAye8LnVeqkcGLZ@gmail.com>



On 6/15/2026 10:14 AM, Breno Leitao wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Mon, Jun 15, 2026 at 10:01:53AM -0700, Jakub Kicinski wrote:
>> The definition of the statistic is quite clear,
>> struct ethtool_link_ext_stats says:
>>
>>     This statistic counts when PHY _actually_ went down, or lost link.
>>
>> Reportedly this is not how the device-counted stat on ionic behaves.
>> The goal is to detect flapping links, due to bad cabling.
>> ionic reportedly uses this for some firmware stat of how many times
>> the traffic was stopped. This is _not_ what should be reported here.
>>
>> Link: https://lore.kernel.org/20260610061830.51037-1-eric.joyner@amd.com
>> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Acked-by: Breno Leitao <leitao@debian.org>
>
> CC: brett.creeley@amd.com
>> CC: eric.joyner@amd.com
>> CC: leitao@debian.org
>> ---
>>   drivers/net/ethernet/pensando/ionic/ionic_ethtool.c | 10 ----------
>>   1 file changed, 10 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/pensando/ionic/ionic_ethtool.c b/drivers/net/ethernet/pensando/ionic/ionic_ethtool.c
>> index 78a802eb159f..f7dcfe3d032d 100644
>> --- a/drivers/net/ethernet/pensando/ionic/ionic_ethtool.c
>> +++ b/drivers/net/ethernet/pensando/ionic/ionic_ethtool.c
>> @@ -111,15 +111,6 @@ static void ionic_get_regs(struct net_device *netdev, struct ethtool_regs *regs,
>>        memcpy_fromio(p + offset, idev->dev_cmd_regs->words, size);
>>   }
>>
>> -static void ionic_get_link_ext_stats(struct net_device *netdev,
>> -                                  struct ethtool_link_ext_stats *stats)
>> -{
>> -     struct ionic_lif *lif = netdev_priv(netdev);
>> -
>> -     if (lif->ionic->pdev->is_physfn)
>> -             stats->link_down_events = lif->link_down_count;
> It seems this is the only place where link_down_count is read. Maybe you
> want to kill it as well?

It still shows in debugfs, but we'd be fine with it being removed 
completely in favor of the correct implementation from Eric at: 
https://lore.kernel.org/netdev/20260614205303.48088-5-eric.joyner@amd.com/.

Thanks,

Brett


      reply	other threads:[~2026-06-15 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15 17:01 [PATCH net-next] eth: ionic: delete the incorrect link_down_count reporting Jakub Kicinski
2026-06-15 17:14 ` Breno Leitao
2026-06-15 17:29   ` Creeley, Brett [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=3193fb6f-d786-4b8a-ace3-d63264c95529@amd.com \
    --to=bcreeley@amd.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=brett.creeley@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.joyner@amd.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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