From: Daniel Gomez <da.gomez@samsung.com>
To: Yin Fengwei <fengwei.yin@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"willy@infradead.org" <willy@infradead.org>,
"vishal.moola@gmail.com" <vishal.moola@gmail.com>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"minchan@kernel.org" <minchan@kernel.org>,
"yuzhao@google.com" <yuzhao@google.com>,
"david@redhat.com" <david@redhat.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"shy828301@gmail.com" <shy828301@gmail.com>
Subject: Re: [PATCH v2 3/3] madvise:madvise_free_pte_range(): don't use mapcount() against large folio for sharing check
Date: Wed, 16 Aug 2023 11:44:43 +0000 [thread overview]
Message-ID: <svdxtqiihsjwcbxjp67s6cteprhoxgypf7rjrk2v73ppyn2ogp@ee4ru6vgspl4> (raw)
In-Reply-To: <2bfa1931-1fc6-5d6f-cba1-c7a9eb8a279a@intel.com>
On Wed, Aug 16, 2023 at 07:30:35AM +0800, Yin Fengwei wrote:
>
>
> On 8/15/23 21:25, Daniel Gomez wrote:
> > Hi Yin,
> > On Tue, Aug 08, 2023 at 10:09:17AM +0800, Yin Fengwei wrote:
> >> Commit 98b211d6415f ("madvise: convert madvise_free_pte_range() to use a
> >> folio") replaced the page_mapcount() with folio_mapcount() to check
> >> whether the folio is shared by other mapping.
> >>
> >> It's not correct for large folios. folio_mapcount() returns the total
> >> mapcount of large folio which is not suitable to detect whether the folio
> >> is shared.
> >>
> >> Use folio_estimated_sharers() which returns a estimated number of shares.
> >> That means it's not 100% correct. It should be OK for madvise case here.
> >
> > I'm trying to understand why it should be ok for madvise this change, so
> > I hope it's okay to ask you few questions.
> >
> > folio_mapcount() calculates the total maps for all the subpages of a
> > folio. However, the folio_estimated_sharers does it only for the first
> > subpage making it not true for large folios. Then, wouldn't this change
> > drop support for large folios?
> I saw David explained this very well in another mail.
>
> >
> > Seems like folio_entire_mapcount() is not accurate either because of it
> > does not inclue PTE-mapped sub-pages which I think we need here. Hence,
> > the folio_mapcount(). Could this be something missing in the test side?
> >
> > I tried to replicate the setup with CONFIG_TRANSPARENT_HUGEPAGE but
> > seems like I'm not able to do it:
> >
> > ./cow
> > # [INFO] detected THP size: 2048 KiB
> > # [INFO] detected hugetlb size: 2048 KiB
> > # [INFO] detected hugetlb size: 1048576 KiB
> > # [INFO] huge zeropage is enabled
> > TAP version 13
> > 1..166
> > # [INFO] Anonymous memory tests in private mappings
> > # [RUN] Basic COW after fork() ... with base page
> > not ok 1 MADV_NOHUGEPAGE failed
> > # [RUN] Basic COW after fork() ... with swapped out base page
> > not ok 2 MADV_NOHUGEPAGE failed
> > # [RUN] Basic COW after fork() ... with THP
> > not ok 3 MADV_HUGEPAGE failed
> > # [RUN] Basic COW after fork() ... with swapped-out THP
> > not ok 4 MADV_HUGEPAGE failed
> > # [RUN] Basic COW after fork() ... with PTE-mapped THP
> > not ok 5 MADV_HUGEPAGE failed
> > # [RUN] Basic COW after fork() ... with swapped-out, PTE-mapped THP
> > not ok 6 MADV_HUGEPAGE failed
> > ...
> Can you post the MADV_PAGEOUT and PTE-mapped THP related testing result?
> And I suppose swap need be enabled also for the testing.
You may find a dump of the logs in the link below with system information. Let me
know if you find something wrong in my setup or if you need something else.
Besides CONFIG_TRANSPARENT_HUGEPAGE, CONFIG_SWAP is also enabled in the kernel.
https://gitlab.com/-/snippets/2584135
Also, strace reports ENOSYS for MADV_*:
madvise(0x7f2912465000, 4096, MADV_NOHUGEPAGE) = -1 ENOSYS (Function not implemented)
madvise(0x7f2912000000, 2097152, MADV_HUGEPAGE) = -1 ENOSYS (Function not implemented)
>
>
> Regards
> Yin, Fengwei
>
> >
> >
> > Daniel
> >>
> >> User-visible effects is that the THP is skipped when user call madvise.
> >> But the correct behavior is THP should be split and processed then.
> >>
> >> NOTE: this change is a temporary fix to reduce the user-visible effects
> >> before the long term fix from David is ready.
> >>
> >> Fixes: 98b211d6415f ("madvise: convert madvise_free_pte_range() to use a folio")
> >> Cc: stable@vger.kernel.org
> >> Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
> >> Reviewed-by: Yu Zhao <yuzhao@google.com>
> >> Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
> >> ---
> >> mm/madvise.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/mm/madvise.c b/mm/madvise.c
> >> index 49af35e2d99a..4dded5d27e7e 100644
> >> --- a/mm/madvise.c
> >> +++ b/mm/madvise.c
> >> @@ -683,7 +683,7 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,
> >> if (folio_test_large(folio)) {
> >> int err;
> >>
> >> - if (folio_mapcount(folio) != 1)
> >> + if (folio_estimated_sharers(folio) != 1)
> >> break;
> >> if (!folio_trylock(folio))
> >> break;
> >> --
> >> 2.39.2
> >>
next prev parent reply other threads:[~2023-08-16 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 2:09 [PATCH v2 0/3] don't use mapcount() to check large folio sharing Yin Fengwei
2023-08-08 2:09 ` [PATCH v2 1/3] madvise:madvise_cold_or_pageout_pte_range(): don't use mapcount() against large folio for sharing check Yin Fengwei
2023-08-08 2:09 ` [PATCH v2 2/3] madvise:madvise_free_huge_pmd(): " Yin Fengwei
2023-08-08 2:49 ` Yu Zhao
2023-08-08 2:09 ` [PATCH v2 3/3] madvise:madvise_free_pte_range(): " Yin Fengwei
[not found] ` <CGME20230815132509eucas1p1b34b2852a9c4efe743c8da82867c4cc3@eucas1p1.samsung.com>
2023-08-15 13:25 ` Daniel Gomez
2023-08-15 13:41 ` David Hildenbrand
2023-08-15 23:30 ` Yin Fengwei
2023-08-16 11:44 ` Daniel Gomez [this message]
2023-08-16 12:04 ` Yin, Fengwei
2023-08-16 14:13 ` Daniel Gomez
2023-08-16 15:11 ` David Hildenbrand
2023-08-17 7:57 ` Daniel Gomez
2023-08-08 2:43 ` [PATCH v2 0/3] don't use mapcount() to check large folio sharing Yu Zhao
2023-08-08 4:10 ` Yin, Fengwei
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=svdxtqiihsjwcbxjp67s6cteprhoxgypf7rjrk2v73ppyn2ogp@ee4ru6vgspl4 \
--to=da.gomez@samsung.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=minchan@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=yuzhao@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