Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1287022ybi; Thu, 30 May 2019 14:58:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqxcdGNAUvcwcBa1rSEpXRf7+/krzL2D8/HOuozpavaGv9NdKw/W8ZK3Hq9/OmzQ4RV+ewNi X-Received: by 2002:a17:902:8ec3:: with SMTP id x3mr5524184plo.340.1559253522609; Thu, 30 May 2019 14:58:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559253522; cv=none; d=google.com; s=arc-20160816; b=Nh3G3N+YZ73MRYgCyCC/l+Y/7ZfA5/SM72XecsZeM/bHknPg9kzdRLIhj7POqV8u9g JY4F/OJF5++FnMNF9ob6p7g91LmT4+ciVzDw2XHNHsVb93isw3vZjhotGlPlv3MgCQiP hGtbg7Xi2N49CHxbU9xRVrqy1aEePKP750ZmmkH8OVTQlLj9NyFGpcluPTTZAHe0dKRs 2rtYe6/6GZT3gFmPvshsu/ZiphFITvPWVyW39vLHVb+jnvdj18JLZs4ePsEqxx7pwQl+ wtGqQG56nlC5GySJ9ZfeGgI3c02Wo1BXZXQSDpDtZkZZ/zfHX7PGoysnKhqg7cjT5xqa 7Xvg== 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:dkim-signature; bh=cMVlGTvXkUveUITBldNsm2wqtZ0vfwdSAKndguUBaOQ=; b=lXc4L8wo4BawCJ1eRvhoHHuO64vf22BLPEzmw5i/xPKI65jt2nDZFC17gp2EINpDZX K28KHqw56h/7s6T8iqqlO/AObFqruDExyMOzpxrklI7hSYrLifDipTVwYAqrbw8/uUeZ oXjGTmuAFNAOXRtYWIVPSNdOjlZtcpH+BkvNOPly8Jz1gUqrp8/vRqHiqzmXRx3e/Z+V igV5X7RwPkFGVhA8qXHcV1tAqbcIWImSGs2efXTNULEl6yQtaz4jVKCUgbjxuSl40Z5J HXeBF3OmOTUvnnLS9K3FABc0hHUO2X0YuiCxKoHW1BwB4EP/BVfR/1Z6ViY9CgaiS82I Naeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@armlinux.org.uk header.s=pandora-2019 header.b=DLH2JYbe; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=armlinux.org.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t1si3998622pgl.47.2019.05.30.14.58.27; Thu, 30 May 2019 14:58:42 -0700 (PDT) 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; dkim=fail (test mode) header.i=@armlinux.org.uk header.s=pandora-2019 header.b=DLH2JYbe; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=armlinux.org.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727110AbfE3VzM (ORCPT + 99 others); Thu, 30 May 2019 17:55:12 -0400 Received: from pandora.armlinux.org.uk ([78.32.30.218]:49572 "EHLO pandora.armlinux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726986AbfE3VzK (ORCPT ); Thu, 30 May 2019 17:55:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=cMVlGTvXkUveUITBldNsm2wqtZ0vfwdSAKndguUBaOQ=; b=DLH2JYbeHwq/YpEbWMtT0JGBL spO2pEc/2hmPltlibpNfKJ2Ih/2Rm4G0phN5i2XSKks3aWtbDZz/GjR3JOGCj0DN/EFFNJYoQcgdY KCaXkwyYwGjN4/dPWIvnF995pitZOxwUX3cRQdPGcd08tJMbDelcgzPTaceo+3xiEu6bQ9l0KxDmW A6ERMXUYjHd+RHWZrpMMqsX0zPrTCj1eb0FZ12RnJMUJ3c1CbH3/iBVkW/k/nJ87VxzdpYmPFA/Bj w8HefDp2VNcdyksBGBu0eg9AnsJHYltB0rlhwyOs9x/BKnj7EROswpX3bRDMtwawd5XTsxhzCT215 893fQ6/Cw==; Received: from shell.armlinux.org.uk ([2001:4d48:ad52:3201:5054:ff:fe00:4ec]:56076) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1hWSpD-0005E4-3f; Thu, 30 May 2019 22:43:03 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.89) (envelope-from ) id 1hWSp5-0005jk-2U; Thu, 30 May 2019 22:42:55 +0100 Date: Thu, 30 May 2019 22:42:54 +0100 From: Russell King - ARM Linux admin To: Morten Rasmussen Cc: "Andrew F. Davis" , Atish Patra , linux-kernel@vger.kernel.org, Sudeep Holla , Rob Herring , Albert Ou , Anup Patel , Catalin Marinas , "David S. Miller" , devicetree@vger.kernel.org, Greg Kroah-Hartman , Ingo Molnar , Jeremy Linton , Linus Walleij , linux-riscv@lists.infradead.org, Mark Rutland , Mauro Carvalho Chehab , Otto Sabart , Palmer Dabbelt , Paul Walmsley , "Peter Zijlstra (Intel)" , "Rafael J. Wysocki" , Rob Herring , Thomas Gleixner , Will Deacon , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v6 1/7] Documentation: DT: arm: add support for sockets defining package boundaries Message-ID: <20190530214254.tuxsnyv52a2fyhck@shell.armlinux.org.uk> References: <20190529211340.17087-1-atish.patra@wdc.com> <20190529211340.17087-2-atish.patra@wdc.com> <49f41e62-5354-a674-d95f-5f63851a0ca6@ti.com> <20190530115103.GA10919@e105550-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190530115103.GA10919@e105550-lin.cambridge.arm.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 30, 2019 at 12:51:03PM +0100, Morten Rasmussen wrote: > On Wed, May 29, 2019 at 07:39:17PM -0400, Andrew F. Davis wrote: > > On 5/29/19 5:13 PM, Atish Patra wrote: > > >From: Sudeep Holla > > > > > >The current ARM DT topology description provides the operating system > > >with a topological view of the system that is based on leaf nodes > > >representing either cores or threads (in an SMT system) and a > > >hierarchical set of cluster nodes that creates a hierarchical topology > > >view of how those cores and threads are grouped. > > > > > >However this hierarchical representation of clusters does not allow to > > >describe what topology level actually represents the physical package or > > >the socket boundary, which is a key piece of information to be used by > > >an operating system to optimize resource allocation and scheduling. > > > > > > > Are physical package descriptions really needed? What does "socket" imply > > that a higher layer "cluster" node grouping does not? It doesn't imply a > > different NUMA distance and the definition of "socket" is already not well > > defined, is a dual chiplet processor not just a fancy dual "socket" or are > > dual "sockets" on a server board "slotket" card, will we need new names for > > those too.. > > Socket (or package) just implies what you suggest, a grouping of CPUs > based on the physical socket (or package). Some resources might be > associated with packages and more importantly socket information is > exposed to user-space. At the moment clusters are being exposed to > user-space as sockets which is less than ideal for some topologies. Please point out a 32-bit ARM system that has multiple "socket"s. As far as I'm aware, all 32-bit systems do not have socketed CPUs (modern ARM CPUs are part of a larger SoC), and the CPUs are always in one package. Even the test systems I've seen do not have socketed CPUs. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up