From: Chris Redpath Date: Fri, 11 Oct 2013 10:44:58 +0000 (+0100) Subject: sched: HMP: Change default HMP thresholds X-Git-Tag: firefly_0821_release~3680^2~16^2^2~41 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=d73babce9a77f8143136fe0d7b6c1ae44b5652dc;p=firefly-linux-kernel-4.4.55.git sched: HMP: Change default HMP thresholds When the up-threshold is at 512 on TC2, behaviour looks OK since the graphic-related tasks are very heavy due to lack of a GPU. Increasing the up-threshold does not reduce power consumption. When a GPU is present, graphic tasks are much less CPU-heavy and so additional power may be saved by having a higher threshold. Signed-off-by: Chris Redpath Signed-off-by: Liviu Dudau Signed-off-by: Jon Medhurst --- diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 754634e774ad..62a93c62a84a 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -3663,15 +3663,13 @@ static struct sched_entity *hmp_get_lightest_task( * Migration thresholds should be in the range [0..1023] * hmp_up_threshold: min. load required for migrating tasks to a faster cpu * hmp_down_threshold: max. load allowed for tasks migrating to a slower cpu - * The default values (512, 256) offer good responsiveness, but may need - * tweaking suit particular needs. * * hmp_up_prio: Only up migrate task with high priority (