From: "Christoph Lameter (Ampere)" <cl@linux.com>
To: Eric Mackay <eric.mackay@oracle.com>
Cc: mark.rutland@arm.com, Jonathan.Cameron@huawei.com,
Matteo.Carlini@arm.com, Valentin.Schneider@arm.com,
akpm@linux-foundation.org, anshuman.khandual@arm.com,
catalin.marinas@arm.com, dave.kleikamp@oracle.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux@armlinux.org.uk, robin.murphy@arm.com,
vanshikonda@os.amperecomputing.com, yang@os.amperecomputing.com
Subject: Re: [PATCH] ARM64: Dynamically allocate cpumasks and increase supported CPUs to 512
Date: Wed, 17 Jan 2024 11:59:53 -0800 (PST) [thread overview]
Message-ID: <47461daf-3aa5-493f-7278-b0116ee2c724@linux.com> (raw)
In-Reply-To: <20240116210633.116278-1-eric.mackay@oracle.com>
On Tue, 16 Jan 2024, Eric Mackay wrote:
>
> It seems > 256 was chosen as the cutoff simply because it preserves existing behavior.
> The patch description seems to imply there was pushback from distro maintainers on just increasing
> the default NR_CPUS.
Yup that was it.
next prev parent reply other threads:[~2024-01-17 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 0:05 Christoph Lameter (Ampere)
2024-01-15 15:39 ` Russell King (Oracle)
2024-01-16 7:10 ` Kefeng Wang
2024-01-16 9:28 ` Russell King (Oracle)
2024-01-16 13:08 ` Mark Rutland
2024-01-16 21:06 ` Eric Mackay
2024-01-17 19:59 ` Christoph Lameter (Ampere) [this message]
2024-01-15 23:59 ` Eric Mackay
2024-01-16 11:24 ` Russell King (Oracle)
2024-01-16 21:06 ` Eric Mackay
2024-01-17 20:01 ` Christoph Lameter (Ampere)
2024-01-18 17:53 ` Eric Mackay
2024-01-23 23:55 ` [PATCH v2] " Christoph Lameter (Ampere)
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=47461daf-3aa5-493f-7278-b0116ee2c724@linux.com \
--to=cl@linux.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Matteo.Carlini@arm.com \
--cc=Valentin.Schneider@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dave.kleikamp@oracle.com \
--cc=eric.mackay@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=vanshikonda@os.amperecomputing.com \
--cc=yang@os.amperecomputing.com \
/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