lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2793441.QOukoFCf94@fedora.fritz.box>
Date: Fri, 03 Jan 2025 19:00:45 +0100
From: Francesco Valla <francesco@...la.it>
To: Andrew Lunn <andrew@...n.ch>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
 Andrew Lunn <andrew+netdev@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
 netdev@...r.kernel.org
Subject:
 Re: [PATCH] net: phy: don't issue a module request if a driver is available

On Thursday, 2 January 2025 at 15:21:51 Andrew Lunn <andrew@...n.ch> wrote:
> > > One other question, how much speadup do you get with async probe of
> > > PHYs? Is it really worth the effort?
> > 
> > For me it's a reduction of ~170ms, which currently accounts for roughly the 25%
> > of the time spent before starting userspace (660ms vs 490ms, give or take a
> > couple of milliseconds). That's due to the large reset time required by the PHYs
> > to initialize
> 
> 170ms seems like a long time for a reset. Maybe check the datasheet
> and see what it says.
> 
> 	Andrew
> 

Turned out that another 50-60ms could be shaven off. I trusted the original
implementation for the platform on the reset timings, but the datasheet used
the same name for two time quantities and they chose the wrong one.

Regards,
Francesco



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ