linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Roberts <ryan.roberts@arm.com>
To: lsf-pc@lists.linux-foundation.org, Linux-MM <linux-mm@kvack.org>
Cc: Matthew Wilcox <willy@infradead.org>,
	Dave Chinner <david@fromorbit.com>,
	Barry Song <21cnbao@gmail.com>
Subject: Re: [LSF/MM/BPF TOPIC] Mapping text with large folios
Date: Tue, 1 Apr 2025 11:53:45 +0100	[thread overview]
Message-ID: <a8eef05e-dd68-40c5-bdae-5e0a6d35f6af@arm.com> (raw)
In-Reply-To: <6201267f-6d3a-4942-9a61-371bd41d633d@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]

On 19/03/2025 11:38, Ryan Roberts wrote:
> Hi All,
> 
> I know this is very last minute, but I was hoping that it might be possible to
> squeeze in a session to discuss the following?
> 
> Summary/Background:
> 
> On arm64, physically contiguous and naturally aligned regions can take advantage
> of contpte mappings (e.g. 64 KB) to reduce iTLB pressure. However, for file
> regions containing text, current readahead behaviour often yields small,
> misaligned folios, preventing this optimization. This proposal introduces a
> special-case path for executable mappings, performing synchronous reads of an
> architecture-chosen size into large folios (64 KB on arm64). Early performance
> tests on real-world workloads (e.g. nginx, redis, kernel compilation) show ~2-9%
> gains.
> 
> I’ve previously posted attempts to enable this performance improvement ([1],
> [2]), but there were objections and conversation fizzled out. Now that I have
> more compelling performance data, I’m hoping there is now stronger
> justification, and we can find a path forwards.
> 
> What I’d Like to Cover:
> 
>  - Describe how text memory should ideally be mapped and why it benefits
>    performance.
> 
>  - Brief review of performance data.
> 
>  - Discuss options for the best way to encourage text into large folios:
>      - Let the architecture request a preferred size
>      - Extend VMA attributes to include preferred THP size hint
>      - Provide a sysfs knob
>      - Plug into the “mapping min folio order” infrastructure
>      - Other approaches?

Slides from session attached. Includes fix to diagram on slide 3; Matthew was
correct that we don't align to the exact sync/async boundary, but extend the
async region down to the previous folio boundary.

> 
> [1] https://lore.kernel.org/all/20240215154059.2863126-1-ryan.roberts@arm.com/
> [2] https://lore.kernel.org/all/20240717071257.4141363-1-ryan.roberts@arm.com/
> 
> Thanks,
> Ryan

[-- Attachment #2: LSFMM Mapping Text with Large Folios March 2025.pdf --]
[-- Type: application/pdf, Size: 422964 bytes --]

      parent reply	other threads:[~2025-04-01 10:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 15:38 Ryan Roberts
2025-03-19 18:16 ` Yang Shi
2025-03-19 20:38   ` Dave Chinner
2025-03-19 22:13     ` Barry Song
2025-03-20  0:53       ` Dave Chinner
2025-03-20 14:47         ` Ryan Roberts
2025-03-20 12:16       ` Ryan Roberts
2025-03-20 12:13     ` Ryan Roberts
2025-03-19 20:47 ` Barry Song
2025-03-20 14:57   ` Ryan Roberts
2025-03-30  4:46     ` Barry Song
2025-04-01 11:09       ` Ryan Roberts
2025-04-01 10:53 ` Ryan Roberts [this message]

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=a8eef05e-dd68-40c5-bdae-5e0a6d35f6af@arm.com \
    --to=ryan.roberts@arm.com \
    --cc=21cnbao@gmail.com \
    --cc=david@fromorbit.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