From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Balbir Singh <bsingharora@gmail.com>,
"Shreyas B. Prabhu" <shreyas@linux.vnet.ibm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: [PATCH v5] cpuidle: Fix last_residency division
Date: Mon, 4 Jul 2016 14:20:59 +0200 [thread overview]
Message-ID: <CAJZ5v0jCTr607OTekNVuYGDmA=ObhgVKDrHdSWB-metEpuydXQ@mail.gmail.com> (raw)
In-Reply-To: <5102d9f9-3b38-17c3-98ce-cceb073da764@gmail.com>
On Mon, Jul 4, 2016 at 8:10 AM, Balbir Singh <bsingharora@gmail.com> wrote:
>
>
> On 02/07/16 00:24, Shreyas B. Prabhu wrote:
>> Snooze is a poll idle state in powernv and pseries platforms. Snooze
>> has a timeout so that if a cpu stays in snooze for more than target
>> residency of the next available idle state, then it would exit thereby
>> giving chance to the cpuidle governor to re-evaluate and
>> promote the cpu to a deeper idle state. Therefore whenever snooze exits
>> due to this timeout, its last_residency will be target_residency of next
>> deeper state.
>>
>> commit e93e59ce5b85 ("cpuidle: Replace ktime_get() with local_clock()")
>> changed the math around last_residency calculation. Specifically, while
>> converting last_residency value from nanoseconds to microseconds it does
>> right shift by 10. Due to this, in snooze timeout exit scenarios
>> last_residency calculated is roughly 2.3% less than target_residency of
>> next available state. This pattern is picked up get_typical_interval()
>> in the menu governor and therefore expected_interval in menu_select() is
>> frequently less than the target_residency of any state but snooze.
>>
>> Due to this we are entering snooze at a higher rate, thereby affecting
>> the single thread performance.
>>
>> Fix this by using precise division via ktime_us_delta.
>>
>> Reported-by: Anton Blanchard <anton@samba.org>
>> Bisected-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
>> Signed-off-by: Shreyas B. Prabhu <shreyas@linux.vnet.ibm.com>
>> ---
>
> This looks so much cleaner :)
>
> Acked-by: Balbir Singh <bsingharora@gmail.com>
Patch applied, thanks!
prev parent reply other threads:[~2016-07-04 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 14:24 [PATCH v5] cpuidle: Fix last_residency division Shreyas B. Prabhu
2016-07-01 14:32 ` Daniel Lezcano
2016-07-04 6:10 ` Balbir Singh
2016-07-04 12:20 ` Rafael J. Wysocki [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='CAJZ5v0jCTr607OTekNVuYGDmA=ObhgVKDrHdSWB-metEpuydXQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=bsingharora@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=shreyas@linux.vnet.ibm.com \
/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).