From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757366AbaJIPAG (ORCPT ); Thu, 9 Oct 2014 11:00:06 -0400 Received: from mail-oi0-f48.google.com ([209.85.218.48]:36680 "EHLO mail-oi0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752514AbaJIO75 (ORCPT ); Thu, 9 Oct 2014 10:59:57 -0400 MIME-Version: 1.0 In-Reply-To: <20141009112352.GO4750@worktop.programming.kicks-ass.net> References: <1412684017-16595-1-git-send-email-vincent.guittot@linaro.org> <1412684017-16595-3-git-send-email-vincent.guittot@linaro.org> <20141009112352.GO4750@worktop.programming.kicks-ass.net> From: Vincent Guittot Date: Thu, 9 Oct 2014 16:59:36 +0200 Message-ID: Subject: Re: [PATCH v7 2/7] sched: move cfs task on a CPU with higher capacity To: Peter Zijlstra Cc: Ingo Molnar , linux-kernel , Preeti U Murthy , Morten Rasmussen , Kamalesh Babulal , Russell King - ARM Linux , LAK , Rik van Riel , Mike Galbraith , Nicolas Pitre , "linaro-kernel@lists.linaro.org" , Daniel Lezcano , Dietmar Eggemann , Paul Turner , Benjamin Segall Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9 October 2014 13:23, Peter Zijlstra wrote: > On Tue, Oct 07, 2014 at 02:13:32PM +0200, Vincent Guittot wrote: >> +++ b/kernel/sched/fair.c >> @@ -5896,6 +5896,18 @@ fix_small_capacity(struct sched_domain *sd, struct sched_group *group) >> } >> >> /* >> + * Check whether the capacity of the rq has been noticeably reduced by side >> + * activity. The imbalance_pct is used for the threshold. >> + * Return true is the capacity is reduced >> + */ >> +static inline int >> +check_cpu_capacity(struct rq *rq, struct sched_domain *sd) >> +{ >> + return ((rq->cpu_capacity * sd->imbalance_pct) < >> + (rq->cpu_capacity_orig * 100)); >> +} >> + >> +/* >> * Group imbalance indicates (and tries to solve) the problem where balancing >> * groups is inadequate due to tsk_cpus_allowed() constraints. >> * >> @@ -6567,6 +6579,14 @@ static int need_active_balance(struct lb_env *env) >> */ >> if ((sd->flags & SD_ASYM_PACKING) && env->src_cpu > env->dst_cpu) >> return 1; >> + >> + /* >> + * The src_cpu's capacity is reduced because of other >> + * sched_class or IRQs, we trig an active balance to move the >> + * task >> + */ >> + if (check_cpu_capacity(env->src_rq, sd)) >> + return 1; >> } > > So does it make sense to first check if there's a better candidate at > all? By this time we've already iterated the current SD while trying > regular load balancing, so we could know this. i'm not sure to completely catch your point. Normally, f_b_g and f_b_q have already looked at the best candidate when we call need_active_balance. And src_cpu has been elected. Or i have missed your point ? > >