From: Barry Song <21cnbao@gmail.com>
To: Lance Yang <ioworker0@gmail.com>
Cc: akpm@linux-foundation.org, david@redhat.com,
fengwei.yin@intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@suse.com, minchan@kernel.org,
peterx@redhat.com, ryan.roberts@arm.com, shy828301@gmail.com,
songmuchun@bytedance.com, wangkefeng.wang@huawei.com,
zokeefe@google.com, Barry Song <v-songbaohua@oppo.com>
Subject: Re: [PATCH 1/1] mm/madvise: enhance lazyfreeing with mTHP in madvise_free
Date: Tue, 27 Feb 2024 15:12:42 +1300 [thread overview]
Message-ID: <CAGsJ_4yAbtMzUifVRLO8nZREOX+nW2_dEcV7++Y7-9SGNK_nsg@mail.gmail.com> (raw)
In-Reply-To: <CAK1f24kuorp8nzdeugURmnGunBhcA5VFTXi_G8M_r+Fmm=_DaQ@mail.gmail.com>
On Tue, Feb 27, 2024 at 2:48 PM Lance Yang <ioworker0@gmail.com> wrote:
>
> On Tue, Feb 27, 2024 at 9:21 AM Barry Song <21cnbao@gmail.com> wrote:
> >
> > > Thanks for your suggestion. I'll use folio_pte_batch() in v2.
> >
> > Hi Lance,
> > Obviously, we both need this. While making large folio swap-in
> > v2, I am exporting folio_pte_batch() as below,
>
> Thanks, Barry.
>
> Could you separate the export of folio_pte_batch() from the large folio
> swap-in v2? Prioritizing the push for this specific change would aid in
> the development of the v2 based on it.
I agree we should make this one pulled in by Andrew early to avoid potential
dependencies and conflicts in two jobs.
>
> Best,
> Lance
>
> >
> > From: Barry Song <v-songbaohua@oppo.com>
> > Date: Tue, 27 Feb 2024 14:05:43 +1300
> > Subject: [PATCH] mm: export folio_pte_batch as a couple of modules need it
> >
> > MADV_FREE, MADV_PAGEOUT and some other modules might need folio_pte_batch
> > to check if a range of PTEs are completely mapped to a large folio with
> > contiguous physcial offset.
> >
> > Cc: Lance Yang <ioworker0@gmail.com>
> > Cc: Ryan Roberts <ryan.roberts@arm.com>
> > Cc: David Hildenbrand <david@redhat.com>
> > Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> > ---
> > mm/internal.h | 13 +++++++++++++
> > mm/memory.c | 2 +-
> > 2 files changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/internal.h b/mm/internal.h
> > index 36c11ea41f47..7e11aea3eda9 100644
> > --- a/mm/internal.h
> > +++ b/mm/internal.h
> > @@ -83,6 +83,19 @@ static inline void *folio_raw_mapping(struct folio *folio)
> > return (void *)(mapping & ~PAGE_MAPPING_FLAGS);
> > }
> >
> > +/* Flags for folio_pte_batch(). */
> > +typedef int __bitwise fpb_t;
> > +
> > +/* Compare PTEs after pte_mkclean(), ignoring the dirty bit. */
> > +#define FPB_IGNORE_DIRTY ((__force fpb_t)BIT(0))
> > +
> > +/* Compare PTEs after pte_clear_soft_dirty(), ignoring the soft-dirty bit. */
> > +#define FPB_IGNORE_SOFT_DIRTY ((__force fpb_t)BIT(1))
> > +
> > +extern int folio_pte_batch(struct folio *folio, unsigned long addr,
> > + pte_t *start_ptep, pte_t pte, int max_nr, fpb_t flags,
> > + bool *any_writable);
> > +
> > void __acct_reclaim_writeback(pg_data_t *pgdat, struct folio *folio,
> > int nr_throttled);
> > static inline void acct_reclaim_writeback(struct folio *folio)
> > diff --git a/mm/memory.c b/mm/memory.c
> > index 6378f6bc22c5..dd9bd67f037a 100644
> > --- a/mm/memory.c
> > +++ b/mm/memory.c
> > @@ -989,7 +989,7 @@ static inline pte_t __pte_batch_clear_ignored(pte_t pte, fpb_t flags)
> > * If "any_writable" is set, it will indicate if any other PTE besides the
> > * first (given) PTE is writable.
> > */
> > -static inline int folio_pte_batch(struct folio *folio, unsigned long addr,
> > +int folio_pte_batch(struct folio *folio, unsigned long addr,
> > pte_t *start_ptep, pte_t pte, int max_nr, fpb_t flags,
> > bool *any_writable)
> > {
> > --
> > 2.34.1
> >
> > > Best,
> > > Lance
> >
Thanks
Barry
> >
next prev parent reply other threads:[~2024-02-27 2:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 12:32 [PATCH 1/1] mm/madvise: enhance lazyfreeing with mTHP in madvise_free Lance Yang
2024-02-26 2:38 ` Yin Fengwei
2024-02-26 8:35 ` Lance Yang
2024-02-26 12:57 ` Ryan Roberts
2024-02-26 13:03 ` David Hildenbrand
2024-02-26 13:47 ` Lance Yang
2024-02-26 4:00 ` Barry Song
2024-02-26 8:37 ` Lance Yang
2024-02-26 8:41 ` David Hildenbrand
2024-02-26 8:55 ` Lance Yang
2024-02-26 13:04 ` Ryan Roberts
2024-02-26 13:50 ` Lance Yang
2024-02-27 1:21 ` Barry Song
2024-02-27 1:48 ` Lance Yang
2024-02-27 2:12 ` Barry Song [this message]
2024-02-27 2:15 ` Lance Yang
2024-02-26 20:49 ` Barry Song
2024-02-27 1:51 ` Yin Fengwei
2024-02-27 2:17 ` Barry Song
2024-02-27 6:14 ` Yin Fengwei
2024-02-27 6:40 ` Barry Song
2024-02-27 6:42 ` Barry Song
2024-02-27 7:02 ` Yin Fengwei
2024-02-27 7:11 ` Barry Song
2024-02-27 7:21 ` Barry Song
2024-02-27 7:42 ` Yin Fengwei
2024-02-27 7:54 ` Barry Song
2024-02-27 8:33 ` Yin Fengwei
2024-02-27 9:01 ` Barry Song
2024-02-26 13:00 ` Ryan Roberts
2024-02-26 13:54 ` 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=CAGsJ_4yAbtMzUifVRLO8nZREOX+nW2_dEcV7++Y7-9SGNK_nsg@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=ioworker0@gmail.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=v-songbaohua@oppo.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).