From: patchwork-bot+netdevbpf@kernel.org
To: Klaus Kudielka <klaus.kudielka@gmail.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/4] net: dsa: mv88e6xxx: accelerate C45 scan
Date: Sat, 18 Mar 2023 05:40:19 +0000 [thread overview]
Message-ID: <167911801910.9150.1802116889596947531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230315163846.3114-1-klaus.kudielka@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 15 Mar 2023 17:38:42 +0100 you wrote:
> Starting with commit 1a136ca2e089 ("net: mdio: scan bus based on bus
> capabilities for C22 and C45"), mdiobus_scan_bus_c45() is being called on
> buses with MDIOBUS_NO_CAP. On a Turris Omnia (Armada 385, 88E6176 switch),
> this causes a significant increase of boot time, from 1.6 seconds, to 6.3
> seconds. The boot time stated here is until start of /init.
>
> Further testing revealed that the C45 scan is indeed expensive (around
> 2.7 seconds, due to a huge number of bus transactions), and called twice.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/4] net: dsa: mv88e6xxx: don't dispose of Global2 IRQ mappings from mdiobus code
https://git.kernel.org/netdev/net-next/c/b1a2de9ccfe6
- [net-next,v4,2/4] net: dsa: mv88e6xxx: re-order functions
https://git.kernel.org/netdev/net-next/c/f1bee740fa82
- [net-next,v4,3/4] net: dsa: mv88e6xxx: move call to mv88e6xxx_mdios_register()
https://git.kernel.org/netdev/net-next/c/2cb0658d4f88
- [net-next,v4,4/4] net: dsa: mv88e6xxx: mask apparently non-existing phys during probing
https://git.kernel.org/netdev/net-next/c/2c7e46edbd03
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-18 5:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 16:38 [PATCH net-next v4 0/4] net: dsa: mv88e6xxx: accelerate C45 scan Klaus Kudielka
2023-03-15 16:38 ` [PATCH net-next v4 1/4] net: dsa: mv88e6xxx: don't dispose of Global2 IRQ mappings from mdiobus code Klaus Kudielka
2023-03-17 15:30 ` Vladimir Oltean
2023-03-17 17:06 ` Florian Fainelli
2023-03-15 16:38 ` [PATCH net-next v4 2/4] net: dsa: mv88e6xxx: re-order functions Klaus Kudielka
2023-03-17 15:31 ` Vladimir Oltean
2023-03-17 17:07 ` Florian Fainelli
2023-03-15 16:38 ` [PATCH net-next v4 3/4] net: dsa: mv88e6xxx: move call to mv88e6xxx_mdios_register() Klaus Kudielka
2023-03-17 15:32 ` Vladimir Oltean
2023-03-17 17:07 ` Florian Fainelli
2023-03-15 16:38 ` [PATCH net-next v4 4/4] net: dsa: mv88e6xxx: mask apparently non-existing phys during probing Klaus Kudielka
2023-03-17 15:33 ` Vladimir Oltean
2023-03-17 17:07 ` Florian Fainelli
2023-03-19 10:06 ` Marek Behún
2023-03-19 13:34 ` Vladimir Oltean
2023-03-19 13:35 ` Vladimir Oltean
2023-03-18 5:40 ` patchwork-bot+netdevbpf [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=167911801910.9150.1802116889596947531.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=klaus.kudielka@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).