All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>
Cc: Brendan Jackman <brendan.jackman@linux.dev>,
	Johannes Weiner <hannes@cmpxchg.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
	Suren Baghdasaryan <surenb@google.com>, Zi Yan <ziy@nvidia.com>
Subject: [PATCH v2 0/2] mm/page_ext: remove pgdat_page_ext_init()
Date: Wed,  5 Aug 2026 00:11:40 +0900	[thread overview]
Message-ID: <20260804151145.3419768-1-ekffu200098@gmail.com> (raw)

Hello,

pgdat_page_ext_init() has no effect on FLATMEM. The pgdat is always
the zero-initialized contig_page_data, because no architecture
supports FLATMEM + NUMA.

That constraint is only implicit in the arch Kconfig files. So patch 1
makes it explicit in mm/Kconfig, and patch 2 removes pgdat_page_ext_init().

No functional change.

---
Changes from v1 [1]
- Add patch 1 to make FLATMEM depend on !NUMA

[1] https://lore.kernel.org/all/20260803134822.2568766-1-ekffu200098@gmail.com/ 
---

Sang-Heon Jeon (2):
  mm/Kconfig: make FLATMEM depend on !NUMA
  mm/page_ext: remove pgdat_page_ext_init()

 include/linux/page_ext.h | 5 -----
 mm/Kconfig               | 2 ++
 mm/mm_init.c             | 1 -
 mm/page_ext.c            | 9 ---------
 4 files changed, 2 insertions(+), 15 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-08-04 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 15:11 Sang-Heon Jeon [this message]
2026-08-04 15:11 ` [PATCH v2 1/2] mm/Kconfig: make FLATMEM depend on !NUMA Sang-Heon Jeon
2026-08-04 15:56   ` Zi Yan
2026-08-05  9:46   ` Mike Rapoport
2026-08-05 10:05   ` David Hildenbrand (Arm)
2026-08-04 15:11 ` [PATCH v2 2/2] mm/page_ext: remove pgdat_page_ext_init() Sang-Heon Jeon
2026-08-04 15:57   ` Zi Yan
2026-08-05 10:05   ` 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=20260804151145.3419768-1-ekffu200098@gmail.com \
    --to=ekffu200098@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brendan.jackman@linux.dev \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.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=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=ziy@nvidia.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 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.