From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8756EC433DB for ; Tue, 9 Feb 2021 11:49:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3B0E364E10 for ; Tue, 9 Feb 2021 11:49:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230134AbhBILs7 (ORCPT ); Tue, 9 Feb 2021 06:48:59 -0500 Received: from foss.arm.com ([217.140.110.172]:50294 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230148AbhBILqw (ORCPT ); Tue, 9 Feb 2021 06:46:52 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F0A63ED1; Tue, 9 Feb 2021 03:46:06 -0800 (PST) Received: from e113632-lin (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D59153F73B; Tue, 9 Feb 2021 03:46:04 -0800 (PST) From: Valentin Schneider To: Vincent Guittot , Barry Song Cc: Mel Gorman , Ingo Molnar , Peter Zijlstra , Dietmar Eggemann , Morten Rasmussen , linux-kernel , linuxarm@openeuler.org, "xuwei \(O\)" , "Liguozhu \(Kenneth\)" , tiantao6@hisilicon.com, wanghuiqiang@huawei.com, "Zengtao \(B\)" , Jonathan Cameron , Guodong Xu , Meelis Roos Subject: Re: [PATCH v3] sched/topology: fix the issue groups don't span domain->span for NUMA diameter > 2 In-Reply-To: References: <20210209082125.22176-1-song.bao.hua@hisilicon.com> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu) Date: Tue, 09 Feb 2021 11:46:02 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/02/21 10:46, Vincent Guittot wrote: > On Tue, 9 Feb 2021 at 09:27, Barry Song wrote: >> Real servers which suffer from this problem include Kunpeng920 and 8-node >> Sun Fire X4600-M2, at least. >> >> Here we move to use the *child* domain of the *child* domain of node2's >> domain2 as the new added sched_group. At the same, we re-use the lower >> level sgc directly. > > Have you evaluated the impact on the imbalance and next_update fields ? > sgc->next_update is safe since it's only touched by CPUs that have the group span as local group (which is never the case for CPUs where we do this "grandchildren" trick). I'm a bit less clear about sgc->imbalance. I think it can be set by remote CPUs, but it should only be cleared when running load_balance() by CPUs that have that group span as local group, as per: int *group_imbalance = &sd_parent->groups->sgc->imbalance;