From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754004AbcIAG5P (ORCPT ); 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 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 Content-Type: text/plain 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 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(-) 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: -- 2.5.0 From mboxrd@z Thu Jan 1 00:00:00 1970 From: 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> References: <1472712907-12700-1-git-send-email-thunder.leizhen@huawei.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <1472712907-12700-1-git-send-email-thunder.leizhen@huawei.com> Sender: owner-linux-mm@kvack.org 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 List-Id: devicetree@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(-) 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: -- 2.5.0 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: thunder.leizhen@huawei.com (Zhen Lei) Date: Thu, 1 Sep 2016 14:55:06 +0800 Subject: [PATCH v8 15/16] Documentation: remove the constraint on the distances of node pairs In-Reply-To: <1472712907-12700-1-git-send-email-thunder.leizhen@huawei.com> References: <1472712907-12700-1-git-send-email-thunder.leizhen@huawei.com> Message-ID: <1472712907-12700-16-git-send-email-thunder.leizhen@huawei.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.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(-) 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: -- 2.5.0