From: Chintan Pandya <cpandya@codeaurora.org>
To: Frank Rowand <frowand.list@gmail.com>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: cache phandle nodes to decrease cost of of_find_node_by_phandle()
Date: Thu, 1 Feb 2018 16:01:58 +0530 [thread overview]
Message-ID: <9e23d32f-05a0-ce8a-41f8-9a1a3d66be37@codeaurora.org> (raw)
In-Reply-To: <38cdcae5-ec0f-d1be-b024-1990d4387731@gmail.com>
>> Anyways, will fix this locally and share test results.
>
> Thanks, I look forward to the results.
>
Set up for this time was slightly different. So, taken all the numbers
again.
Boot to shell time (in ms): Experiment 2
[1] Base : 14.843805 14.784842 14.842338
[2] 64 sized fixed cache : 14.189292 14.200003 14.266711
[3] Dynamic freeable cache : 14.112412 14.064772 14.036052
So, [3] (this patch) looks to be improving 750ms (on avg from base build).
--
Qualcom India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum, a Linux Foundation
Collaborative Project
next prev parent reply other threads:[~2018-02-01 10:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 20:05 frowand.list
2018-01-31 20:10 ` Frank Rowand
2018-01-31 21:43 ` Frank Rowand
2018-02-01 14:24 ` Rob Herring
2018-02-01 14:26 ` Rob Herring
2018-02-01 21:09 ` Frank Rowand
2018-02-02 3:45 ` Rob Herring
2018-02-02 22:34 ` Frank Rowand
2018-02-02 5:53 ` Chintan Pandya
2018-02-03 3:55 ` Frank Rowand
2018-02-01 6:45 ` Chintan Pandya
2018-02-01 8:59 ` Frank Rowand
2018-02-01 10:31 ` Chintan Pandya [this message]
2018-02-01 19:10 ` Frank Rowand
2018-02-02 5:59 ` Chintan Pandya
2018-02-02 21:26 ` Frank Rowand
2018-02-05 12:23 ` Chintan Pandya
2018-02-07 12:44 ` Chintan Pandya
2018-02-07 20:09 ` Frank Rowand
2018-02-01 14:34 ` Rob Herring
2018-02-01 21:13 ` Frank Rowand
-- strict thread matches above, loose matches on Subject: below --
2018-01-31 20:02 frowand.list
2018-01-31 20:07 ` Frank Rowand
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=9e23d32f-05a0-ce8a-41f8-9a1a3d66be37@codeaurora.org \
--to=cpandya@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--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
Powered by JetHome