From: Matthew Wilcox <willy@infradead.org>
To: Barry Song <21cnbao@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux-MM <linux-mm@kvack.org>
Subject: Re: [LSF/MM/BPF TOPIC]mTHP reliable allocation and reclamation
Date: Thu, 16 May 2024 00:41:19 +0100 [thread overview]
Message-ID: <ZkVIH5TgvTTSHvnf@casper.infradead.org> (raw)
In-Reply-To: <CAGsJ_4xgRpfp7yZ_=8mxkaLO=WNVzaeTkFTQYxr8zBLpzFmzzA@mail.gmail.com>
On Fri, May 10, 2024 at 02:22:02PM +1200, Barry Song wrote:
> - The allocation of mTHP isn't consistently reliable; even after
> prolonged use, obtaining large folios
> remains uncertain.
> As an instance, following a few hours of operation, the likelihood
> of successfully allocating large
> folios on a phone may decrease to just 2%.
I'd be curious to know whether you're using a filesystem that supports
large folios or whether the pagecache is full of small folios? The more
places that allocate large folios, the easier it becomes to allocate
large folios.
Also, do you have CONFIG_COMPACTION enabled?
next prev parent reply other threads:[~2024-05-15 23:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 2:22 Barry Song
2024-05-10 2:31 ` Matthew Wilcox
2024-05-10 2:42 ` Barry Song
2024-05-10 14:25 ` [Lsf-pc] " Michal Hocko
2024-05-10 20:33 ` Yu Zhao
2024-05-15 2:42 ` Barry Song
2024-05-15 10:21 ` Karim Manaouil
2024-05-15 10:59 ` Yu Zhao
2024-05-15 13:50 ` Yang Shi
2024-05-15 18:14 ` Barry Song
2024-05-10 21:18 ` Yang Shi
2024-05-14 9:20 ` Barry Song
2024-05-15 13:49 ` Yang Shi
2024-05-15 19:25 ` Barry Song
2024-05-15 21:41 ` Yang Shi
2024-05-15 22:15 ` Barry Song
2024-05-15 23:41 ` Matthew Wilcox [this message]
2024-05-16 0:25 ` Barry Song
2024-05-16 3:19 ` Gao Xiang
2024-05-16 6:57 ` Barry Song
2024-05-16 7:07 ` Gao Xiang
2024-05-22 21:43 ` David Hildenbrand
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=ZkVIH5TgvTTSHvnf@casper.infradead.org \
--to=willy@infradead.org \
--cc=21cnbao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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