Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
From:   Yajun Deng <yajun.deng@linux.dev>
To:     akpm@linux-foundation.org, rppt@kernel.org
Cc:     mike.kravetz@oracle.com, muchun.song@linux.dev,
        willy@infradead.org, david@redhat.com, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, Yajun Deng <yajun.deng@linux.dev>
Subject: [PATCH v5 0/2] mm: Don't init and clear page count when MEMINIT_EARLY
Date:   Sat, 30 Sep 2023 01:00:24 +0800
Message-Id: <20230929170026.2520216-1-yajun.deng@linux.dev>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

__init_single_page would init page count and __free_pages_core would
clear it. A lot of pages don't need to do this when in MEMINIT_EARLY
context. It's unnecessary and time-consuming.

The 1st patch is allow optional initialization of page count and
PG_reserved flag. It's in preparation for the 2nd patch, it didn't
change anything.

The 2nd patch only init page count for the reserved region, not all
of the region when MEMINIT_EARLY.

Yajun Deng (2):
  mm: allow optional initialization of page count and PG_reserved flag
  mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY

 mm/hugetlb.c    |  2 +-
 mm/internal.h   |  8 +++++++-
 mm/mm_init.c    | 40 ++++++++++++++++++++++++++--------------
 mm/page_alloc.c | 20 ++++++++++++--------
 4 files changed, 46 insertions(+), 24 deletions(-)

-- 
2.25.1