From: Barry Song <21cnbao@gmail.com>
To: Lance Yang <ioworker0@gmail.com>,
david@redhat.com, Vishal Moola <vishal.moola@gmail.com>
Cc: akpm@linux-foundation.org, zokeefe@google.com,
ryan.roberts@arm.com, shy828301@gmail.com, mhocko@suse.com,
fengwei.yin@intel.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 v2 1/1] mm/madvise: enhance lazyfreeing with mTHP in madvise_free
Date: Thu, 7 Mar 2024 21:10:10 +1300 [thread overview]
Message-ID: <CAGsJ_4xREM-P1mFqeM-s3-cJ9czb6PXwizb-3hOhwaF6+QM5QA@mail.gmail.com> (raw)
In-Reply-To: <CAK1f24k2G_DSEjuqqqPyY0f7+btpYbjfoyMH7btLfP8nkasCTQ@mail.gmail.com>
On Thu, Mar 7, 2024 at 9:00 PM Lance Yang <ioworker0@gmail.com> wrote:
>
> Hey Barry,
>
> Thanks for taking time to review!
>
> On Thu, Mar 7, 2024 at 3:00 PM Barry Song <21cnbao@gmail.com> wrote:
> >
> > On Thu, Mar 7, 2024 at 7:15 PM Lance Yang <ioworker0@gmail.com> wrote:
> > >
> [...]
> > > +static inline bool can_mark_large_folio_lazyfree(unsigned long addr,
> > > + struct folio *folio, pte_t *start_pte)
> > > +{
> > > + int nr_pages = folio_nr_pages(folio);
> > > + fpb_t flags = FPB_IGNORE_DIRTY | FPB_IGNORE_SOFT_DIRTY;
> > > +
> > > + for (int i = 0; i < nr_pages; i++)
> > > + if (page_mapcount(folio_page(folio, i)) != 1)
> > > + return false;
> >
> > we have moved to folio_estimated_sharers though it is not precise, so
> > we don't do
> > this check with lots of loops and depending on the subpage's mapcount.
>
> If we don't check the subpage’s mapcount, and there is a cow folio associated
> with this folio and the cow folio has smaller size than this folio,
> should we still
> mark this folio as lazyfree?
I agree, this is true. However, we've somehow accepted the fact that
folio_likely_mapped_shared
can result in false negatives or false positives to balance the
overhead. So I really don't know :-)
Maybe David and Vishal can give some comments here.
>
> > BTW, do we need to rebase our work against David's changes[1]?
> > [1] https://lore.kernel.org/linux-mm/20240227201548.857831-1-david@redhat.com/
>
> Yes, we should rebase our work against David’s changes.
>
> >
> > > +
> > > + return nr_pages == folio_pte_batch(folio, addr, start_pte,
> > > + ptep_get(start_pte), nr_pages, flags, NULL);
> > > +}
> > > +
> > > static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,
> > > unsigned long end, struct mm_walk *walk)
> > >
> > > @@ -676,11 +690,45 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,
> > > */
> > > if (folio_test_large(folio)) {
> > > int err;
> > > + unsigned long next_addr, align;
> > >
> > > - if (folio_estimated_sharers(folio) != 1)
> > > - break;
> > > - if (!folio_trylock(folio))
> > > - break;
> > > + if (folio_estimated_sharers(folio) != 1 ||
> > > + !folio_trylock(folio))
> > > + goto skip_large_folio;
> >
> >
> > I don't think we can skip all the PTEs for nr_pages, as some of them might be
> > pointing to other folios.
> >
> > for example, for a large folio with 16PTEs, you do MADV_DONTNEED(15-16),
> > and write the memory of PTE15 and PTE16, you get page faults, thus PTE15
> > and PTE16 will point to two different small folios. We can only skip when we
> > are sure nr_pages == folio_pte_batch() is sure.
>
> Agreed. Thanks for pointing that out.
>
> >
> > > +
> > > + align = folio_nr_pages(folio) * PAGE_SIZE;
> > > + next_addr = ALIGN_DOWN(addr + align, align);
> > > +
> > > + /*
> > > + * If we mark only the subpages as lazyfree, or
> > > + * cannot mark the entire large folio as lazyfree,
> > > + * then just split it.
> > > + */
> > > + if (next_addr > end || next_addr - addr != align ||
> > > + !can_mark_large_folio_lazyfree(addr, folio, pte))
> > > + goto split_large_folio;
> > > +
> > > + /*
> > > + * Avoid unnecessary folio splitting if the large
> > > + * folio is entirely within the given range.
> > > + */
> > > + folio_clear_dirty(folio);
> > > + folio_unlock(folio);
> > > + for (; addr != next_addr; pte++, addr += PAGE_SIZE) {
> > > + ptent = ptep_get(pte);
> > > + if (pte_young(ptent) || pte_dirty(ptent)) {
> > > + ptent = ptep_get_and_clear_full(
> > > + mm, addr, pte, tlb->fullmm);
> > > + ptent = pte_mkold(ptent);
> > > + ptent = pte_mkclean(ptent);
> > > + set_pte_at(mm, addr, pte, ptent);
> > > + tlb_remove_tlb_entry(tlb, pte, addr);
> > > + }
> >
> > Can we do this in batches? for a CONT-PTE mapped large folio, you are unfolding
> > and folding again. It seems quite expensive.
>
> Thanks for your suggestion. I'll do this in batches in v3.
>
> Thanks again for your time!
>
> Best,
> Lance
>
> >
> > > + }
> > > + folio_mark_lazyfree(folio);
> > > + goto next_folio;
> > > +
> > > +split_large_folio:
> > > folio_get(folio);
> > > arch_leave_lazy_mmu_mode();
> > > pte_unmap_unlock(start_pte, ptl);
> > > @@ -688,13 +736,28 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,
> > > err = split_folio(folio);
> > > folio_unlock(folio);
> > > folio_put(folio);
> > > - if (err)
> > > - break;
> > > - start_pte = pte =
> > > - pte_offset_map_lock(mm, pmd, addr, &ptl);
> > > - if (!start_pte)
> > > - break;
> > > - arch_enter_lazy_mmu_mode();
> > > +
> > > + /*
> > > + * If the large folio is locked or cannot be split,
> > > + * we just skip it.
> > > + */
> > > + if (err) {
> > > +skip_large_folio:
> > > + if (next_addr >= end)
> > > + break;
> > > + pte += (next_addr - addr) / PAGE_SIZE;
> > > + addr = next_addr;
> > > + }
> > > +
> > > + if (!start_pte) {
> > > + start_pte = pte = pte_offset_map_lock(
> > > + mm, pmd, addr, &ptl);
> > > + if (!start_pte)
> > > + break;
> > > + arch_enter_lazy_mmu_mode();
> > > + }
> > > +
> > > +next_folio:
> > > pte--;
> > > addr -= PAGE_SIZE;
> > > continue;
> > > --
> > > 2.33.1
> > >
Thanks
Barry
next prev parent reply other threads:[~2024-03-07 8:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 6:14 Lance Yang
2024-03-07 7:00 ` Barry Song
2024-03-07 8:00 ` Lance Yang
2024-03-07 8:10 ` Barry Song [this message]
2024-03-07 9:07 ` Ryan Roberts
2024-03-07 9:33 ` Barry Song
2024-03-07 10:50 ` Ryan Roberts
2024-03-07 10:54 ` David Hildenbrand
2024-03-07 10:54 ` David Hildenbrand
2024-03-07 11:13 ` Ryan Roberts
2024-03-07 11:17 ` David Hildenbrand
2024-03-07 14:41 ` Lance Yang
2024-03-07 14:58 ` David Hildenbrand
2024-03-07 15:08 ` Lance Yang
2024-03-07 11:26 ` Barry Song
2024-03-07 11:31 ` David Hildenbrand
2024-03-07 11:42 ` Ryan Roberts
2024-03-07 11:45 ` David Hildenbrand
2024-03-07 12:01 ` Barry Song
2024-03-07 12:04 ` David Hildenbrand
2024-03-07 16:31 ` Ryan Roberts
2024-03-07 18:54 ` Barry Song
2024-03-07 19:48 ` David Hildenbrand
2024-03-08 13:05 ` Ryan Roberts
2024-03-08 13:27 ` David Hildenbrand
2024-03-08 13:48 ` Ryan Roberts
2024-03-08 18:01 ` Barry Song
2024-03-11 9:55 ` Ryan Roberts
2024-03-11 10:01 ` Barry Song
2024-03-11 15:07 ` Ryan Roberts
2024-03-12 10:20 ` 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_4xREM-P1mFqeM-s3-cJ9czb6PXwizb-3hOhwaF6+QM5QA@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=vishal.moola@gmail.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