From: Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, anton@samba.org,
mpe@ellerman.id.au, bsingharora@gmail.com,
David.Laight@ACULAB.COM, arnd@arndb.de
Subject: Re: [PATCH v4] cpuidle: Fix last_residency division
Date: Fri, 01 Jul 2016 19:46:35 +0530 [thread overview]
Message-ID: <57767B43.3000802@linux.vnet.ibm.com> (raw)
In-Reply-To: <577624A3.2000406@linaro.org>
On 07/01/2016 01:36 PM, Daniel Lezcano wrote:
> On 06/30/2016 05:37 PM, Nicolas Pitre wrote:
>> On Thu, 30 Jun 2016, Daniel Lezcano wrote:
>>> + }
>>>> +}
>>>
>>>
>>> What bothers me with this division is the benefit of adding an extra
>>> ultra
>>> optimized division by 1000 in cpuidle.h while we have already
>>> ktime_divns
>>> which is optimized in ktime.h.
>>
>> It is "optimized" but still much heavier than what is presented above as
>> it provides maximum precision.
>>
>> It all depends on how important the performance gain from the original
>> shift by 10 was in the first place.
>
> Actually the original shift was there because it was convenient as a
> simple ~div1000 operation. But against all odds, the approximation
> introduced a regression on a very specific use case on PowerPC.
>
> We are not in the hot path and I think we can live with a ktime_divns
> without problem. That would simplify the fix I believe.
>
I agree too. I'll post next version with this.
Thanks,
Shreyas
prev parent reply other threads:[~2016-07-01 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:34 [PATCH v4] cpuidle: Fix last_residency division Shreyas B. Prabhu
2016-06-30 14:57 ` Daniel Lezcano
2016-06-30 15:37 ` Nicolas Pitre
2016-07-01 8:06 ` Daniel Lezcano
2016-07-01 12:41 ` Balbir Singh
2016-07-01 13:02 ` Nicolas Pitre
2016-07-01 13:00 ` Nicolas Pitre
2016-07-01 14:16 ` Shreyas B Prabhu [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=57767B43.3000802@linux.vnet.ibm.com \
--to=shreyas@linux.vnet.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=bsingharora@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
/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).