linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: akpm@linux-foundation.org, Hua Su <suhua.tanke@gmail.com>
Cc: Mike Rapoport <rppt@kernel.org>,
	Wei Yang <richard.weiyang@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memblock: uniformly initialize all reserved pages to MIGRATE_MOVABLE
Date: Mon, 21 Oct 2024 09:52:42 +0300	[thread overview]
Message-ID: <172949345149.2327149.636551407707863142.b4-ty@kernel.org> (raw)
In-Reply-To: <20241021051151.4664-1-suhua.tanke@gmail.com>

From: Mike Rapoport (Microsoft) <rppt@kernel.org>

On Mon, 21 Oct 2024 13:11:51 +0800, Hua Su wrote:
> Currently when CONFIG_DEFERRED_STRUCT_PAGE_INIT is not set, the reserved
> pages are initialized to MIGRATE_MOVABLE by default in memmap_init.
> 
> Reserved memory mainly store the metadata of struct page. When
> HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON=Y and hugepages are allocated,
> the HVO will remap the vmemmap virtual address range to the page which
> vmemmap_reuse is mapped to. The pages previously mapping the range will
> be freed to the buddy system.
> 
> [...]

Applied to for-next branch of memblock.git tree, thanks!

[1/1] memblock: uniformly initialize all reserved pages to MIGRATE_MOVABLE
      commit: ad48825232a91a382f665bb7c3bf0044027791d4

tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: for-next

--
Sincerely yours,
Mike.



  reply	other threads:[~2024-10-21  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  5:11 Hua Su
2024-10-21  6:52 ` Mike Rapoport [this message]
2024-10-25  2:13 ` kernel test robot

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=172949345149.2327149.636551407707863142.b4-ty@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=richard.weiyang@gmail.com \
    --cc=suhua.tanke@gmail.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