Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Muchun Song <songmuchun@bytedance.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Oscar Salvador <osalvador@suse.de>,
	Mike Rapoport <rppt@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
	David Laight <david.laight.linux@gmail.com>,
	"Liam R . Howlett" <liam@infradead.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Qi Zheng <qi.zheng@linux.dev>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 09/17] mm/sparse: initialize memory sections earlier
Date: Wed, 9 Sep 2026 20:58:08 +0800	[thread overview]
Message-ID: <7A0F5F1F-F724-478A-A34A-E9F9771E2EB7@linux.dev> (raw)
In-Reply-To: <e6335c78-a20a-4024-8980-097a922eb257@kernel.org>



> On Sep 9, 2026, at 20:48, David Hildenbrand (Arm) <david@kernel.org> wrote:
> 
> 
>> 
>>> 
>>> I have patches to get rid of __section_mark_present() and just set them all to
>>> SECTION_IS_EARLY|SECTION_IS_ONLINE such that we can just iterate early sections
>>> and get rid of that PRESENT monstrosity.
>>> 
>>> Apart from that LGTM, even though I don't particularly enjoy splitting us now
>>> having two init entry points
>>> 
>>> sparse_init
>> 
>> Maybe this one should be sparse_memmap_init? If yes, it could be another separate
>> cleanup patch.
> 
> It does way more than that. In my patches I factor some of sparse_init out and
> call it sparse_metadata_init() -- memmap and usemap.

OK, I'll leave this part untouched since you've already done the perfect
renaming.

Thanks.

> 
> -- 
> Cheers,
> 
> David



  reply	other threads:[~2026-09-09 12:58 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  8:45 [PATCH v5 00/17] mm: Introduce section-based vmemmap optimization for HugeTLB Muchun Song
2026-08-25  8:45 ` [PATCH v5 01/17] mm/sparse: relax struct mem_section size constraints Muchun Song
2026-09-09  9:33   ` David Hildenbrand (Arm)
2026-08-25  8:45 ` [PATCH v5 02/17] mm/sparse-vmemmap: rename HVO order macros Muchun Song
2026-08-25 10:05   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 03/17] mm/mm_init: skip initializing shared vmemmap tail pages Muchun Song
2026-08-25  9:30   ` Mike Rapoport
2026-08-25 10:15   ` Qi Zheng
2026-09-09  9:36   ` David Hildenbrand (Arm)
2026-09-09 11:30     ` Muchun Song
2026-08-25  8:45 ` [PATCH v5 04/17] mm/sparse-vmemmap: initialize shared tail vmemmap pages on allocation Muchun Song
2026-08-25  9:30   ` Mike Rapoport
2026-08-25 10:40   ` Qi Zheng
2026-09-09  9:39   ` David Hildenbrand (Arm)
2026-09-09 12:49     ` Muchun Song
2026-08-25  8:45 ` [PATCH v5 05/17] mm/sparse-vmemmap: support section-based vmemmap accounting Muchun Song
2026-08-25 10:47   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 06/17] mm/mm_init: factor out pfn_to_zone() Muchun Song
2026-08-25 10:51   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 07/17] mm/sparse-vmemmap: move helpers ahead of future callers Muchun Song
2026-08-25 10:54   ` Qi Zheng
2026-08-25  8:45 ` [PATCH v5 08/17] mm/sparse-vmemmap: support section-based vmemmap optimization Muchun Song
2026-08-25  9:30   ` Mike Rapoport
2026-08-25 12:38   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 09/17] mm/sparse: initialize memory sections earlier Muchun Song
2026-08-25 12:49   ` Qi Zheng
2026-09-09  9:56   ` David Hildenbrand (Arm)
2026-09-09 12:29     ` Muchun Song
2026-09-09 12:48       ` David Hildenbrand (Arm)
2026-09-09 12:58         ` Muchun Song [this message]
2026-08-25  8:46 ` [PATCH v5 10/17] mm/hugetlb: switch HugeTLB to section-based vmemmap optimization Muchun Song
2026-08-25 13:12   ` Qi Zheng
2026-08-26  2:38     ` Muchun Song
2026-08-26  3:24       ` Qi Zheng
2026-09-09  9:58   ` David Hildenbrand (Arm)
2026-09-09 13:08     ` Muchun Song
2026-09-09 13:39       ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 11/17] mm/sparse-vmemmap: remove SPARSEMEM_VMEMMAP_PREINIT support Muchun Song
2026-08-25 13:16   ` Qi Zheng
2026-09-09  9:59   ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 12/17] mm/sparse: inline usemap allocation into sparse_init_nid() Muchun Song
2026-09-09 10:01   ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 13/17] mm/sparse: remove section_map_size() Muchun Song
2026-09-09 10:02   ` David Hildenbrand (Arm)
2026-08-25  8:46 ` [PATCH v5 14/17] mm/hugetlb: remove HUGE_BOOTMEM_HVO Muchun Song
2026-08-25 13:28   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 15/17] mm/hugetlb: remove HUGE_BOOTMEM_CMA Muchun Song
2026-08-25 13:42   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 16/17] mm/hugetlb: localize struct huge_bootmem_page Muchun Song
2026-08-25 13:38   ` Qi Zheng
2026-08-25  8:46 ` [PATCH v5 17/17] mm/hugetlb: localize HUGE_BOOTMEM_ZONES_VALID Muchun Song
2026-08-25 13:40   ` Qi Zheng
2026-08-28  4:20 ` [PATCH v5 00/17] mm: Introduce section-based vmemmap optimization for HugeTLB Andrew Morton
2026-09-09  9:31 ` David Hildenbrand (Arm)

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=7A0F5F1F-F724-478A-A34A-E9F9771E2EB7@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david.laight.linux@gmail.com \
    --cc=david@kernel.org \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=osalvador@suse.de \
    --cc=qi.zheng@linux.dev \
    --cc=rppt@kernel.org \
    --cc=songmuchun@bytedance.com \
    --cc=surenb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox