From: Chuck Lever III <chuck.lever@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] State Of The Page
Date: Sat, 20 Jan 2024 14:11:02 +0000 [thread overview]
Message-ID: <B9605EFB-4AB5-43E2-8538-850B758F37B9@oracle.com> (raw)
In-Reply-To: <ZaqiPSj1wMrTMdHa@casper.infradead.org>
> On Jan 19, 2024, at 11:24 AM, Matthew Wilcox <willy@infradead.org> wrote:
>
> It's probably worth doing another roundup of where we are on our journey
> to separating folios, slabs, pages, etc. Something suitable for people
> who aren't MM experts, and don't care about the details of how page
> allocation works. I can talk for hours about whatever people want to
> hear about but some ideas from me:
>
> - Overview of how the conversion is going
> - Convenience functions for filesystem writers
> - What's next?
> - What's the difference between &folio->page and page_folio(folio, 0)?
> - What are we going to do about bio_vecs?
Thanks for suggesting bio_vecs, one of my current favorite topics.
I'm still interested in any work going on for a bio_vec-enabled
API to the kernel's IOMMU infrastructure, which I've heard Leon R.
is working on.
> - How does all of this work with kmap()?
>
> I'm sure people would like to suggest other questions they have that
> aren't adequately answered already and might be of interest to a wider
> audience.
>
--
Chuck Lever
next prev parent reply other threads:[~2024-01-20 14:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 16:24 [LSF/MM/BPF TOPIC] State Of The Page Matthew Wilcox
2024-01-19 20:31 ` Keith Busch
2024-01-20 14:11 ` Chuck Lever III [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-01-26 16:40 Matthew Wilcox
2023-02-21 16:57 ` 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
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=B9605EFB-4AB5-43E2-8538-850B758F37B9@oracle.com \
--to=chuck.lever@oracle.com \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).