From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: [PATCH v2 0/6] mm: hugetlb+THP folio and migration cleanups
Date: Mon, 13 Jan 2025 14:16:05 +0100 [thread overview]
Message-ID: <20250113131611.2554758-1-david@redhat.com> (raw)
Some cleanups around more folio conversion and migration handling that
I collected working on random stuff.
Patch #2->#6 were previous sent as part of [1], but I think they make
sense independent of that.
[1] https://lkml.kernel.org/r/20241108162040.159038-1-tabba@google.com
v1 -> v2:
* "mm/hugetlb: rename isolate_hugetlb() to folio_isolate_hugetlb()"
* Use "-" vs. ":" in kerneldoc
* "mm/migrate: don't call folio_putback_active_hugetlb() on dst hugetlb
folio"
* Also care about activelist and adjust patch description
* "mm/hugetlb-cgroup: convert hugetlb_cgroup_css_offline() to work on
folios"
* Extend patch description
* "mm/hugetlb: use folio->lru int demote_free_hugetlb_folios()"
* Also use "new_folio->mapping = NULL", and calculate new_folio like
__split_huge_page_tail(), adding also a comment.
* Adjust patch description
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Muchun Song <muchun.song@linux.dev>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
David Hildenbrand (6):
mm/huge_memory: convert has_hwpoisoned into a pure folio flag
mm/hugetlb: rename isolate_hugetlb() to folio_isolate_hugetlb()
mm/migrate: don't call folio_putback_active_hugetlb() on dst hugetlb
folio
mm/hugetlb: rename folio_putback_active_hugetlb() to
folio_putback_hugetlb()
mm/hugetlb-cgroup: convert hugetlb_cgroup_css_offline() to work on
folios
mm/hugetlb: use folio->lru int demote_free_hugetlb_folios()
include/linux/hugetlb.h | 8 +++---
include/linux/page-flags.h | 6 ++---
mm/gup.c | 2 +-
mm/huge_memory.c | 2 +-
mm/hugetlb.c | 54 +++++++++++++++++++++++++++++++++-----
mm/hugetlb_cgroup.c | 17 ++++++------
mm/mempolicy.c | 2 +-
mm/migrate.c | 20 +++++++-------
8 files changed, 74 insertions(+), 37 deletions(-)
base-commit: 0703fa3785f1b969a3a98fc9bb3e4ae5062684ea
--
2.47.1
next reply other threads:[~2025-01-13 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 13:16 David Hildenbrand [this message]
2025-01-13 13:16 ` [PATCH v2 1/6] mm/huge_memory: convert has_hwpoisoned into a pure folio flag David Hildenbrand
2025-01-13 13:16 ` [PATCH v2 2/6] mm/hugetlb: rename isolate_hugetlb() to folio_isolate_hugetlb() David Hildenbrand
2025-01-13 13:16 ` [PATCH v2 3/6] mm/migrate: don't call folio_putback_active_hugetlb() on dst hugetlb folio David Hildenbrand
2025-01-13 13:16 ` [PATCH v2 4/6] mm/hugetlb: rename folio_putback_active_hugetlb() to folio_putback_hugetlb() David Hildenbrand
2025-01-13 13:16 ` [PATCH v2 5/6] mm/hugetlb-cgroup: convert hugetlb_cgroup_css_offline() to work on folios David Hildenbrand
2025-01-13 13:16 ` [PATCH v2 6/6] mm/hugetlb: use folio->lru int demote_free_hugetlb_folios() David Hildenbrand
2025-01-13 15:18 ` Sidhartha Kumar
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=20250113131611.2554758-1-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--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