From: Barry Song <21cnbao@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Matthew Wilcox <willy@infradead.org>,
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 18:57:26 +1200 [thread overview]
Message-ID: <CAGsJ_4wtE8OcpinuqVwG4jtdx6Qh5f+TON6wz+4HMCq=A2qFcA@mail.gmail.com> (raw)
In-Reply-To: <c25a6d0d-735f-4e6e-85c2-183e240d86ab@linux.alibaba.com>
On Thu, May 16, 2024 at 3:19 PM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>
>
>
> On 2024/5/16 08:25, Barry Song wrote:
> > On Thu, May 16, 2024 at 11:41 AM Matthew Wilcox <willy@infradead.org> wrote:
> >>
> >> 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.
> >
> > I am not using file systems with large folios as neither erofs(compressed files)
>
> Side note: I will offically support large folios of compressed files
> upstream in the upcoming one or two cycle, it's almost okay in the current
> codebase.
Thanks for passing along this fantastic news! Feel free to reach me when you
send the patchset. I'm eager to delve into the code and run some tests.
>
> I have to do more tests to ensure it doesn't break anything...
>
> Thanks,
> Gao Xiang
>
> > nor f2fs supports large folios. So, yes, the page cache is full of small folios.
> >
> >>
> >> Also, do you have CONFIG_COMPACTION enabled?
> >>
> >
> > Yes. COMPACTION is enabled.
> >
Thanks
Barry
next prev parent reply other threads:[~2024-05-16 6:57 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
2024-05-16 0:25 ` Barry Song
2024-05-16 3:19 ` Gao Xiang
2024-05-16 6:57 ` Barry Song [this message]
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='CAGsJ_4wtE8OcpinuqVwG4jtdx6Qh5f+TON6wz+4HMCq=A2qFcA@mail.gmail.com' \
--to=21cnbao@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=willy@infradead.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