From: Frank Rowand <frowand.list@gmail.com>
To: Chintan Pandya <cpandya@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()
Date: Wed, 28 Feb 2018 10:22:39 -0800 [thread overview]
Message-ID: <22ed033d-fd35-7f06-39e3-075c500492b4@gmail.com> (raw)
In-Reply-To: <ab87b605-6ec4-0b65-89ff-6232c89cb75f@codeaurora.org>
On 02/28/18 05:27, Chintan Pandya wrote:
>
>
> On 2/15/2018 6:22 AM, frowand.list@gmail.com wrote:
>
>> +static void of_populate_phandle_cache(void)
>> +{
>> + unsigned long flags;
>> + u32 cache_entries;
>> + struct device_node *np;
>> + u32 phandles = 0;
>> +
>> + raw_spin_lock_irqsave(&devtree_lock, flags);
>> +
>> + kfree(phandle_cache);
>> + phandle_cache = NULL;
>> +
>> + for_each_of_allnodes(np)
>> + if (np->phandle && np->phandle != OF_PHANDLE_ILLEGAL)
>> + phandles++;
>> +
>> + cache_entries = roundup_pow_of_two(phandles);
>> + phandle_cache_mask = cache_entries - 1;
>> +
>> + phandle_cache = kcalloc(cache_entries, sizeof(*phandle_cache),
>> + GFP_ATOMIC);
>> +
>
> NULL check of phandle_cache would be good to have.
Thanks for catching that.
>> + for_each_of_allnodes(np)
>> + if (np->phandle && np->phandle != OF_PHANDLE_ILLEGAL)
>> + phandle_cache[np->phandle & phandle_cache_mask] = np;
>> +
>> + raw_spin_unlock_irqrestore(&devtree_lock, flags);
>> +}
>
>
> Chintan
prev parent reply other threads:[~2018-02-28 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 0:52 [PATCH v3] of: cache phandle nodes to reduce cost of of_find_node_by_phandle() frowand.list
2018-02-16 9:04 ` Chintan Pandya
2018-02-16 22:20 ` Frank Rowand
2018-02-16 22:33 ` Frank Rowand
2018-02-28 13:27 ` Chintan Pandya
2018-02-28 18:22 ` Frank Rowand [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=22ed033d-fd35-7f06-39e3-075c500492b4@gmail.com \
--to=frowand.list@gmail.com \
--cc=cpandya@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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