From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,yangge1116@126.com,sj@kernel.org,muchun.song@linux.dev,david@redhat.com,baolin.wang@linux.alibaba.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [obsolete] replace-free-hugepage-folios-after-migration-fix.patch removed from -mm tree
Date: Sat, 11 Jan 2025 21:27:32 -0800 [thread overview]
Message-ID: <20250112052732.DFB28C4CEE0@smtp.kernel.org> (raw)
The quilt patch titled
Subject: replace-free-hugepage-folios-after-migration-fix
has been removed from the -mm tree. Its filename was
replace-free-hugepage-folios-after-migration-fix.patch
This patch was dropped because it is obsolete
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: replace-free-hugepage-folios-after-migration-fix
Date: Wed Dec 18 05:57:21 PM PST 2024
fix comments, 80-column tweak
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Muchun Song <muchun.song@linux.dev>
Cc: yangge <yangge1116@126.com>
Cc: SeongJae Park <sj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/hugetlb.c | 5 +++--
mm/page_alloc.c | 11 +++++------
2 files changed, 8 insertions(+), 8 deletions(-)
--- a/mm/hugetlb.c~replace-free-hugepage-folios-after-migration-fix
+++ a/mm/hugetlb.c
@@ -2978,7 +2978,7 @@ int isolate_or_dissolve_huge_page(struct
/*
* replace_free_hugepage_folios - Replace free hugepage folios in a given pfn
* range with new folios.
- * @stat_pfn: start pfn of the given pfn range
+ * @start_pfn: start pfn of the given pfn range
* @end_pfn: end pfn of the given pfn range
* Returns 0 on success, otherwise negated error.
*/
@@ -3000,7 +3000,8 @@ int replace_free_hugepage_folios(unsigne
}
if (!folio_ref_count(folio)) {
- ret = alloc_and_dissolve_hugetlb_folio(h, folio, &isolate_list);
+ ret = alloc_and_dissolve_hugetlb_folio(h, folio,
+ &isolate_list);
if (ret)
break;
--- a/mm/page_alloc.c~replace-free-hugepage-folios-after-migration-fix
+++ a/mm/page_alloc.c
@@ -6509,12 +6509,11 @@ int alloc_contig_range_noprof(unsigned l
goto done;
/*
- * When in-use hugetlb pages are migrated, they may simply be
- * released back into the free hugepage pool instead of being
- * returned to the buddy system. After the migration of in-use
- * huge pages is completed, we will invoke the
- * replace_free_hugepage_folios() function to ensure that
- * these hugepages are properly released to the buddy system.
+ * When in-use hugetlb pages are migrated, they may simply be released
+ * back into the free hugepage pool instead of being returned to the
+ * buddy system. After the migration of in-use huge pages is completed,
+ * we will invoke replace_free_hugepage_folios() to ensure that these
+ * hugepages are properly released to the buddy system.
*/
ret = replace_free_hugepage_folios(start, end);
if (ret)
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-swap_cgroup-allocate-swap_cgroup-map-using-vcalloc-fix.patch
mm-page_alloc-add-some-detailed-comments-in-can_steal_fallback-fix.patch
mm-introduce-mmap_lock_speculate_try_beginretry-fix.patch
mm-damon-tests-vaddr-kunith-reduce-stack-consumption.patch
mm-damon-tests-vaddr-kunith-reduce-stack-consumption-fix.patch
mm-fix-outdated-incorrect-code-comments-for-handle_mm_fault-fix.patch
mm-huge_memoryc-rename-shadowed-local.patch
mm-shmem-skip-swapcache-for-swapin-of-synchronous-swap-device-fix.patch
mm-hugetlb-rename-isolate_hugetlb-to-folio_isolate_hugetlb-fix.patch
documentation-filesystems-procrst-fix-possessive-form-of-process.patch
xarray-port-tests-to-kunit-fix.patch
checkpatch-check-return-of-git_commit_info-fix.patch
fault-inject-use-prandom-where-cryptographically-secure-randomness-is-not-needed-fix.patch
hung_task-add-task-flags-blocked-by-coredump-to-log-fix.patch
reply other threads:[~2025-01-12 5:27 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=20250112052732.DFB28C4CEE0@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=sj@kernel.org \
--cc=yangge1116@126.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.