Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1243977pxf; Fri, 19 Mar 2021 02:39:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwvpYoAWox+W9j0IefgoTBPJcJ3tb4pvHilhTcXya5as6jcRRrbcgxsSJJd3UtdezomLryE X-Received: by 2002:a17:906:379b:: with SMTP id n27mr3351932ejc.182.1616146753473; Fri, 19 Mar 2021 02:39:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616146753; cv=none; d=google.com; s=arc-20160816; b=jTgUOEVK9x3Mw9otz27B+4GgcCJqki7vsaJrSlWQ06heIS9HXxJ4Q31ydqsxgWzShT VfSeo8ZuyyMV/QCWmG0wy4137PdV9hcXTjSlOfDSWp+75zI5WgQBbVZvTgmoYcVzbqM1 LAOCnRkUhIp6pQEcrjhjHtdnFll87T4UUj5NfRGzmduP1sded7OeBn7NT8sW7Z5K76Nv 5iKwNCGT5R7UAxTGnWMGtzCljER5+OrqFVXlucFRpgNLoLzUqb7snN4lB2MIXNO7hCtI Q+5tvfmSWTLpcvueKDyWxVNAK/M9BCkVv+edRUirxuTQFo/alAVHv49xo5EbsIIOd2Tn 9yfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=2kWmrO9BMRtwJgQf+TU0mfUcwCtZW/We0S93teB6MFI=; b=laVorfOH3KoRwlGb+/BLNH71xzsp/dO99OZLi980IRVD+FIhCPJlkUXAwVTwe/qZ1L Aj0rC3EKK8liRrvnPvyuuuOFrxbYO+n1tSwy6TQ2pazoyQCO4ci7So6ATqhr0VpK81fe YF9Op7JN3Q3WszfhTnjvzIVZnISHTWdINeU6iKNSxSJPGQIQuaKeK9CF3O8/pr1Wn35a yxoJ65N/erclgNin+zgeJsi0vwLb9Un2Cpz1+S3VKvVrolKKaCecsBNH54dgBSY1klZ7 lAoptAvlFMboonHgVhDOr1k0Kh5jaMZLT8DDRvkEdugvBH+yXieh4XFHarFEjgKVakRS TrIw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s24si3517972edy.266.2021.03.19.02.38.50; Fri, 19 Mar 2021 02:39:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229618AbhCSJhy (ORCPT + 99 others); Fri, 19 Mar 2021 05:37:54 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:2715 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229564AbhCSJhl (ORCPT ); Fri, 19 Mar 2021 05:37:41 -0400 Received: from fraeml736-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F1zG14Flrz681ZH; Fri, 19 Mar 2021 17:32:57 +0800 (CST) Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by fraeml736-chm.china.huawei.com (10.206.15.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 19 Mar 2021 10:37:34 +0100 Received: from localhost (10.47.25.23) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 19 Mar 2021 09:37:33 +0000 Date: Fri, 19 Mar 2021 09:36:16 +0000 From: Jonathan Cameron To: "Song Bao Hua (Barry Song)" CC: Greg KH , "tim.c.chen@linux.intel.com" , "catalin.marinas@arm.com" , "will@kernel.org" , "rjw@rjwysocki.net" , "vincent.guittot@linaro.org" , "bp@alien8.de" , "tglx@linutronix.de" , "mingo@redhat.com" , "lenb@kernel.org" , "peterz@infradead.org" , "dietmar.eggemann@arm.com" , "rostedt@goodmis.org" , "bsegall@google.com" , "mgorman@suse.de" , "msys.mizuma@gmail.com" , "valentin.schneider@arm.com" , "juri.lelli@redhat.com" , "mark.rutland@arm.com" , "sudeep.holla@arm.com" , "aubrey.li@linux.intel.com" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "x86@kernel.org" , "xuwei (O)" , "Zengtao (B)" , "guodong.xu@linaro.org" , yangyicong , "Liguozhu (Kenneth)" , "linuxarm@openeuler.org" , "hpa@zytor.com" Subject: Re: [RFC PATCH v5 1/4] topology: Represent clusters of CPUs within a die Message-ID: <20210319093616.00001879@Huawei.com> In-Reply-To: References: <20210319041618.14316-1-song.bao.hua@hisilicon.com> <20210319041618.14316-2-song.bao.hua@hisilicon.com> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.47.25.23] X-ClientProxiedBy: lhreml730-chm.china.huawei.com (10.201.108.81) To lhreml710-chm.china.huawei.com (10.201.108.61) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 19 Mar 2021 06:57:08 +0000 "Song Bao Hua (Barry Song)" wrote: > > -----Original Message----- > > From: Greg KH [mailto:gregkh@linuxfoundation.org] > > Sent: Friday, March 19, 2021 7:35 PM > > To: Song Bao Hua (Barry Song) > > Cc: tim.c.chen@linux.intel.com; catalin.marinas@arm.com; will@kernel.org; > > rjw@rjwysocki.net; vincent.guittot@linaro.org; bp@alien8.de; > > tglx@linutronix.de; mingo@redhat.com; lenb@kernel.org; peterz@infradead.org; > > dietmar.eggemann@arm.com; rostedt@goodmis.org; bsegall@google.com; > > mgorman@suse.de; msys.mizuma@gmail.com; valentin.schneider@arm.com; Jonathan > > Cameron ; juri.lelli@redhat.com; > > mark.rutland@arm.com; sudeep.holla@arm.com; aubrey.li@linux.intel.com; > > linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; > > linux-acpi@vger.kernel.org; x86@kernel.org; xuwei (O) ; > > Zengtao (B) ; guodong.xu@linaro.org; yangyicong > > ; Liguozhu (Kenneth) ; > > linuxarm@openeuler.org; hpa@zytor.com > > Subject: Re: [RFC PATCH v5 1/4] topology: Represent clusters of CPUs within > > a die > > > > On Fri, Mar 19, 2021 at 05:16:15PM +1300, Barry Song wrote: > > > diff --git a/Documentation/admin-guide/cputopology.rst > > b/Documentation/admin-guide/cputopology.rst > > > index b90dafc..f9d3745 100644 > > > --- a/Documentation/admin-guide/cputopology.rst > > > +++ b/Documentation/admin-guide/cputopology.rst > > > @@ -24,6 +24,12 @@ core_id: > > > identifier (rather than the kernel's). The actual value is > > > architecture and platform dependent. > > > > > > +cluster_id: > > > + > > > + the Cluster ID of cpuX. Typically it is the hardware platform's > > > + identifier (rather than the kernel's). The actual value is > > > + architecture and platform dependent. > > > + > > > book_id: > > > > > > the book ID of cpuX. Typically it is the hardware platform's > > > @@ -56,6 +62,14 @@ package_cpus_list: > > > human-readable list of CPUs sharing the same physical_package_id. > > > (deprecated name: "core_siblings_list") > > > > > > +cluster_cpus: > > > + > > > + internal kernel map of CPUs within the same cluster. > > > + > > > +cluster_cpus_list: > > > + > > > + human-readable list of CPUs within the same cluster. > > > + > > > die_cpus: > > > > > > internal kernel map of CPUs within the same die. > > > > Why are these sysfs files in this file, and not in a Documentation/ABI/ > > file which can be correctly parsed and shown to userspace? > > Well. Those ABIs have been there for much a long time. It is like: > > [root@ceph1 topology]# ls > core_id core_siblings core_siblings_list physical_package_id thread_siblings thread_siblings_list > [root@ceph1 topology]# pwd > /sys/devices/system/cpu/cpu100/topology > [root@ceph1 topology]# cat core_siblings_list > 64-127 > [root@ceph1 topology]# > > > > > Any chance you can fix that up here as well? > > Yes. we will send a separate patch to address this, which won't > be in this patchset. This patchset will base on that one. > > > > > Also note that "list" is not something that goes in sysfs, sysfs is "one > > value per file", and a list is not "one value". How do you prevent > > overflowing the buffer of the sysfs file if you have a "list"? > > > > At a glance, the list is using "-" rather than a real list > [root@ceph1 topology]# cat core_siblings_list > 64-127 > > Anyway, I will take a look if it has any chance to overflow. It could in theory be alternate CPUs as comma separated list. So it's would get interesting around 500-1000 cpus (guessing). Hopefully no one has that crazy a cpu numbering scheme but it's possible (note that cluster is fine for this, but I guess it might eventually happen for core-siblings list (cpus within a package). Shouldn't crash or anything like that but might terminate early. On sysfs file conversion, that got mentioned earlier but I forgot to remind Barry about it when he took this patch into his series. Sorry about that! Jonathan > > > thanks, > > > > greg k-h > > Thanks > Barry >