From: Muchun Song <muchun.song@linux.dev>
To: Usama Arif <usama.arif@bytedance.com>
Cc: Linux-MM <linux-mm@kvack.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Muchun Song <songmuchun@bytedance.com>,
fam.zheng@bytedance.com, liangma@liangbit.com,
punit.agrawal@bytedance.com
Subject: Re: [v4 3/4] memblock: introduce MEMBLOCK_RSRV_NOINIT flag
Date: Wed, 6 Sep 2023 19:35:52 +0800 [thread overview]
Message-ID: <05DA93DB-84E5-48C3-AA16-F1F2525C8CC8@linux.dev> (raw)
In-Reply-To: <20230906112605.2286994-4-usama.arif@bytedance.com>
> On Sep 6, 2023, at 19:26, Usama Arif <usama.arif@bytedance.com> wrote:
>
> For reserved memory regions marked with this flag,
> reserve_bootmem_region is not called during memmap_init_reserved_pages.
> This can be used to avoid struct page initialization for
> regions which won't need them, for e.g. hugepages with
> HVO enabled.
>
> Signed-off-by: Usama Arif <usama.arif@bytedance.com>
Acked-by: Muchun Song <songmuchun@bytedance.com>
next prev parent reply other threads:[~2023-09-06 11:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 11:26 [v4 0/4] mm: hugetlb: Skip initialization of gigantic tail struct pages if freed by HVO Usama Arif
2023-09-06 11:26 ` [v4 1/4] mm: hugetlb_vmemmap: Use nid of the head page to reallocate it Usama Arif
2023-09-06 11:26 ` [v4 2/4] memblock: pass memblock_type to memblock_setclr_flag Usama Arif
2023-09-06 11:26 ` [v4 3/4] memblock: introduce MEMBLOCK_RSRV_NOINIT flag Usama Arif
2023-09-06 11:35 ` Muchun Song [this message]
2023-09-06 12:01 ` Mike Rapoport
2023-09-06 11:26 ` [v4 4/4] mm: hugetlb: Skip initialization of gigantic tail struct pages if freed by HVO Usama Arif
2023-09-06 18:10 ` Mike Kravetz
2023-09-06 21:27 ` [External] " Usama Arif
2023-09-06 21:59 ` Mike Kravetz
2023-09-07 10:14 ` Usama Arif
2023-09-07 18:24 ` Mike Kravetz
2023-09-07 18:37 ` Mike Kravetz
2023-09-08 2:39 ` Muchun Song
2023-09-08 18:29 ` Mike Kravetz
2023-09-08 20:48 ` [External] " Usama Arif
2023-09-22 14:42 ` [v4 0/4] " Pasha Tatashin
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=05DA93DB-84E5-48C3-AA16-F1F2525C8CC8@linux.dev \
--to=muchun.song@linux.dev \
--cc=fam.zheng@bytedance.com \
--cc=liangma@liangbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=punit.agrawal@bytedance.com \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=usama.arif@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome