summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@linux.intel.com>2010-05-24 14:32:59 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2010-05-25 08:07:02 -0700
commit1f85f87d4f81d1e5a2d502d48316a1bdc5acac0b (patch)
treeef9254e52665274ae4d0fd1381cc2ae5a48791f6 /firmware
parent6cdafaae41d52e6ef9a5c5be23602ef083e4d0f9 (diff)
downloadlinux-1f85f87d4f81d1e5a2d502d48316a1bdc5acac0b.tar.bz2
cpuidle: add a repeating pattern detector to the menu governor
Currently, the menu governor uses the (corrected) next timer as key item for predicting the idle duration. It turns out that there are specific cases where this breaks down: There are cases where we have a very repetitive pattern of idle durations, where the idle period is pretty much the same, for reasons completely unrelated to the next timer event. Examples of such repeating patterns are network loads with irq mitigation, the mouse moving but in theory also the wifi beacons. This patch adds a relatively simple detector for such repeating patterns, where the standard deviation of the last 8 idle periods is compared to a threshold. With this extra predictor in place, measurements show that the DECAY factor can now be increased (the decaying average will now decay slower) to get an even more stable result. [arjan@infradead.org: fix bug identified by Frank] Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Cc: Corrado Zoccolo <czoccolo@gmail.com> Cc: Frank Rowand <frank.rowand@am.sony.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions