From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Dev Jain <dev.jain@arm.com>,
akpm@linux-foundation.org, david@kernel.org, hughd@google.com,
chrisl@kernel.org
Cc: ljs@kernel.org, Liam.Howlett@oracle.com, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
kasong@tencent.com, qi.zheng@linux.dev, shakeel.butt@linux.dev,
baohua@kernel.org, axelrasmussen@google.com, yuanchu@google.com,
weixugc@google.com, riel@surriel.com, harry@kernel.org,
jannh@google.com, pfalcato@suse.de,
baolin.wang@linux.alibaba.com, shikemeng@huaweicloud.com,
nphamcs@gmail.com, bhe@redhat.com, youngjun.park@lge.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v2 2/9] mm/rmap: refactor hugetlb pte clearing in try_to_unmap_one
Date: Sat, 11 Apr 2026 19:45:50 +0800 [thread overview]
Message-ID: <2bfb7fd3-fc0c-47f7-8450-6180b0251ae5@oss.qualcomm.com> (raw)
In-Reply-To: <20260410103204.120409-3-dev.jain@arm.com>
On 4/10/2026 6:31 PM, Dev Jain wrote:
> Simplify the code by refactoring the folio_test_hugetlb() branch into
> a new function.
>
> No functional change is intended.
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> mm/rmap.c | 116 +++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 67 insertions(+), 49 deletions(-)
>
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 62a8c912fd788..a9c43e2f6e695 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1978,6 +1978,67 @@ static inline unsigned int folio_unmap_pte_batch(struct folio *folio,
> FPB_RESPECT_WRITE | FPB_RESPECT_SOFT_DIRTY);
> }
>
> +static inline bool unmap_hugetlb_folio(struct vm_area_struct *vma,
> + struct folio *folio, struct page_vma_mapped_walk *pvmw,
> + struct page *page, enum ttu_flags flags, pte_t *pteval,
> + struct mmu_notifier_range *range, bool *walk_done)
> +{
> + /*
> + * The try_to_unmap() is only passed a hugetlb page
> + * in the case where the hugetlb page is poisoned.
> + */
> + VM_WARN_ON_PAGE(!PageHWPoison(page), page);
As you mentioned "No functional change is intended." in commit message,
but you have changed VM_BUG_ON_PAGE to VM_WARN_ON_PAGE here?
> + /*
> + * huge_pmd_unshare may unmap an entire PMD page.
> + * There is no way of knowing exactly which PMDs may
> + * be cached for this mm, so we must flush them all.
> + * start/end were already adjusted above to cover this
> + * range.
> + */
> + flush_cache_range(vma, range->start, range->end);
> +
> + /*
> + * To call huge_pmd_unshare, i_mmap_rwsem must be
> + * held in write mode. Caller needs to explicitly
> + * do this outside rmap routines.
> + *
> + * We also must hold hugetlb vma_lock in write mode.
> + * Lock order dictates acquiring vma_lock BEFORE
> + * i_mmap_rwsem. We can only try lock here and fail
> + * if unsuccessful.
> + */
> + if (!folio_test_anon(folio)) {
> + struct mmu_gather tlb;
> +
> + VM_WARN_ON(!(flags & TTU_RMAP_LOCKED));
ditto
Thanks,
Jie
> + if (!hugetlb_vma_trylock_write(vma)) {
> + *walk_done = true;
> + return false;
> + }
> +
> + tlb_gather_mmu_vma(&tlb, vma);
> + if (huge_pmd_unshare(&tlb, vma, pvmw->address, pvmw->pte)) {
> + hugetlb_vma_unlock_write(vma);
> + huge_pmd_unshare_flush(&tlb, vma);
> + tlb_finish_mmu(&tlb);
> + /*
> + * The PMD table was unmapped,
> + * consequently unmapping the folio.
> + */
> + *walk_done = true;
> + return true;
> + }
> + hugetlb_vma_unlock_write(vma);
> + tlb_finish_mmu(&tlb);
> + }
> + *pteval = huge_ptep_clear_flush(vma, pvmw->address, pvmw->pte);
> + if (pte_dirty(*pteval))
> + folio_mark_dirty(folio);
> +
> + *walk_done = false;
> + return true;
> +}
> +
> /*
> * @arg: enum ttu_flags will be passed to this argument
> */
> @@ -2115,56 +2176,13 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
> PageAnonExclusive(subpage);
>
> if (folio_test_hugetlb(folio)) {
> - bool anon = folio_test_anon(folio);
> -
> - /*
> - * The try_to_unmap() is only passed a hugetlb page
> - * in the case where the hugetlb page is poisoned.
> - */
> - VM_BUG_ON_PAGE(!PageHWPoison(subpage), subpage);
> - /*
> - * huge_pmd_unshare may unmap an entire PMD page.
> - * There is no way of knowing exactly which PMDs may
> - * be cached for this mm, so we must flush them all.
> - * start/end were already adjusted above to cover this
> - * range.
> - */
> - flush_cache_range(vma, range.start, range.end);
> + bool walk_done;
>
> - /*
> - * To call huge_pmd_unshare, i_mmap_rwsem must be
> - * held in write mode. Caller needs to explicitly
> - * do this outside rmap routines.
> - *
> - * We also must hold hugetlb vma_lock in write mode.
> - * Lock order dictates acquiring vma_lock BEFORE
> - * i_mmap_rwsem. We can only try lock here and fail
> - * if unsuccessful.
> - */
> - if (!anon) {
> - struct mmu_gather tlb;
> -
> - VM_BUG_ON(!(flags & TTU_RMAP_LOCKED));
> - if (!hugetlb_vma_trylock_write(vma))
> - goto walk_abort;
> -
> - tlb_gather_mmu_vma(&tlb, vma);
> - if (huge_pmd_unshare(&tlb, vma, address, pvmw.pte)) {
> - hugetlb_vma_unlock_write(vma);
> - huge_pmd_unshare_flush(&tlb, vma);
> - tlb_finish_mmu(&tlb);
> - /*
> - * The PMD table was unmapped,
> - * consequently unmapping the folio.
> - */
> - goto walk_done;
> - }
> - hugetlb_vma_unlock_write(vma);
> - tlb_finish_mmu(&tlb);
> - }
> - pteval = huge_ptep_clear_flush(vma, address, pvmw.pte);
> - if (pte_dirty(pteval))
> - folio_mark_dirty(folio);
> + ret = unmap_hugetlb_folio(vma, folio, &pvmw, subpage,
> + flags, &pteval, &range,
> + &walk_done);
> + if (walk_done)
> + goto walk_done;
> } else if (likely(pte_present(pteval))) {
> nr_pages = folio_unmap_pte_batch(folio, &pvmw, flags, pteval);
> end_addr = address + nr_pages * PAGE_SIZE;
next prev parent reply other threads:[~2026-04-11 11:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 10:31 [PATCH v2 0/9] Optimize anonymous large folio unmapping Dev Jain
2026-04-10 10:31 ` [PATCH v2 1/9] mm/rmap: initialize nr_pages to 1 at loop start in try_to_unmap_one Dev Jain
2026-04-11 1:02 ` Barry Song
2026-04-10 10:31 ` [PATCH v2 2/9] mm/rmap: refactor hugetlb pte clearing " Dev Jain
2026-04-11 8:55 ` Barry Song
2026-04-11 16:05 ` Dev Jain
2026-04-11 16:24 ` Dev Jain
2026-04-11 11:45 ` Jie Gan [this message]
2026-04-11 16:08 ` Dev Jain
2026-04-10 10:31 ` [PATCH v2 3/9] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-04-10 10:31 ` [PATCH v2 4/9] mm/memory: Batch set uffd-wp markers during zapping Dev Jain
2026-04-10 10:32 ` [PATCH v2 5/9] mm/rmap: batch unmap folios belonging to uffd-wp VMAs Dev Jain
2026-04-10 10:32 ` [PATCH v2 6/9] mm/swapfile: Add batched version of folio_dup_swap Dev Jain
2026-04-10 10:32 ` [PATCH v2 7/9] mm/swapfile: Add batched version of folio_put_swap Dev Jain
2026-04-10 10:32 ` [PATCH v2 8/9] mm/rmap: Add batched version of folio_try_share_anon_rmap_pte Dev Jain
2026-04-10 10:32 ` [PATCH v2 9/9] mm/rmap: enable batch unmapping of anonymous folios Dev Jain
2026-04-10 13:53 ` [PATCH v2 0/9] Optimize anonymous large folio unmapping Lorenzo Stoakes
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=2bfb7fd3-fc0c-47f7-8450-6180b0251ae5@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=harry@kernel.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=pfalcato@suse.de \
--cc=qi.zheng@linux.dev \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=youngjun.park@lge.com \
--cc=yuanchu@google.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