From: "Theodore Tso" <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Implementation plan for a dedicated block cache for ext4
Date: Fri, 20 Nov 2026 10:21:11 -0500 [thread overview]
Message-ID: <awBYFgSWjU5pDFDy@mit.edu> (raw)
As I had discussed on the ext4 conference call, I've been toying with
the idea of creating a dedicated block cache for ext4. With the help
of AI --- I won't say AI Overlords; I'm conficed the AI Intern, or
perhaps AI PFY is more appropriate :-) --- I've come up with a
high-level design and implementation doc:
https://github.com/tytso/ext4-artifacts/blob/main/jbuf/implementation-plan.md
I'd appreciate comments. I'd suggest reading sections 1 (Goals), 3
(Architectural Decisions and Hazards), and 7 (Block-Device Superblock
Coherency) first.
Nothing here is locked down. One of the things that I am still unsure
about is how nasty including support for data=journal mode is going to
be, and whether we will want to drop support before proceeding.
I expect we'll be doing several rounds of design reviews before I ask
the AI to create the patch series. For people who prefer to look at
code first, feel free to wait until later. But I do think this is one
place where debating things at the detail level of the implementation
plan is more efficient than having reading throguh 37 iterations of a
20 patch series. :-)
- Ted
reply other threads:[~2026-11-20 15:21 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=awBYFgSWjU5pDFDy@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.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