From: David Laight <david.laight.linux@gmail.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@kernel.org>,
linux-mm@kvack.org, Mike Rapoport <rppt@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, muchun.song@linux.dev
Subject: Re: [PATCH 01/17] mm/sparse: drop power-of-2 size requirement for struct mem_section
Date: Wed, 15 Jul 2026 10:34:45 +0100 [thread overview]
Message-ID: <20260715103445.31b2f727@pumpkin> (raw)
In-Reply-To: <20260702093821.2740183-2-songmuchun@bytedance.com>
On Thu, 2 Jul 2026 17:38:05 +0800
Muchun Song <songmuchun@bytedance.com> wrote:
> struct mem_section is currently forced to a power-of-2 size so the
> section-to-root lookup can use a mask instead of a modulo.
>
> That requirement adds configuration-dependent padding, especially with
> CONFIG_PAGE_EXTENSION, just to preserve the lookup scheme.
>
> Drop the constraint and use a plain modulo for the lookup instead. The
> divisor is constant, so the generated code remains cheap while avoiding
> the extra padding. It also removes an unnecessary layout constraint
> from the type.
This has a side effect of changing the size of the 'section' from
PAGE_SIZE to something 'a bit smaller' when CONFIG_PAGE_EXTENSION
is defined.
I don't think it actually matters, the allocation is done by:
static noinline struct mem_section __ref *sparse_index_alloc(int nid)
{
struct mem_section *section = NULL;
unsigned long array_size = SECTIONS_PER_ROOT *
sizeof(struct mem_section);
if (slab_is_available()) {
section = kzalloc_node(array_size, GFP_KERNEL, nid);
} else {
section = memblock_alloc_node(array_size, SMP_CACHE_BYTES,
nid);
so the size might get rounded up to PAGE_SIZE anyway.
I also suspect that '% 24u' might be enough slower than '% 32u' to
generate a measurable performance drop.
(It doesn't matter whether you do '& 31' or '% 32u'.)
David
next prev parent reply other threads:[~2026-07-15 9:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:38 [PATCH 00/17] mm: Introduce section-based vmemmap optimization for HugeTLB Muchun Song
2026-07-02 9:38 ` [PATCH 01/17] mm/sparse: drop power-of-2 size requirement for struct mem_section Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-15 9:34 ` David Laight [this message]
2026-07-15 13:15 ` Muchun Song
2026-07-02 9:38 ` [PATCH 02/17] mm/sparse-vmemmap: track compound page order in " Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-15 6:42 ` Muchun Song
2026-07-15 9:45 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 03/17] mm/sparse-vmemmap: introduce folio-oriented vmemmap optimization macros Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 04/17] mm/mm_init: skip initializing shared vmemmap tail pages Muchun Song
2026-07-09 10:45 ` Mike Rapoport
2026-07-09 12:31 ` Muchun Song
2026-07-09 13:05 ` Mike Rapoport
2026-07-09 13:23 ` Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-15 9:11 ` Muchun Song
2026-07-15 9:47 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 05/17] mm/sparse-vmemmap: initialize shared tail vmemmap pages on allocation Muchun Song
2026-07-02 9:38 ` [PATCH 06/17] mm/sparse-vmemmap: support section-based vmemmap accounting Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 07/17] mm/sparse-vmemmap: support section-based vmemmap optimization Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 08/17] mm/sparse: mark memory sections present earlier Muchun Song
2026-07-09 10:54 ` Mike Rapoport
2026-07-09 12:35 ` Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 09/17] mm/hugetlb: switch HugeTLB to section-based vmemmap optimization Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 10/17] mm/mm_init: factor out pfn_to_zone() Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 11/17] mm/sparse-vmemmap: remove SPARSEMEM_VMEMMAP_PREINIT support Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 12/17] mm/sparse: inline usemap allocation into sparse_init_nid() Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 13/17] mm/sparse: remove section_map_size() Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 14/17] mm/hugetlb: remove HUGE_BOOTMEM_HVO Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 15/17] mm/hugetlb: remove HUGE_BOOTMEM_CMA Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 16/17] mm/hugetlb: localize struct huge_bootmem_page Muchun Song
2026-07-15 5:08 ` Mike Rapoport
2026-07-02 9:38 ` [PATCH 17/17] mm/hugetlb: localize HUGE_BOOTMEM_ZONES_VALID Muchun Song
2026-07-15 5:08 ` Mike Rapoport
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=20260715103445.31b2f727@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.