From: Lance Yang <ioworker0@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, ryan.roberts@arm.com,
21cnbao@gmail.com, mhocko@suse.com, fengwei.yin@intel.com,
zokeefe@google.com, shy828301@gmail.com, xiehuan09@gmail.com,
wangkefeng.wang@huawei.com, songmuchun@bytedance.com,
peterx@redhat.com, minchan@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/3] mm/madvise: introduce clear_young_dirty_ptes() batch helper
Date: Wed, 17 Apr 2024 12:12:42 +0800 [thread overview]
Message-ID: <CAK1f24mEoC_Pg7-49G=y7dMUaGhzW11_A5sK0EWVhH6K1kjMMA@mail.gmail.com> (raw)
In-Reply-To: <a0d9e198-8799-47b9-ac20-8460b984afee@redhat.com>
On Tue, Apr 16, 2024 at 11:03 PM David Hildenbrand <david@redhat.com> wrote:
>
> On 16.04.24 05:34, Lance Yang wrote:
> > This commit introduces clear_young_dirty_ptes() to replace mkold_ptes().
> > By doing so, we can use the same function for both use cases
> > (madvise_pageout and madvise_free), and it also provides the flexibility
> > to only clear the dirty flag in the future if needed.
> >
> > Suggested-by: Ryan Roberts <ryan.roberts@arm.com>
> > Signed-off-by: Lance Yang <ioworker0@gmail.com>
> > ---
> > include/linux/mm_types.h | 9 +++++
> > include/linux/pgtable.h | 74 ++++++++++++++++++++++++----------------
> > mm/madvise.c | 3 +-
> > 3 files changed, 55 insertions(+), 31 deletions(-)
> >
> > diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> > index c432add95913..28822cd65d2a 100644
> > --- a/include/linux/mm_types.h
> > +++ b/include/linux/mm_types.h
> > @@ -1367,6 +1367,15 @@ enum fault_flag {
> >
> > typedef unsigned int __bitwise zap_flags_t;
> >
> > +/* Flags for clear_young_dirty_ptes(). */
> > +typedef int __bitwise cydp_t;
> > +
> > +/* Clear the access bit */
> > +#define CYDP_CLEAR_YOUNG ((__force cydp_t)BIT(0))
> > +
> > +/* Clear the dirty bit */
> > +#define CYDP_CLEAR_DIRTY ((__force cydp_t)BIT(1))
> > +
> > /*
> > * FOLL_PIN and FOLL_LONGTERM may be used in various combinations with each
> > * other. Here is what they mean, and how to use them:
> > diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
> > index e2f45e22a6d1..18019f037bae 100644
> > --- a/include/linux/pgtable.h
> > +++ b/include/linux/pgtable.h
> > @@ -361,36 +361,6 @@ static inline int ptep_test_and_clear_young(struct vm_area_struct *vma,
> > }
> > #endif
> >
> > -#ifndef mkold_ptes
> > -/**
> > - * mkold_ptes - Mark PTEs that map consecutive pages of the same folio as old.
> > - * @vma: VMA the pages are mapped into.
> > - * @addr: Address the first page is mapped at.
> > - * @ptep: Page table pointer for the first entry.
> > - * @nr: Number of entries to mark old.
> > - *
> > - * May be overridden by the architecture; otherwise, implemented as a simple
> > - * loop over ptep_test_and_clear_young().
> > - *
> > - * Note that PTE bits in the PTE range besides the PFN can differ. For example,
> > - * some PTEs might be write-protected.
> > - *
> > - * Context: The caller holds the page table lock. The PTEs map consecutive
> > - * pages that belong to the same folio. The PTEs are all in the same PMD.
> > - */
> > -static inline void mkold_ptes(struct vm_area_struct *vma, unsigned long addr,
> > - pte_t *ptep, unsigned int nr)
> > -{
> > - for (;;) {
> > - ptep_test_and_clear_young(vma, addr, ptep);
> > - if (--nr == 0)
> > - break;
> > - ptep++;
> > - addr += PAGE_SIZE;
> > - }
> > -}
> > -#endif
> > -
> > #ifndef __HAVE_ARCH_PMDP_TEST_AND_CLEAR_YOUNG
> > #if defined(CONFIG_TRANSPARENT_HUGEPAGE) || defined(CONFIG_ARCH_HAS_NONLEAF_PMD_YOUNG)
> > static inline int pmdp_test_and_clear_young(struct vm_area_struct *vma,
> > @@ -489,6 +459,50 @@ static inline pte_t ptep_get_and_clear(struct mm_struct *mm,
> > }
> > #endif
> >
> > +#ifndef clear_young_dirty_ptes
> > +/**
> > + * clear_young_dirty_ptes - Mark PTEs that map consecutive pages of the
> > + * same folio as old/clean.
> > + * @mm: Address space the pages are mapped into.
> > + * @addr: Address the first page is mapped at.
> > + * @ptep: Page table pointer for the first entry.
> > + * @nr: Number of entries to mark old/clean.
> > + * @flags: Flags to modify the PTE batch semantics.
> > + *
> > + * May be overridden by the architecture; otherwise, implemented by
> > + * get_and_clear/modify/set for each pte in the range.
> > + *
> > + * Note that PTE bits in the PTE range besides the PFN can differ. For example,
> > + * some PTEs might be write-protected.
> > + *
> > + * Context: The caller holds the page table lock. The PTEs map consecutive
> > + * pages that belong to the same folio. The PTEs are all in the same PMD.
> > + */
> > +static inline void clear_young_dirty_ptes(struct vm_area_struct *vma,
> > + unsigned long addr, pte_t *ptep,
> > + unsigned int nr, cydp_t flags)
> > +{
> > + pte_t pte;
> > +
> > + for (;;) {
> > + if (flags == CYDP_CLEAR_YOUNG)
> > + ptep_test_and_clear_young(vma, addr, ptep);
> > + else {
> > + pte = ptep_get_and_clear(vma->vm_mm, addr, ptep);
> > + if (flags & CYDP_CLEAR_YOUNG)
> > + pte = pte_mkold(pte);
> > + if (flags & CYDP_CLEAR_DIRTY)
> > + pte = pte_mkclean(pte);
> > + set_pte_at(vma->vm_mm, addr, ptep, pte);
> > + }
> > + if (--nr == 0)
> > + break;
> > + ptep++;
> > + addr += PAGE_SIZE;
> > + }
> > +}
>
Hey David,
Thanks for taking time to review!
> The complier *might* generate a bit faster code if you check for
> CYDP_CLEAR_YOUNG outside of the loop, so you don't have to recheck on
> each loop iteration.
Nice! I think moving the CYDP_CLEAR_YOUNG check outside of the loop
could speed up the code. I'll make this change in the next version.
>
> For now, nothing to lose sleep about
>
> Acked-by: David Hildenbrand <david@redhat.com>
Thanks again for the review!
Best,
Lance
>
> --
> Cheers,
>
> David / dhildenb
>
next prev parent reply other threads:[~2024-04-17 4:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 3:34 [PATCH v7 0/3] mm/madvise: enhance lazyfreeing with mTHP in madvise_free Lance Yang
2024-04-16 3:34 ` [PATCH v7 1/3] mm/madvise: introduce clear_young_dirty_ptes() batch helper Lance Yang
2024-04-16 16:25 ` Ryan Roberts
2024-04-17 4:13 ` Lance Yang
[not found] ` <a0d9e198-8799-47b9-ac20-8460b984afee@redhat.com>
2024-04-17 4:12 ` Lance Yang [this message]
2024-04-17 5:04 ` Lance Yang
2024-04-17 8:19 ` David Hildenbrand
2024-04-17 9:01 ` Lance Yang
2024-04-17 10:53 ` Ryan Roberts
2024-04-16 3:34 ` [PATCH v7 2/3] mm/arm64: override " Lance Yang
2024-04-16 15:02 ` David Hildenbrand
2024-04-16 16:29 ` Ryan Roberts
2024-04-17 4:16 ` Lance Yang
2024-04-16 3:34 ` [PATCH v7 3/3] mm/madvise: optimize lazyfreeing with mTHP in madvise_free Lance Yang
2024-04-16 16:35 ` Ryan Roberts
2024-04-16 16:52 ` David Hildenbrand
2024-04-17 4:35 ` Lance Yang
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='CAK1f24mEoC_Pg7-49G=y7dMUaGhzW11_A5sK0EWVhH6K1kjMMA@mail.gmail.com' \
--to=ioworker0@gmail.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=wangkefeng.wang@huawei.com \
--cc=xiehuan09@gmail.com \
--cc=zokeefe@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