linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, Valentin.Schneider@arm.com,
	Anshuman.Khandual@arm.com, patches@amperecomputing.com
Subject: Re: [PATCH v3] arm64: NUMA: Kconfig: Increase NODES_SHIFT to 4
Date: Tue,  3 Nov 2020 14:54:52 +0000	[thread overview]
Message-ID: <160439588576.1151017.825552867492752498.b4-ty@kernel.org> (raw)
In-Reply-To: <20201030173050.1182876-1-vanshikonda@os.amperecomputing.com>

On Fri, 30 Oct 2020 10:30:50 -0700, Vanshidhar Konda wrote:
> The current arm64 default config limits max NUMA nodes available on
> system to 4 (NODES_SHIFT = 2). Today's arm64 systems can reach or
> exceed 16 NUMA nodes. To accomodate current hardware and to fit
> NODES_SHIFT within page flags on arm64, increase NODES_SHIFT to 4.
> 
> Discussion on v1 of the patch:
> https://lore.kernel.org/linux-arm-kernel/20201020173409.1266576-1-vanshikonda@os.amperecomputing.com/
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64: NUMA: Kconfig: Increase NODES_SHIFT to 4
      https://git.kernel.org/arm64/c/2a13c13b39a8

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      reply	other threads:[~2020-11-03 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 17:30 [PATCH v3] arm64: NUMA: Kconfig: Increase NODES_SHIFT to 4 Vanshidhar Konda
2020-11-03 14:54 ` Will Deacon [this message]

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=160439588576.1151017.825552867492752498.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=Anshuman.Khandual@arm.com \
    --cc=Valentin.Schneider@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@amperecomputing.com \
    --cc=vanshikonda@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;
as well as URLs for NNTP newsgroup(s).