mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yanteng Si <si.yanteng@linux.dev>
To: Huacai Chen <chenhuacai@loongson.cn>,
	Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, Xuefeng Li <lixuefeng@loongson.cn>,
	Guo Ren <guoren@kernel.org>, Xuerui Wang <kernel@xen0n.name>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] LoongArch: Increase max supported CPUs up to 2048
Date: Wed, 7 May 2025 18:07:33 +0800	[thread overview]
Message-ID: <728f6bff-d029-4ce5-a760-520fadee26ac@linux.dev> (raw)
In-Reply-To: <20250507073428.216090-1-chenhuacai@loongson.cn>

在 5/7/25 3:34 PM, Huacai Chen 写道:
> Increase max supported CPUs up to 2048, including:
> 1. Increase CSR.CPUID register's effective width;
> 2. Define MAX_CORE_PIC (a.k.a. max physical ID) to 2048;
> 3. Allow NR_CPUS (a.k.a. max logical ID) to be as large as 2048;
> 4. Introduce acpi_numa_x2apic_affinity_init() to handle ACPI SRAT
>     for CPUID >= 256.
> 
> Note: The reason of increasing to 2048 rather than 4096/8192 is because
>        the IPI hardware can only support 2048 as a maximum.
> 
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
>   arch/loongarch/Kconfig                 |  6 ++--
>   arch/loongarch/include/asm/acpi.h      |  2 +-
>   arch/loongarch/include/asm/loongarch.h |  4 +--
>   arch/loongarch/kernel/acpi.c           | 41 ++++++++++++++++++++++----
>   4 files changed, 41 insertions(+), 12 deletions(-)
> 
> diff --git a/arch/loongarch/Kconfig b/arch/loongarch/Kconfig
> index 38706186cf13..0c356de91bc4 100644
> --- a/arch/loongarch/Kconfig
> +++ b/arch/loongarch/Kconfig
> @@ -496,10 +496,10 @@ config HOTPLUG_CPU
>   	  Say N if you want to disable CPU hotplug.
>   

>   config NR_CPUS
> -	int "Maximum number of CPUs (2-256)"
> -	range 2 256
> +	int "Maximum number of CPUs (2-2048)"
> +	range 2 2048
> +	default "2048"
I'm curious. As a new architecture, why did you write
such a small value at the beginning?


Reviewed-by: Yanteng Si <si.yanteng@linux.dev>

Thanks,
Yanteng

  reply	other threads:[~2025-05-07 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  7:34 Huacai Chen
2025-05-07 10:07 ` Yanteng Si [this message]
2025-05-07 10:20   ` Huacai Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=728f6bff-d029-4ce5-a760-520fadee26ac@linux.dev \
    --to=si.yanteng@linux.dev \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=guoren@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=loongarch@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®