[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d6c5a1c4-e41f-d239-e0b0-15eba3e78274@gmail.com>
Date: Thu, 26 Mar 2020 19:56:29 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>, davem@...emloft.net,
kuba@...nel.org
Cc: alexander.duyck@...il.com,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Aaron Brown <aaron.f.brown@...el.com>,
Michal Kubecek <mkubecek@...e.cz>,
Andrew Lunn <andrew@...n.ch>,
Maxime Chevallier <maxime.chevallier@...tlin.com>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ethtool: Report speed and duplex as unknown when device
is runtime suspended
On 3/26/2020 7:45 PM, Kai-Heng Feng wrote:
> Device like igb gets runtime suspended when there's no link partner. We
> can't get correct speed under that state:
> $ cat /sys/class/net/enp3s0/speed
> 1000
>
> In addition to that, an error can also be spotted in dmesg:
> [ 385.991957] igb 0000:03:00.0 enp3s0: PCIe link lost
>
> Since device can only be runtime suspended when there's no link partner,
> we can directly report the speed and duplex as unknown.
>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> Cc: Aaron Brown <aaron.f.brown@...el.com>
> Suggested-by: Alexander Duyck <alexander.duyck@...il.com>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@...onical.com>
I would push this to the responsibility of the various drivers instead
of making this part of the standard ethtool implementation.
--
Florian
Powered by blists - more mailing lists