Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp4783018pxu; Wed, 21 Oct 2020 05:25:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyvHH5j/e1IGcaGyEISjNOrN1bto95dt+g4fmiN00/SUfTtj/+3foBtaLoYcQitkaJDh0VQ X-Received: by 2002:a50:ec88:: with SMTP id e8mr2719994edr.277.1603283115942; Wed, 21 Oct 2020 05:25:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603283115; cv=none; d=google.com; s=arc-20160816; b=adaoHx9kTDbkxYqNXXkHt5yK+BFpNJKMNFJVa4OEhY5LN1ojWqM9IeY7bf+oglhrHb Xy7U++xwtu8L4PTgontYZeHlLXNxok5nLv9uHGeZSTPEC1GdsY4qYMgxIOEw2M/XJKOs nVkpQ1DoV5u5DPOTXZjlD3gAlpU7i0GFE6lUVWUn5bA4y42im+H2f6Ze0P3I4dXkONbb vAI7swHcQBFMvyEAtyZ1ypRwjjb3UaSGUhjuP2IlcBTYaCcI+PaOCiafO1kahvdPvWe8 NVF+EMizQjyPOzDOVyr8IRbYrUgEyTAgegf1lAP3PbteykNJ1BpMmDe5ai6e6R7ZxQEW LlbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=6J+Q1s/2T+h9xgyDb+HmZ/8AO/4386S1zenrQxOtokE=; b=e5sTndc4Zc0OzfRC7MJaZwq9gyAn9Gki0Nm2C6Yk5QeT3njK9oQP67ZAxvFZWRyOMv EBN7cbjI3vTULkP3TyxhUTfB7aUqslgbF8SdqX4XHIDfv7Sb9cj2IvZIKYpFjcx5g71o Hp3UrNUkDwGqaTj/HoB98xU6bOU5wQqDonQLGKz7uyKZ+MSifKKa5IvKi/1jpSckQcFZ /dIscwSncDCuwtQGJ8jz2S+EEmuEHSEZQQdgSZIzhgEcM8heodk9+6rlP8GrxIAEe+QQ 4w5jhly3M8Q5TSy4FkUWrKFJd6fpFLJPkFyoMjxmMWwJCI7+9oRKiYffgznqhlCb5Z+w 6G/Q== 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=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ng3si1187240ejb.345.2020.10.21.05.24.52; Wed, 21 Oct 2020 05:25:15 -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=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404314AbgJUENx (ORCPT + 99 others); Wed, 21 Oct 2020 00:13:53 -0400 Received: from foss.arm.com ([217.140.110.172]:58556 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404232AbgJUENx (ORCPT ); Wed, 21 Oct 2020 00:13:53 -0400 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 66AE01FB; Tue, 20 Oct 2020 21:13:52 -0700 (PDT) Received: from [192.168.0.130] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 85AA13F66E; Tue, 20 Oct 2020 21:13:50 -0700 (PDT) Subject: Re: [PATCH] arm64: NUMA: Kconfig: Increase max number of nodes To: Valentin Schneider , Vanshidhar Konda Cc: linux-arm-kernel@lists.infradead.org, patches@amperecomputing.com, linux-kernel@vger.kernel.org References: <20201020173409.1266576-1-vanshikonda@os.amperecomputing.com> From: Anshuman Khandual Message-ID: <9e14c0d3-9204-fb32-31db-5b3f98639cba@arm.com> Date: Wed, 21 Oct 2020 09:43:21 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/20/2020 11:39 PM, Valentin Schneider wrote: > > Hi, > > Nit on the subject: this only increases the default, the max is still 2¹⁰. Agreed. > > On 20/10/20 18:34, Vanshidhar Konda wrote: >> The current arm64 max NUMA nodes default to 4. Today's arm64 systems can >> reach or exceed 16. Increase the number to 64 (matching x86_64). >> >> Signed-off-by: Vanshidhar Konda >> --- >> arch/arm64/Kconfig | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig >> index 893130ce1626..3e69d3c981be 100644 >> --- a/arch/arm64/Kconfig >> +++ b/arch/arm64/Kconfig >> @@ -980,7 +980,7 @@ config NUMA >> config NODES_SHIFT >> int "Maximum NUMA Nodes (as a power of 2)" >> range 1 10 >> - default "2" >> + default "6" > > This leads to more statically allocated memory for things like node to CPU > maps (see uses of MAX_NUMNODES), but that shouldn't be too much of an > issue. The smaller systems should not be required to waste those memory in a default case, unless there is a real and available larger system with those increased nodes. > > AIUI this also directly correlates to how many more page->flags bits are > required: are we sure the max 10 works on any aarch64 platform? I'm We will have to test that. Besides 256 (2 ^ 8) is the first threshold to be crossed here. > genuinely asking here, given that I'm mostly a stranger to the mm > world. The default should be something we're somewhat confident works > everywhere. Agreed. Do we really need to match X86 right now ? Do we really have systems that has 64 nodes ? We should not increase the default node value and then try to solve some new problems, when there might not be any system which could even use that. I would suggest increase NODES_SHIFT value upto as required by a real and available system. > >> depends on NEED_MULTIPLE_NODES >> help >> Specify the maximum number of NUMA Nodes available on the target >