Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3942589ybl; Mon, 13 Jan 2020 05:24:11 -0800 (PST) X-Google-Smtp-Source: APXvYqyKDupGWaHbnascM0CeREh6XIpkiJT72meujU95BKzQPrX2gjR4cX3XM6Sn6N/gaHqa3ByL X-Received: by 2002:aca:398b:: with SMTP id g133mr12100335oia.11.1578921851590; Mon, 13 Jan 2020 05:24:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578921851; cv=none; d=google.com; s=arc-20160816; b=d/2Dn00tnJ9DhkAHcCns0Odq3daPDFacQ1oEB6btHDZbu3CNqMBRDD1SklzLxBWL8Y go+RArBlrEBUTXsMoCHC9OKnRHhDLA9cCUaelGnp1xVEZ+WX6+hgEBNP1SfN9M/XNnRY Cs9MVyogY7yd/e1ILK+jh6OBDaHRUXQoRDBw+C7b9C2wsnoAxCEci7CPdLj74j/SVQ32 LrD7TZXIWFeTCsyREEHhNIl2L7ys5N2gjayLj5JkI0harTpNzhWbLskhW0wGZbxJApEB aJUowaZavfnHhiS3JPYKQeNHW7AJ7K9LptP2ZwRdfeMw0NTwBj65vFzsF0V3PyHfMQJQ MHlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=QIbuqebFPekGcjFISvYTNWY4WDQDOxz6izqWwoavk3I=; b=SVVVjPtIcWeQrBMwuebwP4Mmmh8CZmrmhq83tgJC+ALeUHvpEYlZEnKJjeEznUxXKH DgO6+HyGvBt6/JoI2q4E9tMvK2zLuk3Ov2fj/zKriw5eeB4xC9G3A3/09awlro/UKmnC YKrQSNtMIemEB2Rv8zVBVjrib4XEa7KI3nVO4RDpDsNEKZHLEdoL5W6kJJBL2u5Bn2Ot mioWqCGqiPG1rBudH1XbWvafDnoXCPT0ximLIzFIjCXhuBkz5KA+qmJ8M/JAN/HTFfb8 Z5mzCKkfoMLIBV/xgn5a10+jUYQvVFiNkW08RE+HgcT98ARCNFMEQ7+fklXv6bvRA7j6 kp8A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i124si5946391oif.214.2020.01.13.05.23.58; Mon, 13 Jan 2020 05:24:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728835AbgAMNWV (ORCPT + 99 others); Mon, 13 Jan 2020 08:22:21 -0500 Received: from foss.arm.com ([217.140.110.172]:39426 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728646AbgAMNWS (ORCPT ); Mon, 13 Jan 2020 08:22:18 -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 979E713D5; Mon, 13 Jan 2020 05:22:17 -0800 (PST) Received: from e105550-lin.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 96D1E3F68E; Mon, 13 Jan 2020 05:22:16 -0800 (PST) Date: Mon, 13 Jan 2020 13:22:14 +0000 From: Morten Rasmussen To: Valentin Schneider Cc: "Zengtao (B)" , Sudeep Holla , Linuxarm , Greg Kroah-Hartman , "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] cpu-topology: warn if NUMA configurations conflicts with lower layer Message-ID: <20200113132214.GD10914@e105550-lin.cambridge.arm.com> References: <1577088979-8545-1-git-send-email-prime.zeng@hisilicon.com> <20191231164051.GA4864@bogus> <678F3D1BB717D949B966B68EAEB446ED340AE1D3@dggemm526-mbx.china.huawei.com> <20200102112955.GC4864@bogus> <678F3D1BB717D949B966B68EAEB446ED340AEB67@dggemm526-mbx.china.huawei.com> <20200109105228.GB10914@e105550-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 12, 2020 at 01:22:02PM +0000, Valentin Schneider wrote: > On 09/01/2020 10:52, Morten Rasmussen wrote: > >> AFAIA what matters here is memory controllers, less so LLCs. Cores within > >> a single die could have private LLCs and separate memory controllers, or > >> shared LLC and separate memory controllers. > > > > Don't confuse cache boundaries, packages and nodes :-) > > > > core_siblings are cpus in the same package and doesn't say anything > > about cache boundaries. It is not given that there is sched_domain that > > matches the core_sibling span. > > > > The MC sched_domain is supposed to match the LLC span which might > > different for core_siblings. So the about example should be valid for a > > NUMA-in-package system with one package containing two nodes. > > > > Right, the point I was trying to make is that node boundaries can be pretty > much anything, so nodes can span over LLCs, or LLCs can span over nodes, > which is why we need checks such as the one in arch_topology() that lets us > build up a usable domain hierarchy (which cares about LLCs, at least at some > level). Indeed. The topology masks can't always be used as is to define the sched_domain hierarchy.