From: Matthew Wilcox <willy@infradead.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
bpf@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] State Of The Page
Date: Thu, 26 Jan 2023 16:40:41 +0000 [thread overview]
Message-ID: <Y9KtCc+4n5uANB2f@casper.infradead.org> (raw)
I'd like to do another session on how the struct page dismemberment
is going and what remains to be done. Given how widely struct page is
used, I think there will be interest from more than just MM, so I'd
suggest a plenary session.
If I were hosting this session today, topics would include:
Splitting out users:
- slab (done!)
- netmem (in progress)
- hugetlb (in akpm)
- tail pages (in akpm)
- page tables
- ZONE_DEVICE
Users that really should have their own types:
- zsmalloc
- bootmem
- percpu
- buddy
- vmalloc
Converting filesystems to folios:
- XFS (done)
- AFS (done)
- NFS (in progress)
- ext4 (in progress)
- f2fs (in progress)
- ... others?
Unresolved challenges:
- mapcount
- AnonExclusive
- Splitting anon & file folios apart
- Removing PG_error & PG_private
This will probably all change before May.
I'd like to nominate Vishal Moola & Sidhartha Kumar as invitees based on
their work to convert various functions from pages to folios.
next reply other threads:[~2023-01-26 16:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:40 Matthew Wilcox [this message]
2023-02-21 16:57 ` [LSF/MM/BPF TOPIC] State Of The Page David Howells
2023-02-21 18:08 ` Gao Xiang
2023-02-21 19:09 ` Yang Shi
2023-02-22 2:40 ` Gao Xiang
2023-02-21 19:58 ` Matthew Wilcox
2023-02-22 2:38 ` Gao Xiang
2023-03-02 3:17 ` David Rientjes
2023-03-02 3:50 ` Pasha Tatashin
2023-03-02 4:03 ` Matthew Wilcox
2023-03-02 4:16 ` Pasha Tatashin
2024-01-19 16:24 Matthew Wilcox
2024-01-19 20:31 ` Keith Busch
2024-01-20 14:11 ` Chuck Lever III
2024-01-21 21:00 ` David Rientjes
2024-01-21 23:14 ` Matthew Wilcox
2024-01-21 23:31 ` Pasha Tatashin
2024-01-21 23:54 ` Matthew Wilcox
2024-01-22 0:18 ` Pasha Tatashin
2024-01-24 17:51 ` Christoph Lameter (Ampere)
2024-01-24 17:55 ` Matthew Wilcox
2024-01-24 19:05 ` Christoph Lameter (Ampere)
2024-01-27 10:10 ` Amir Goldstein
2024-01-27 16:18 ` Matthew Wilcox
2024-01-27 17:57 ` Kent Overstreet
2024-01-27 18:43 ` Matthew Wilcox
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=Y9KtCc+4n5uANB2f@casper.infradead.org \
--to=willy@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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).