From: Rik van Riel <riel@redhat.com>
To: Youquan Song <youquan.song@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
arjan@linux.intel.com, lenb@kernel.org,
Youquan Song <youquan.song@linux.intel.com>
Subject: Re: [PATCH V2 1/3] x86,idle: Quickly notice prediction failure for repeat mode
Date: Mon, 17 Sep 2012 09:59:45 -0400 [thread overview]
Message-ID: <50572CD1.700@redhat.com> (raw)
In-Reply-To: <1347933209-25939-2-git-send-email-youquan.song@intel.com>
On 09/17/2012 09:53 PM, Youquan Song wrote:
> The prediction for future is difficult and when the cpuidle governor prediction
> fails and govenor possibly choose the shallower C-state than it should. How to
> quickly notice and find the failure becomes important for power saving.
>
> cpuidle menu governor has a method to predict the repeat pattern if there are 8
> C-states residency which are continuous and the same or very close, so it will
> predict the next C-states residency will keep same residency time.
Could I convince you to try out my variation on
detect_repeating_intervals? :)
http://people.redhat.com/riel/cstate/cstate-stddev-converge.patch
I suspect that small change might help your code adapt to changed
conditions even faster.
--
All rights reversed
next prev parent reply other threads:[~2012-09-17 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 1:53 [PATCH V2 0/3] x86,idle: Enhance cpuidle prediction to handle its failure Youquan Song
2012-09-17 14:52 ` Daniel Lezcano
2012-09-18 3:30 ` Youquan Song
2012-09-17 20:32 ` Daniel Lezcano
2012-09-18 1:53 ` [PATCH V2 1/3] x86,idle: Quickly notice prediction failure for repeat mode Youquan Song
2012-09-17 13:59 ` Rik van Riel [this message]
2012-09-18 2:15 ` Youquan Song
2012-09-18 1:53 ` [PATCH V2 2/3] x86,idle: Quickly notice prediction failure in general case Youquan Song
2012-09-18 1:53 ` [PATCH V2 3/3] x86,idle: Set residency to 0 if target Cstate not really enter Youquan Song
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=50572CD1.700@redhat.com \
--to=riel@redhat.com \
--cc=arjan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=youquan.song@intel.com \
--cc=youquan.song@linux.intel.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).