linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Christoph Lameter (Ampere)" <cl@linux.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Yang Shi <shy828301@gmail.com>,
	lsf-pc@lists.linux-foundation.org,
	olivier.singla@amperecomputing.com, Linux MM <linux-mm@kvack.org>,
	Michal Hocko <mhocko@suse.com>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [LSF/MM/BPF TOPIC] Multi-sized THP performance benchmarks and analysis on ARM64
Date: Mon, 8 Apr 2024 17:30:51 +0100	[thread overview]
Message-ID: <ZhQbu8eLYwpTbhah@casper.infradead.org> (raw)
In-Reply-To: <afaddbaa-3c89-d5c1-a1e4-b2739f7d4490@linux.com>

On Thu, Apr 04, 2024 at 11:57:03AM -0700, Christoph Lameter (Ampere) wrote:
> On Mon, 1 Apr 2024, Jonathan Cameron wrote:
> 
> > Sounds like useful data, but is it a suitable topic for LSF-MM?
> > What open questions etc is it raising?
> 
> 
> mTHP is new functionality that will require additional work to support more
> use cases. It is also unclear at this point in what usecases mTHP is useful
> and where no benefit can so far be seen. Also the effect of coalescing
> multiple PTE entries into one TLB entry is new to MM (CONT_PTE).
> 
> Ultimately it would be useful to have mTHP support also provide larger
> blocksize capabilities for filesystem etc etc. mTHP needs to mature and an
> analysis of the arguable a bit experimental state of affairs can help a lot
> in getting there.

Have you been paying attention to anything that's been happening in Linux
development in the last three years?  7b230db3b8d3 introduced folios
in December 2020 (was merged in November 2021 for v5.16).  v5.17 (March
2022) did everything short of enabling large folios for the page cache,
which landed in v5.18 (May 2022).  We started using cont-PTEs for large
folios in August 2023.  Again, the page cache led the way here and we're
just adding support for anonymous large folios (called mTHP) now.

There's still a ton of work to do, but we've been busy doing it since
LSFMM in Puerto Rico (2019) with READ_ONLY_THP_FOR_FS being the very
first result from the group of interested developers.

And if you haven't seen the results that Ryan Roberts has posted for
the tests he's run, I suggest you look them up.  He does a great job
of breaking down how much benefit he sees from the hardware side (use of
contPTE) vs the software side (shorter LRU lists, fewer atomic ops).


  parent reply	other threads:[~2024-04-08 16:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 16:47 Yang Shi
2024-04-01 18:16 ` Jonathan Cameron
2024-04-02 20:04   ` Yang Shi
2024-04-04 18:57   ` Christoph Lameter (Ampere)
2024-04-04 19:33     ` David Hildenbrand
2024-04-09 18:41       ` Yang Shi
2024-04-09 18:44         ` David Hildenbrand
2024-04-30 14:41       ` Michal Hocko
2024-05-01 16:37         ` Yang Shi
2024-04-08 16:30     ` Matthew Wilcox [this message]
2024-04-08 18:56       ` Zi Yan
2024-04-09 10:47         ` Ryan Roberts
2024-06-25 11:12           ` Ryan Roberts
2024-06-25 18:11             ` Christoph Lameter (Ampere)
2024-06-26 10:47               ` Ryan Roberts
2024-06-27 20:54             ` Yang Shi

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=ZhQbu8eLYwpTbhah@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=cl@linux.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mhocko@suse.com \
    --cc=olivier.singla@amperecomputing.com \
    --cc=shy828301@gmail.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