archive mirror
 help / color / mirror / Atom feed
From: Sudarshan Rajagopalan <>
	Catalin Marinas <>,
	Will Deacon <>,
	Anshuman Khandual <>,
	David Hildenbrand <>
Cc: Sudarshan Rajagopalan <>
Subject: [PATCH 0/1] arm64/sparsemem: reduce SECTION_SIZE_BITS
Date: Wed, 20 Jan 2021 21:29:12 -0800	[thread overview]
Message-ID: <> (raw)

This patch is the follow-up from the discussions in the thread [1].
Reducing the section size has the merit of reducing wastage of reserved memory
for vmmemmap mappings for sections with large memory holes. Also with smaller 
section size gives more grunularity and agility for memory hot(un)plugging.

But there are also constraints in reducing SECTION_SIZE_BIT:

- Should accommodate highest order page for a given config
- Should not break PMD mapping in vmemmap for 4K pages
- Should not consume too many page->flags bits reducing space for other info

This patch uses the suggestions from Anshuman Khandual and David Hildenbrand
in thread [1] to set the least possible section size to 128MB for 4K and 16K
base page size configs for simplicity, and to 512MB for 64K base page size config.


Sudarshan Rajagopalan (1):
  arm64/sparsemem: reduce SECTION_SIZE_BITS

 arch/arm64/include/asm/sparsemem.h | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)

Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

             reply	other threads:[~2021-01-21  5:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21  5:29 Sudarshan Rajagopalan [this message]
2021-01-21  5:29 ` [PATCH 1/1] arm64/sparsemem: reduce SECTION_SIZE_BITS Sudarshan Rajagopalan
2021-01-21 10:08   ` Christoph Lameter
2021-01-21 15:54     ` Catalin Marinas
2021-01-21 13:36   ` Will Deacon
2021-01-22  2:58     ` Anshuman Khandual
2021-01-21 13:45   ` David Hildenbrand
2021-01-21 14:16   ` Mike Rapoport
2021-01-21 16:04     ` David Hildenbrand
2021-01-21 15:51   ` Catalin Marinas
2021-01-21 18:26 ` [PATCH 0/1] " Will Deacon
2021-01-29  0:17   ` Pavel Tatashin

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).