linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: Yu Zhao <yuzhao@google.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux-MM <linux-mm@kvack.org>,
	 Yang Shi <shy828301@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	 "Yin, Fengwei" <fengwei.yin@intel.com>,
	Hugh Dickins <hughd@google.com>,
	 "Kirill A . Shutemov" <kirill@shutemov.name>
Subject: Re: [LSF/MM/BPF TOPIC] Flexible orders for anonymous folios
Date: Wed, 22 Feb 2023 16:16:38 -0800	[thread overview]
Message-ID: <CAJuCfpG95Y6qbozZQXUmMRFgVTrCZ7oSvBp=fJYyooPvhVTtZw@mail.gmail.com> (raw)
In-Reply-To: <CAOUHufYEj+pYK7tO4JGJx80xYsFdgGcHzMjqr5tJnYuuf7YG7w@mail.gmail.com>

On Wed, Feb 22, 2023 at 3:56 PM Yu Zhao <yuzhao@google.com> wrote:
>
> Currently anonymous folios only support two orders: 0 and the PMD
> order. Flexible orders for anonymous folios can resist both internal
> or external fragmentations when the PMD order is too underutilized or
> costly to allocate. Flexible orders can also leverage the TLB
> coalescing feature, .e.g., order 3 for AMD and order 4 for ARM CPUs.
>
> Discussion points:
> 1. The page fault path: determining the best order and the fallback policy.
> 2. The reclaim path: detecting the utilization and the splitting policy.
> 3. The refcount and the mapcount models, e.g., reuse the PMD-mapped
> THP model or not.
> 4. The splitting, and the collapsing if needed.
> 5. Other paths: COW, GUP, madvise(), mprotect(), page migration, etc.
>
> A bit of history:
> I discussed this topic at Matthew's THP Cabal meeting a couple of
> years ago, as one of the major use cases of folios. Around the same
> time, I tried to get Hugh to work with me on it, since he tried
> something similar back in 2001 [1]. William's page clustering from
> 2003 [2] is also based on that, btw. Then I put the idea on the back
> burner.
>
> Now it seems to be a good time to revisit. Yang Shi and I have been
> looking at some details, trying to scope out the work that would be
> required. We don't have anything definitive yet, but we should have
> enough to share by the time of the LSF/MM/BPF.

This might be useful for Android. I would like to participate in this
discussion.

>
> [1] https://lore.kernel.org/linux-mm/Pine.LNX.4.21.0107051737340.1577-100000@localhost.localdomain/
> [2] https://lwn.net/Articles/23785/
>


  reply	other threads:[~2023-02-23  0:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 23:55 Yu Zhao
2023-02-23  0:16 ` Suren Baghdasaryan [this message]
2023-02-23  4:01 ` Matthew Wilcox
2023-02-23  4:45   ` Yin, Fengwei
2023-02-23 18:07   ` Yang Shi
2023-03-01 10:35   ` Ryan Roberts
2023-03-06 20:57   ` Zi Yan
2023-02-24 20:34 ` Jason Gunthorpe
2023-02-26  1:30 ` Hillf Danton
2023-02-26  2:34   ` Matthew Wilcox
2023-02-26  4:12     ` Hillf Danton
2023-02-27  0:58       ` Hillf Danton
2023-03-01 23:29 ` Chris Li
2023-03-02  4:05 ` Yu Zhao

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='CAJuCfpG95Y6qbozZQXUmMRFgVTrCZ7oSvBp=fJYyooPvhVTtZw@mail.gmail.com' \
    --to=surenb@google.com \
    --cc=fengwei.yin@intel.com \
    --cc=hughd@google.com \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=shy828301@gmail.com \
    --cc=willy@infradead.org \
    --cc=yuzhao@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