On Thu, Jan 25, 2018 at 4:14 AM, Chintan Pandya <cpandya@xxxxxxxxxxxxxx> wrote:On my SDM device, I see total saving of 400ms during boot time. For some clients
of_find_node_by_phandle() takes a lot of time findingGot some numbers for what is "a lot of time"?
Yes, will correct this if original is confusing.
right node when your intended device is too right-sideBy right side, you mean a deep path?
in the fdt. Reason is, we search each device serially
from the fdt, starting from left-most to right-most.
Sure. My bad.
Implement, device-phandle relation in hash-table soRun checkpatch.pl
that look up can be faster.
Change-Id: I4a2bc7eff6de142e4f91a7bf474893a45e61c128
Ok, sure.
@@ -61,6 +62,7 @@ struct device_node {Always base your patches on the latest -rc at least. This won't apply.
struct kobject kobj;
unsigned long _flags;
void *data;
+ struct hlist_node hash;
On my system, there are ~6.7k calls of this API during boot.
This grows struct device_node for every single node which we recently
worked on to shrink (which is why this won't apply). So I'm now
sensitive to anything that grows it. I'd really prefer something out
of band.
I'd guess that there's really only a few phandle lookups that occur
over and over.
The clock controller, interrupt controller, etc. WhatI clearly see repeat calling with same phandle. But I have few hundreds of nodes.
if you just had a simple array of previously found nodes for a cache
and of_find_node_by_phandle can check that array first. Probably 8-16
entries would be enough.