Linux MM tree latest commits
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,muchun.song@linux.dev,david@kernel.org,kas@kernel.org,akpm@linux-foundation.org
Subject: [folded-merged] hugetlb-update-vmemmap_deduprst-fix.patch removed from -mm tree
Date: Tue, 24 Mar 2026 14:16:02 -0700	[thread overview]
Message-ID: <20260324211602.BBC26C19424@smtp.kernel.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3635 bytes --]


The quilt patch titled
     Subject: hugetlb: update vmemmap_dedup.rst
has been removed from the -mm tree.  Its filename was
     hugetlb-update-vmemmap_deduprst-fix.patch

This patch was dropped because it was folded into hugetlb-update-vmemmap_deduprst.patch

------------------------------------------------------
From: Kiryl Shutsemau <kas@kernel.org>
Subject: hugetlb: update vmemmap_dedup.rst
Date: Mon, 2 Mar 2026 10:56:28 +0000

Update the documentation regarding vmemmap optimization for hugetlb to
reflect the changes in how the kernel maps the tail pages.

Fake heads no longer exist. Remove their description.

Link: https://lkml.kernel.org/r/20260302105630.303492-1-kas@kernel.org
Signed-off-by: Kiryl Shutsemau <kas@kernel.org>
Reviewed-by: Muchun Song <muchun.song@linux.dev>
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/mm/vmemmap_dedup.rst |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

--- a/Documentation/mm/vmemmap_dedup.rst~hugetlb-update-vmemmap_deduprst-fix
+++ a/Documentation/mm/vmemmap_dedup.rst
@@ -128,8 +128,8 @@ The first page of ``struct page`` (page
 contains the 4 ``struct page`` necessary to describe the HugeTLB. The remaining
 pages of ``struct page`` (page 1 to page 7) are tail pages.
 
-The optimization is only applied when the size of the struct page is a power-of-2
-In this case, all tail pages of the same order are identical. See
+The optimization is only applied when the size of the struct page is a power
+of 2. In this case, all tail pages of the same order are identical. See
 compound_head(). This allows us to remap the tail pages of the vmemmap to a
 shared, read-only page. The head page is also remapped to a new page. This
 allows the original vmemmap pages to be freed.
@@ -143,7 +143,7 @@ Here is how things look after remapping:
  |           |                     |     1     | ------┐
  |           |                     +-----------+       |
  |           |                     |     2     | ------┼        +----------------------------+
- |           |                     +-----------+       |        | A single, per-node page    |
+ |           |                     +-----------+       |        | A single, per-zone page    |
  |           |                     |     3     | ------┼------> | frame shared among all     |
  |           |                     +-----------+       |        | hugepages of the same size |
  |           |                     |     4     | ------┼        +----------------------------+
_

Patches currently in -mm which might be from kas@kernel.org are

mm-move-max_folio_order-definition-to-mmzoneh.patch
mm-change-the-interface-of-prep_compound_tail.patch
mm-rename-the-compound_head-field-in-the-struct-page-to-compound_info.patch
mm-move-set-clear_compound_head-next-to-compound_head.patch
riscv-mm-align-vmemmap-to-maximal-folio-size.patch
loongarch-mm-align-vmemmap-to-maximal-folio-size.patch
mm-rework-compound_head-for-power-of-2-sizeofstruct-page.patch
mm-sparse-check-memmap-alignment-for-compound_info_has_mask.patch
mm-hugetlb-defer-vmemmap-population-for-bootmem-hugepages.patch
mm-hugetlb-refactor-code-around-vmemmap_walk.patch
x86-vdso-undefine-config_hugetlb_page_optimize_vmemmap-for-vdso32.patch
mm-hugetlb-remove-fake-head-pages.patch
mm-drop-fake-head-checks.patch
hugetlb-remove-vmemmap_synchronize_rcu.patch
mm-hugetlb-remove-hugetlb_optimize_vmemmap_key-static-key.patch
mm-remove-the-branch-from-compound_head.patch
hugetlb-update-vmemmap_deduprst.patch
mm-slab-use-compound_head-in-page_slab.patch


                 reply	other threads:[~2026-03-24 21:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260324211602.BBC26C19424@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=kas@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=muchun.song@linux.dev \
    /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