linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: [LSF/MM/BPF TOPIC] Folios
Date: Wed, 26 Jan 2022 20:38:20 +0000	[thread overview]
Message-ID: <YfGxPKBRdR8FKDcv@casper.infradead.org> (raw)

You might think that with a fortnightly meeting, presentations on the
subject of folios at several conferences and hundreds of patches merged,
I'd be short of things to discuss at LSFMM.  Hah.

From a filesystem point of view,

 - Converting APIs that filesystems implement to use folios (aops, primarily)
   to be folio based instead of page based
 - What it takes to support large (ie multi-page) folios in your
   filesystem
 - Removing old page-based APIs used by filesystems (eg everything in
   mm/folio-compat.c)
 - Converting your filesystem to use iomap.

For the MM crowd:
 - Continued conversion of the MM from pages to folios
   - GUP is done
   - page_vma_mapped is done, not yet posted for review
   - rmap in progress
   - mlock in progress
   - vmscan in progress
   (this list will have changed by May)
 - Splitting out other page types from struct page
 - Dynamically allocating struct folio & shrinking struct page

I'm going to throw a discussion of mapcount into this as well; getting
mapcount right on a multi-page folio is expensive.  I intend to send a full
proposal for making mapcount less accurate by default soon; just haven't
found time to do it yet.

                 reply	other threads:[~2022-01-26 20:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=YfGxPKBRdR8FKDcv@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).