From patchwork Thu Sep 1 06:55:06 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Leizhen \(ThunderTown\)" X-Patchwork-Id: 75171 Delivered-To: patch@linaro.org Received: by 10.140.29.8 with SMTP id a8csp130361qga; Wed, 31 Aug 2016 23:57:26 -0700 (PDT) X-Received: by 10.98.89.23 with SMTP id n23mr24121740pfb.34.1472713041525; Wed, 31 Aug 2016 23:57:21 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c7si4065870pax.281.2016.08.31.23.57.20; Wed, 31 Aug 2016 23:57:21 -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; 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 S1754006AbcIAG5P (ORCPT + 27 others); Thu, 1 Sep 2016 02:57:15 -0400 Received: from szxga03-in.huawei.com ([119.145.14.66]:58405 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753757AbcIAG5H (ORCPT ); Thu, 1 Sep 2016 02:57:07 -0400 Received: from 172.24.1.60 (EHLO szxeml431-hub.china.huawei.com) ([172.24.1.60]) by szxrg03-dlp.huawei.com (MOS 4.4.3-GA FastPath queued) with ESMTP id CHE42847; Thu, 01 Sep 2016 14:56:51 +0800 (CST) Received: from localhost (10.177.23.164) by szxeml431-hub.china.huawei.com (10.82.67.208) with Microsoft SMTP Server id 14.3.235.1; Thu, 1 Sep 2016 14:56:18 +0800 From: Zhen Lei To: Catalin Marinas , Will Deacon , linux-arm-kernel , linux-kernel , Rob Herring , "Frank Rowand" , devicetree , Andrew Morton , linux-mm CC: Zefan Li , Xinwei Hu , "Tianhong Ding" , Hanjun Guo , Zhen Lei Subject: [PATCH v8 15/16] Documentation: remove the constraint on the distances of node pairs Date: Thu, 1 Sep 2016 14:55:06 +0800 Message-ID: <1472712907-12700-16-git-send-email-thunder.leizhen@huawei.com> X-Mailer: git-send-email 1.9.5.msysgit.1 In-Reply-To: <1472712907-12700-1-git-send-email-thunder.leizhen@huawei.com> References: <1472712907-12700-1-git-send-email-thunder.leizhen@huawei.com> MIME-Version: 1.0 X-Originating-IP: [10.177.23.164] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.57C7D134.004E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-05-26 15:14:31, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 91a67d36a51afad8c876f5568de2d045 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At present, the distances must equal in both direction for each node pairs. For example: the distance of node B->A must the same to A->B. But we really don't have to do this. Signed-off-by: Zhen Lei --- Documentation/devicetree/bindings/numa.txt | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) -- 2.5.0 diff --git a/Documentation/devicetree/bindings/numa.txt b/Documentation/devicetree/bindings/numa.txt index 21b3505..f7234cd 100644 --- a/Documentation/devicetree/bindings/numa.txt +++ b/Documentation/devicetree/bindings/numa.txt @@ -48,15 +48,19 @@ distance (memory latency) between all numa nodes. Note: 1. Each entry represents distance from first node to second node. - The distances are equal in either direction. 2. The distance from a node to self (local distance) is represented with value 10 and all internode distance should be represented with a value greater than 10. - 3. distance-matrix should have entries in lexicographical ascending + 3. For non-local node pairs: + 1) If both direction specified, keep no change. + 2) If only one direction specified, assign it to the other direction. + 3) If none of the two direction specified, both are assigned to + REMOTE_DISTANCE. + 4. distance-matrix should have entries in lexicographical ascending order of nodes. - 4. There must be only one device node distance-map which must + 5. There must be only one device node distance-map which must reside in the root node. - 5. If the distance-map node is not present, a default + 6. If the distance-map node is not present, a default distance-matrix is used. Example: