Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp1566448rwr; Fri, 5 May 2023 16:42:30 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7dDJOloMx5fV4lyT7l0xS0lSFPdJhIlTZrg8B4R8GcFupH3GbIkZ9kRLNwPnFfD4QaFcXR X-Received: by 2002:a05:6a20:3ca9:b0:f3:3ea5:5185 with SMTP id b41-20020a056a203ca900b000f33ea55185mr4039950pzj.10.1683330150433; Fri, 05 May 2023 16:42:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683330150; cv=none; d=google.com; s=arc-20160816; b=pmH9JIO/mfPeoLYYxwdsZBxcxBkoxK+7ns8fhMNBSWyNsJIOAjTkgUdB8ZeQZmWwfJ OLx5A8Bl3nLLQGmqgMA5Hav4e3RviUSAFac33SaKTq8VtMlBqNyGPjuVhu2CsExC2hwq loa/LaI1w9mc237dg0slNGA3bK+k3FoH8F3MByMhZ7gsFnFWVx1ckA4CU6FjTdDmwW4G PGARRuct+jYymC5WliY6x7SZXW54MhHzUCQH1wDSQflrgeAHmLteigD0bpGKWzepJfq3 CL3kuPibkJ3T+rp1gEn+gglHSQDQyyY0uaLWJV+6WfJ+3pJ4M+HnXuZcYRjHbq7Z9F3e +dmQ== 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 :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=/9TVslmwX5A+yWAH+VNhEf7+pDOmOY7yUhPP8ylk9iw=; b=t9WmXx/6ZW89Nl4IftZgv6QC/fsknH+Y5qmRzYtQxfjQAVu2Yf0QXxYMgM3IbS1K9a yoOjfb/xgf8NWOHes+8Zv4kJ3zUKJ9LL8eCuX45L1sVLC5q47jaMpFdekF1pCXbMF47U Xu7XcGy/RocXuv8l51lLvD8HIuLMgA4Rh0XeS554diiMBgX+ZSdrNQMZzVM9Jmj77vEh OYaJvgBDEd8Y5K141uxyNXwkKsFnftqfR5Yw6O1pHLMOkeMfaNAOlq2NSEKOnfzMC2fR LTf1n8imRq7xD6x5CZ79lJK7DL/3PezQJNkaEJ6jLdLmf3SKgVSqzOn51wCGEt5NVrsF AkGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=hYz+Y34V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m12-20020a633f0c000000b0051b85b5a3d1si2968015pga.127.2023.05.05.16.42.13; Fri, 05 May 2023 16:42:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=hYz+Y34V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230371AbjEEXHn (ORCPT + 99 others); Fri, 5 May 2023 19:07:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59972 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229819AbjEEXHl (ORCPT ); Fri, 5 May 2023 19:07:41 -0400 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 61A6E3598 for ; Fri, 5 May 2023 16:07:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1683328060; x=1714864060; h=message-id:subject:from:to:cc:date:in-reply-to: references:content-transfer-encoding:mime-version; bh=CxdlYALuIwm8JyKBywdAOVuE4rIPcmX0leYCKwfv6c4=; b=hYz+Y34V1zArMM3CRqtpewAhwQIS5KvgDhrGI2YD+BATXCyl7GoCh45t sOwh+EbEzT1sYkIeVF6I0SxAWbntKXnuATk8nbAAcSv2BEUKALELtu9R/ mGHKwFOYOQyL97jquK6U5GE7loSp56iSeur6dRFGiKWB4+cWikX847cL3 EzsltW3BNWFge2AHqWGdy7dym7seZXzUH9A+70Fl+CDdV8GKsq2+gjAKY GNIVHgqv+sizVFOU9ZFhZOgb0pfzG7vyhUWl4K1jsMRxeBEea7eeATpfv TIM2kJq8b1OkB9OjIMntfq/4EhKg7OcuJ4Q1cxX1P+n/HYzYWVEC13hVR w==; X-IronPort-AV: E=McAfee;i="6600,9927,10701"; a="352366436" X-IronPort-AV: E=Sophos;i="5.99,253,1677571200"; d="scan'208";a="352366436" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2023 16:07:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10701"; a="821899152" X-IronPort-AV: E=Sophos;i="5.99,253,1677571200"; d="scan'208";a="821899152" Received: from rmarepal-mobl3.amr.corp.intel.com (HELO [10.255.231.148]) ([10.255.231.148]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2023 16:07:39 -0700 Message-ID: <7c5ad793fe0195f7129156b67a043df18b46d732.camel@linux.intel.com> Subject: Re: [PATCH 4/6] sched/fair: Skip prefer sibling move between SMT group and non-SMT group From: Tim Chen To: Peter Zijlstra Cc: Juri Lelli , Vincent Guittot , Ricardo Neri , "Ravi V . Shankar" , Ben Segall , Daniel Bristot de Oliveira , Dietmar Eggemann , Len Brown , Mel Gorman , "Rafael J . Wysocki" , Srinivas Pandruvada , Steven Rostedt , Valentin Schneider , Ionela Voinescu , x86@kernel.org, linux-kernel@vger.kernel.org, Shrikanth Hegde , Srikar Dronamraju , naveen.n.rao@linux.vnet.ibm.com, Yicong Yang , Barry Song , Ricardo Neri Date: Fri, 05 May 2023 16:07:39 -0700 In-Reply-To: <20230505132211.GQ83892@hirez.programming.kicks-ass.net> References: <20230505132211.GQ83892@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4 (3.44.4-2.fc36) MIME-Version: 1.0 X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2023-05-05 at 15:22 +0200, Peter Zijlstra wrote: > On Thu, May 04, 2023 at 09:09:54AM -0700, Tim Chen wrote: > > From: Tim C Chen > >=20 > > Do not try to move tasks between non SMT sched group and SMT sched > > group for "prefer sibling" load balance. > > Let asym_active_balance_busiest() handle that case properly. > > Otherwise we could get task bouncing back and forth between > > the SMT sched group and non SMT sched group. > >=20 > > Reviewed-by: Ricardo Neri > > Signed-off-by: Tim Chen > > --- > > kernel/sched/fair.c | 4 ++++ > > 1 file changed, 4 insertions(+) > >=20 > > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > > index 8a325db34b02..58ef7d529731 100644 > > --- a/kernel/sched/fair.c > > +++ b/kernel/sched/fair.c > > @@ -10411,8 +10411,12 @@ static struct sched_group *find_busiest_group(= struct lb_env *env) > > /* > > * Try to move all excess tasks to a sibling domain of the busiest > > * group's child domain. > > + * > > + * Do not try to move between non smt sched group and smt sched > > + * group. Let asym active balance properly handle that case. > > */ > > if (sds.prefer_sibling && local->group_type =3D=3D group_has_spare && > > + !asymmetric_groups(sds.busiest, sds.local) && > > busiest->sum_nr_running > local->sum_nr_running + 1) > > goto force_balance; >=20 > This seems to have the hidden assumption that a !SMT core is somehow > 'less' that an SMT code. Should this not also look at > sched_asym_prefer() to establush this is so? >=20 > I mean, imagine I have a regular system and just offline one smt sibling > for giggles. I don't quite follow your point as asymmetric_groups() returns false even one smt sibling is offlined. Even say sds.busiest has 1 SMT and sds.local has 2 SMT, both sched groups s= till have SD_SHARE_CPUCAPACITY flag turned on. So asymmetric_groups() return false and the load balancing logic is not changed for regular non-hybrid sy= stem. I may be missing something. Tim