From: SeongJae Park <sj@kernel.org>
To: Lance Yang <ioworker0@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, willy@infradead.org,
maskray@google.com, ziy@nvidia.com, ryan.roberts@arm.com,
david@redhat.com, 21cnbao@gmail.com, mhocko@suse.com,
fengwei.yin@intel.com, zokeefe@google.com, shy828301@gmail.com,
xiehuan09@gmail.com, libang.li@antgroup.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 v4 0/3] Reclaim lazyfree THP without splitting
Date: Wed, 1 May 2024 09:08:03 -0700 [thread overview]
Message-ID: <20240501160803.60988-1-sj@kernel.org> (raw)
In-Reply-To: <20240501042700.83974-1-ioworker0@gmail.com>
Hi Lance,
On Wed, 1 May 2024 12:26:57 +0800 Lance Yang <ioworker0@gmail.com> wrote:
> Hi all,
>
> This series adds support for reclaiming PMD-mapped THP marked as lazyfree
> without needing to first split the large folio via split_huge_pmd_address().
>
> When the user no longer requires the pages, they would use madvise(MADV_FREE)
> to mark the pages as lazy free. Subsequently, they typically would not re-write
> to that memory again.
>
> During memory reclaim, if we detect that the large folio and its PMD are both
> still marked as clean and there are no unexpected references(such as GUP), so we
> can just discard the memory lazily, improving the efficiency of memory
> reclamation in this case.
>
> Performance Testing
> ===================
>
> On an Intel i5 CPU, reclaiming 1GiB of lazyfree THPs using
> mem_cgroup_force_empty() results in the following runtimes in seconds
> (shorter is better):
>
> --------------------------------------------
> | Old | New | Change |
> --------------------------------------------
> | 0.683426 | 0.049197 | -92.80% |
> --------------------------------------------
>
> ---
>
> Changes since v3 [3]
> ====================
> - mm/rmap: integrate PMD-mapped folio splitting into pagewalk loop
> - Resolve compilation errors by handling the case where
> CONFIG_PGTABLE_HAS_HUGE_LEAVES is undefined (thanks to SeongJae Park)
I confirmed that the issue I reported before is disappeared with this version
of the patchset. For the fix,
Tested-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
[...]
next prev parent reply other threads:[~2024-05-01 16:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 4:26 Lance Yang
2024-05-01 4:26 ` [PATCH v4 1/3] mm/rmap: remove duplicated exit code in pagewalk loop Lance Yang
2024-05-07 14:51 ` Zi Yan
2024-05-07 14:53 ` Lance Yang
2024-05-01 4:26 ` [PATCH v4 2/3] mm/rmap: integrate PMD-mapped folio splitting into " Lance Yang
2024-05-07 3:40 ` Baolin Wang
2024-05-07 4:37 ` Lance Yang
2024-05-07 8:17 ` David Hildenbrand
2024-05-07 8:38 ` Lance Yang
2024-05-07 17:22 ` Andrew Morton
2024-05-07 17:33 ` David Hildenbrand
2024-05-07 17:38 ` Andrew Morton
2024-05-07 18:30 ` David Hildenbrand
2024-05-07 15:26 ` Zi Yan
2024-05-08 5:43 ` Lance Yang
2024-05-08 14:07 ` Zi Yan
2024-05-08 14:35 ` Lance Yang
2024-05-08 14:48 ` Zi Yan
2024-05-08 14:56 ` Zi Yan
2024-05-08 15:52 ` Jason Gunthorpe
2024-05-08 16:22 ` Zi Yan
2024-05-08 16:35 ` Jason Gunthorpe
2024-05-09 8:21 ` Lance Yang
2024-05-09 14:53 ` Zi Yan
2024-05-09 8:56 ` Lance Yang
2024-05-01 4:27 ` [PATCH v4 3/3] mm/vmscan: avoid split lazyfree THP during shrink_folio_list() Lance Yang
2024-05-07 4:00 ` Baolin Wang
2024-05-07 6:32 ` Lance Yang
2024-05-07 8:26 ` Lance Yang
2024-05-07 9:33 ` Baolin Wang
2024-05-07 11:37 ` Lance Yang
2024-05-09 9:36 ` Baolin Wang
2024-05-09 12:17 ` Lance Yang
2024-05-07 16:20 ` Zi Yan
2024-05-08 5:14 ` Lance Yang
2024-05-01 16:08 ` SeongJae Park [this message]
2024-05-02 0:30 ` [PATCH v4 0/3] Reclaim lazyfree THP without splitting 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=20240501160803.60988-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=ioworker0@gmail.com \
--cc=libang.li@antgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maskray@google.com \
--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=willy@infradead.org \
--cc=xiehuan09@gmail.com \
--cc=ziy@nvidia.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