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 v4 0/2] mm: Don't set and reset page count in MEMINIT_EARLY
Date: Thu, 28 Sep 2023 16:33:00 +0800 [thread overview]
Message-ID: <20230928083302.386202-1-yajun.deng@linux.dev> (raw)
__init_single_page would set page count and __free_pages_core would
reset 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 pass page count and reserved to __init_single_page.
It's in preparation for the 2nd patch, it didn't change anything.
The 2nd patch only set page count for the reserved region, not all
of the region.
Yajun Deng (2):
mm: pass page count and reserved to __init_single_page
mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY
mm/hugetlb.c | 2 +-
mm/internal.h | 8 +++++++-
mm/mm_init.c | 38 ++++++++++++++++++++++++--------------
mm/page_alloc.c | 20 ++++++++++++--------
4 files changed, 44 insertions(+), 24 deletions(-)
--
2.25.1
next reply other threads:[~2023-09-28 8:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 8:33 Yajun Deng [this message]
2023-09-28 8:33 ` [PATCH v4 1/2] mm: pass page count and reserved to __init_single_page Yajun Deng
2023-09-29 8:19 ` Mike Rapoport
2023-09-29 9:37 ` Yajun Deng
2023-09-28 8:33 ` [PATCH v4 2/2] mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY Yajun Deng
2023-09-29 8:30 ` Mike Rapoport
2023-09-29 9:50 ` Yajun Deng
2023-09-29 10:02 ` Mike Rapoport
2023-09-29 10:27 ` Yajun Deng
2023-10-01 18:59 ` Mike Rapoport
2023-10-02 7:03 ` Yajun Deng
2023-10-02 8:47 ` Mike Rapoport
2023-10-02 8:56 ` David Hildenbrand
2023-10-02 11:10 ` Mike Rapoport
2023-10-02 11:25 ` David Hildenbrand
2023-10-03 14:38 ` Yajun Deng
2023-10-05 5:06 ` Mike Rapoport
2023-10-05 14:04 ` Yajun Deng
2023-10-12 9:19 ` Mike Rapoport
2023-10-12 9:36 ` Yajun Deng
2023-10-02 8:30 ` David Hildenbrand
2023-10-08 8:57 ` Yajun Deng
2023-10-10 2:31 ` Yajun Deng
2023-10-12 9:23 ` David Hildenbrand
2023-10-12 9:53 ` Yajun Deng
2023-10-13 8:48 ` Mike Rapoport
2023-10-13 9:29 ` Yajun Deng
2023-10-16 6:33 ` Mike Rapoport
2023-10-16 8:10 ` Yajun Deng
2023-10-16 8:16 ` David Hildenbrand
2023-10-16 8:32 ` Yajun Deng
2023-10-16 8:36 ` David Hildenbrand
2023-10-16 10:17 ` Yajun Deng
2023-10-17 9:58 ` 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=20230928083302.386202-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