From e640249dbade56af7bc968fce2f5ede230602e6e Mon Sep 17 00:00:00 2001 From: Syed Rameez Mustafa Date: Fri, 25 Apr 2014 12:27:25 -0700 Subject: sched/fair: Limit MAX_PINNED_INTERVAL for more frequent load balancing Should the system get stuck in a state where load balancing is failing due to all tasks being pinned, deferring load balancing for up to half a second may cause further performance problems. Eventually all tasks will not be pinned and load balancing should not be deferred for a great length of time. Change-Id: I06f93b5448353b5871645b9274ce4419dc9fae0f Signed-off-by: Syed Rameez Mustafa Signed-off-by: Srivatsa Vaddagiri --- kernel/sched/fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'kernel') diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index cabc223ffd32..b04af1c436cc 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -7699,7 +7699,7 @@ static struct rq *find_busiest_queue(struct lb_env *env, * Max backoff if we encounter pinned tasks. Pretty arbitrary value, but * so long as it is large enough. */ -#define MAX_PINNED_INTERVAL 512 +#define MAX_PINNED_INTERVAL 16 /* Working cpumask for load_balance and load_balance_newidle. */ DEFINE_PER_CPU(cpumask_var_t, load_balance_mask); -- cgit v1.2.3