Received: by 2002:a05:7412:a9a2:b0:e2:908c:2ebd with SMTP id o34csp1811400rdh; Sat, 28 Oct 2023 08:04:00 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEjXAAAomLCv4C7fCqouW15bxj9A2N9/peEoYrROj0GIvETV+SWOCWZi0TZKXwL/3geCZU0 X-Received: by 2002:a05:6a20:4290:b0:15d:641b:57b6 with SMTP id o16-20020a056a20429000b0015d641b57b6mr6207125pzj.5.1698505439989; Sat, 28 Oct 2023 08:03:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698505439; cv=none; d=google.com; s=arc-20160816; b=HIvAvpPdv3+54t0efaEfk8Oy9Ai4tGGerUdJZWMgEIwQsRnZCDv88ZyYegs3sBtAMN c1B19zetWeWulx+cjeMgjgcMzumxruzYLBZg3xr3QqdIxm9fok4VLZrgqNYSGFusujFO LAMRy4s/qqly8LI43eCA7T82/NvCLUUhAJdFioPZQ9zKKga9rnbEVrsEn+Tnh+jqYsk7 F4WVTUfvta/Fmz1LtDtVbzKQbWnMj5JxHUTg3ZILYu52ZnIqheSJsBYAFoaHvmf/asRn 0F+w49czUec0Zp4p/C5L2ctLaftaje8YUvveVuY8hovcH+sh874vCQHXsdm8T1Ro4RaF ky/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date:dkim-signature; bh=JCgC8iEfqeVG5SmoD+Z1qjOZtlgkC88g0qaak8aF7AM=; fh=3LmCmoeI++7fvj4Amk21RFxhmK4UxO0aJN32IF5CBQk=; b=l8mbMFdWNDAid+ZMWJOopcgsTRpB2MwYUAo/Fk/Nx2V53z820vJwreaI3vt5rWPFyK Q9VdzdVA0ooD7O4QmQPc5dRNkBKJ+ajev+pyxPm/K4HGIlp6TRoJjHkTGpBXbzNn53vD JYtrrMZiPQAMtwGVhlMYNR/GN3JFoB69zOdUM4EDTJTOVl3iwRpzK5McgbJQdSZQ95QB A0S/vHkv4eLjMA3yE8e8fgDnF99mx1QvNFg9tEI8SXMD0+wkBz7Gf76v1+l6pe/de9kG TJswi9DFbFvb36LzxVzq/WBasvLf39RzT3ByzKJ6NGmo0oi9n7p4GRlWqvI2PjskOQk2 CGbg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@inria.fr header.s=dc header.b=HwvWRDA7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=inria.fr Return-Path: Received: from fry.vger.email (fry.vger.email. [23.128.96.38]) by mx.google.com with ESMTPS id x185-20020a6386c2000000b00584b293d17fsi2561717pgd.550.2023.10.28.08.03.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 28 Oct 2023 08:03:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38; Authentication-Results: mx.google.com; dkim=pass header.i=@inria.fr header.s=dc header.b=HwvWRDA7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=inria.fr Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id 5BD88809F3AF; Sat, 28 Oct 2023 08:03:57 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229461AbjJ1PDa (ORCPT + 99 others); Sat, 28 Oct 2023 11:03:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32922 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229446AbjJ1PDa (ORCPT ); Sat, 28 Oct 2023 11:03:30 -0400 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7D869D for ; Sat, 28 Oct 2023 08:03:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=JCgC8iEfqeVG5SmoD+Z1qjOZtlgkC88g0qaak8aF7AM=; b=HwvWRDA7Sgno0G1lAYJ4S8dFlOw/uCUwDTPVjlc61GeP9Fl7fV96iEfB u9SBd+tk6u+pE0SatqvwzY4NmVwZL84fjhx5soQ8lnE2clzkgBbFCh3Df HXpW/QvsvygxkReqhxcvSArAn14eWPH+SFjSgJWvec3LDNKb7Bj6FMSMF w=; Authentication-Results: mail2-relais-roc.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=julia.lawall@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr X-IronPort-AV: E=Sophos;i="6.03,259,1694728800"; d="scan'208";a="133701260" Received: from 231.85.89.92.rev.sfr.net (HELO hadrien) ([92.89.85.231]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2023 17:03:23 +0200 Date: Sat, 28 Oct 2023 17:03:23 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Chen Yu cc: Keisuke Nishimura , Ingo Molnar , Peter Zijlstra , Vincent Guittot , linux-kernel@vger.kernel.org, Dietmar Eggemann , Mel Gorman , Valentin Schneider , Ricardo Neri , Tim Chen Subject: Re: [PATCH] sched/fair: Fix the decision for load balance In-Reply-To: Message-ID: References: <20231027171742.1426070-1-keisuke.nishimura@inria.fr> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Sat, 28 Oct 2023 08:03:57 -0700 (PDT) On Sat, 28 Oct 2023, Chen Yu wrote: > On 2023-10-28 at 08:37:59 +0200, Julia Lawall wrote: > > > > > > On Sat, 28 Oct 2023, Chen Yu wrote: > > > > > On 2023-10-27 at 19:17:43 +0200, Keisuke Nishimura wrote: > > > > should_we_balance is called for the decision to do load-balancing. > > > > When sched ticks invoke this function, only one CPU should return > > > > true. However, in the current code, two CPUs can return true. The > > > > following situation, where b means busy and i means idle, is an > > > > example because CPU 0 and CPU 2 return true. > > > > > > > > [0, 1] [2, 3] > > > > b b i b > > > > > > > > This fix checks if there exists an idle CPU with busy sibling(s) > > > > after looking for a CPU on an idle core. If some idle CPUs with busy > > > > siblings are found, just the first one should do load-balancing. > > > > > > > > Fixes: b1bfeab9b002 ("sched/fair: Consider the idle state of the whole core for load balance") > > > > Signed-off-by: Keisuke Nishimura > > > > --- > > > > kernel/sched/fair.c | 5 +++-- > > > > 1 file changed, 3 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > > > > index 2048138ce54b..eff0316d6c7d 100644 > > > > --- a/kernel/sched/fair.c > > > > +++ b/kernel/sched/fair.c > > > > @@ -11083,8 +11083,9 @@ static int should_we_balance(struct lb_env *env) > > > > return cpu == env->dst_cpu; > > > > } > > > > > > > > - if (idle_smt == env->dst_cpu) > > > > - return true; > > > > + /* Is there an idle CPU with busy siblings? */ > > > > + if (idle_smt != -1) > > > > + return idle_smt == env->dst_cpu; > > > > > > > > /* Are we the first CPU of this group ? */ > > > > return group_balance_cpu(sg) == env->dst_cpu; > > > > > > Looks reasonable to me, if there is other idle SMT(from half-busy core) > > > in the system, we should leverage that SMT to do the periodic lb. > > > Per my understanding, > > > > That's not the goal of this patch. The goal of this patch is to avoid > > doing return group_balance_cpu(sg) == env->dst_cpu; > > Yes, I mean, without this patch, we could incorrectly choose the current > non idle CPU rather than that idle SMT, but actually we should let that > idle SMT to do the idle lb. OK, agreed. Thanks for the feedback! julia > > thanks, > Chenyu > > > when a half-busy core > > has been identified that is different from env->dst_cpu. > > > > julia > > > > > > > > Reviewed-by: Chen Yu > > > > > > thanks, > > > Chenyu > > > >