linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20230929170026.2520216-1-yajun.deng@linux.dev> (raw)

__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



             reply	other threads:[~2023-09-29 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 17:00 Yajun Deng [this message]
2023-09-29 17:00 ` [PATCH v5 1/2] mm: allow optional initialization of page count and PG_reserved flag Yajun Deng
2023-09-29 17:00 ` [PATCH v5 2/2] mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY Yajun Deng

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=20230929170026.2520216-1-yajun.deng@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --cc=rppt@kernel.org \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).