From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [PATCH 0/7] Start moving write_begin/write_end out of aops
Date: Tue, 28 May 2024 17:48:21 +0100 [thread overview]
Message-ID: <20240528164829.2105447-1-willy@infradead.org> (raw)
Christoph wants to remove write_begin/write_end from aops and pass them
to filemap as callback functions. Here's one possible route to do this.
I combined it with the folio conversion (because why touch the same code
twice?) and tweaked some of the other things (support for ridiculously
large folios with size_t lengths, remove the need to initialise fsdata
by passing only a pointer to the fsdata pointer). And then I converted
ext4, which is probably the worst filesystem to convert because it needs
three different bwops. Most fs will only need one.
Not written yet: convert all the other fs, remove wrappers.
v2:
- Redo how we pass fsdata around so it can persist across multiple
invocations of filemap_perform_write()
- Add ext2
- Minor tweak to iomap
This is against 2bfcfd584ff5 (Linus current head) and will conflict with
other patches in flight.
Matthew Wilcox (Oracle) (7):
fs: Introduce buffered_write_operations
fs: Supply optional buffered_write_operations in buffer.c
buffer: Add buffer_write_begin, buffer_write_end and
__buffer_write_end
fs: Add filemap_symlink()
ext2: Convert to buffered_write_operations
ext4: Convert to buffered_write_operations
iomap: Return the folio from iomap_write_begin()
Documentation/filesystems/locking.rst | 23 ++++
fs/buffer.c | 158 ++++++++++++++++++--------
fs/ext2/ext2.h | 1 +
fs/ext2/file.c | 4 +-
fs/ext2/inode.c | 55 ++++-----
fs/ext2/namei.c | 2 +-
fs/ext4/ext4.h | 24 ++--
fs/ext4/file.c | 12 +-
fs/ext4/inline.c | 66 +++++------
fs/ext4/inode.c | 134 ++++++++++------------
fs/iomap/buffered-io.c | 35 +++---
fs/jfs/file.c | 3 +-
fs/namei.c | 25 ++++
fs/ramfs/file-mmu.c | 3 +-
fs/ufs/file.c | 2 +-
include/linux/buffer_head.h | 28 ++++-
include/linux/fs.h | 3 -
include/linux/pagemap.h | 23 ++++
mm/filemap.c | 77 ++++++++-----
19 files changed, 417 insertions(+), 261 deletions(-)
--
2.43.0
next reply other threads:[~2024-05-28 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 16:48 Matthew Wilcox (Oracle) [this message]
2024-05-28 16:48 ` [PATCH 1/7] fs: Introduce buffered_write_operations Matthew Wilcox (Oracle)
2024-05-28 23:42 ` kernel test robot
2024-05-29 5:21 ` Christoph Hellwig
2024-05-28 16:48 ` [PATCH 2/7] fs: Supply optional buffered_write_operations in buffer.c Matthew Wilcox (Oracle)
2024-05-28 16:48 ` [PATCH 3/7] buffer: Add buffer_write_begin, buffer_write_end and __buffer_write_end Matthew Wilcox (Oracle)
2024-05-28 16:48 ` [PATCH 4/7] fs: Add filemap_symlink() Matthew Wilcox (Oracle)
2024-05-28 16:48 ` [PATCH 5/7] ext2: Convert to buffered_write_operations Matthew Wilcox (Oracle)
2024-05-28 16:48 ` [PATCH 6/7] ext4: " Matthew Wilcox (Oracle)
2024-05-28 23:42 ` kernel test robot
2024-05-28 16:48 ` [PATCH 7/7] iomap: Return the folio from iomap_write_begin() Matthew Wilcox (Oracle)
2024-05-28 23:31 ` kernel test robot
2024-05-28 23:44 ` Dave Chinner
2024-05-29 5:25 ` Christoph Hellwig
2024-05-29 5:20 ` [PATCH 0/7] Start moving write_begin/write_end out of aops Christoph Hellwig
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=20240528164829.2105447-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).