[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200515053500.215929-1-saravanak@google.com>
Date: Thu, 14 May 2020 22:34:56 -0700
From: Saravana Kannan <saravanak@...gle.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Len Brown <lenb@...nel.org>
Cc: Saravana Kannan <saravanak@...gle.com>, kernel-team@...roid.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-acpi@...r.kernel.org, Ji Luo <ji.luo@....com>
Subject: [PATCH v1 0/4] Optimize fw_devlink parsing
When fw_devlink is enabled on hardware with a large number of device
tree nodes, the initial device addition done in
of_platform_default_populate_init() can be very inefficient. This is
because most devices will fail to find all their suppliers when they are
added and will keep trying to parse their device tree nodes and link to
any newly added devices
This was an item on my TODO list that I'm finally getting around to. On
hardware I'm testing on, this saved 1.216 _seconds_! Another SoC vendor
was also able to test a similar but hacky patch series and confirmed
that it saved them around 1 second.
Thanks,
Saravana
P.S: It took me longer to write the comments than the code!
Saravana Kannan (4):
driver core: Move code to the right part of the file
driver core: Look for waiting consumers only for a fwnode's primary
device
driver core: fw_devlink: Add support for batching fwnode parsing
of: platform: Batch fwnode parsing when adding all top level devices
drivers/base/base.h | 1 +
drivers/base/core.c | 193 ++++++++++++++++++++++++++++++++---------
drivers/base/dd.c | 8 ++
drivers/of/platform.c | 2 +
include/linux/fwnode.h | 2 +
5 files changed, 164 insertions(+), 42 deletions(-)
--
2.26.2.761.g0e0b3e54be-goog
Powered by blists - more mailing lists