linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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/3] Start moving write_begin/write_end out of aops
Date: Tue, 30 Jan 2024 05:54:10 +0000	[thread overview]
Message-ID: <20240130055414.2143959-1-willy@infradead.org> (raw)

Christoph wants to remove write_begin/write_end from aops and pass them
to filemap as callback functions.  Hre'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.

Matthew Wilcox (Oracle) (3):
  fs: Introduce buffered_write_operations
  fs: Supply optional buffered_write_operations in buffer.c
  ext4: Convert to buffered_write_operations

 fs/buffer.c                 | 62 +++++++++++++++++++++++--------
 fs/ext4/ext4.h              |  8 +++-
 fs/ext4/file.c              | 10 ++++-
 fs/ext4/inline.c            | 15 +++-----
 fs/ext4/inode.c             | 73 +++++++++++++++++++------------------
 fs/jfs/file.c               |  3 +-
 fs/ramfs/file-mmu.c         |  3 +-
 fs/ufs/file.c               |  2 +-
 include/linux/buffer_head.h | 22 +++++++++--
 include/linux/fs.h          |  3 --
 include/linux/pagemap.h     | 22 +++++++++++
 mm/filemap.c                | 70 +++++++++++++++++++++++------------
 12 files changed, 193 insertions(+), 100 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-01-30  5:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  5:54 Matthew Wilcox (Oracle) [this message]
2024-01-30  5:54 ` [PATCH 1/3] fs: Introduce buffered_write_operations Matthew Wilcox (Oracle)
2024-01-30  8:12   ` Christoph Hellwig
2024-02-01  4:36     ` Matthew Wilcox
2024-02-01  4:42       ` Christoph Hellwig
2024-02-02 19:54         ` Matthew Wilcox
2024-01-31  3:14   ` kernel test robot
2024-01-30  5:54 ` [PATCH 2/3] fs: Supply optional buffered_write_operations in buffer.c Matthew Wilcox (Oracle)
2024-01-30  5:54 ` [PATCH 3/3] ext4: Convert to buffered_write_operations Matthew Wilcox (Oracle)
2024-01-30  6:13   ` Matthew Wilcox
2024-01-30  8:13   ` Christoph Hellwig
2024-02-01 15:12   ` kernel test robot

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=20240130055414.2143959-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).