From: Wei Yang <richard.weiyang@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/mm_init.c: don't initialize page->lru again
Date: Sat, 8 Jun 2024 00:35:35 +0000 [thread overview]
Message-ID: <20240608003535.cxrupjomwaxh7zpi@master> (raw)
In-Reply-To: <ZmK31YqzZUmOnDwb@kernel.org>
On Fri, Jun 07, 2024 at 10:33:41AM +0300, Mike Rapoport wrote:
>On Wed, Jun 05, 2024 at 10:14:36PM +0000, Wei Yang wrote:
>> After init_reserved_page(), we expect __init_single_page() has done its
>> work to the page, which already initialize page->lru properly.
>
>init_reserved_page only available with CONFIG_DEFERRED_STRUCT_PAGE_INIT
The common page initialize path is :
memmap_init
memmap_init_zone_range
memmap_init_range
defer_init
__init_single_page
If CONFIG_DEFERRED_STRUCT_PAGE_INIT set, we would skip initialization for pages
after first_init_pfn. So init_reserved_page would initialize page struct
before __SetPageReserved().
If CONFIG_DEFERRED_STRUCT_PAGE_INIT not set, page struct is already initialized.
Is my understanding correct?
>
>> We don't need to do it again.
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> ---
>> mm/mm_init.c | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/mm/mm_init.c b/mm/mm_init.c
>> index 14133a1cfc7b..30379b0e7729 100644
>> --- a/mm/mm_init.c
>> +++ b/mm/mm_init.c
>> @@ -759,9 +759,6 @@ void __meminit reserve_bootmem_region(phys_addr_t start,
>>
>> init_reserved_page(start_pfn, nid);
>>
>> - /* Avoid false-positive PageTail() */
>> - INIT_LIST_HEAD(&page->lru);
>> -
>> /*
>> * no need for atomic set_bit because the struct
>> * page is not visible yet so nobody should
>> --
>> 2.34.1
>>
>>
>
>--
>Sincerely yours,
>Mike.
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2024-06-08 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 22:14 Wei Yang
2024-06-07 7:33 ` Mike Rapoport
2024-06-08 0:35 ` Wei Yang [this message]
2024-06-08 7:56 ` Mike Rapoport
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=20240608003535.cxrupjomwaxh7zpi@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rppt@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