summaryrefslogtreecommitdiffstats
path: root/crypto/sm4_generic.c
diff options
context:
space:
mode:
authorVincent Guittot <vincent.guittot@linaro.org>2020-06-24 17:44:22 +0200
committerBorislav Petkov <bp@suse.de>2020-06-28 17:01:20 +0200
commite21cf43406a190adfcc4bfe592768066fb3aaa9b (patch)
treee5f7d137033c19c399fc285d5931a737f7be4f2f /crypto/sm4_generic.c
parent8c4890d1c3358fb8023d46e1e554c41d54f02878 (diff)
downloadlinux-e21cf43406a190adfcc4bfe592768066fb3aaa9b.tar.bz2
sched/cfs: change initial value of runnable_avg
Some performance regression on reaim benchmark have been raised with commit 070f5e860ee2 ("sched/fair: Take into account runnable_avg to classify group") The problem comes from the init value of runnable_avg which is initialized with max value. This can be a problem if the newly forked task is finally a short task because the group of CPUs is wrongly set to overloaded and tasks are pulled less agressively. Set initial value of runnable_avg equals to util_avg to reflect that there is no waiting time so far. Fixes: 070f5e860ee2 ("sched/fair: Take into account runnable_avg to classify group") Reported-by: kernel test robot <rong.a.chen@intel.com> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lkml.kernel.org/r/20200624154422.29166-1-vincent.guittot@linaro.org
Diffstat (limited to 'crypto/sm4_generic.c')
0 files changed, 0 insertions, 0 deletions