From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cleanup the filemap / direct I/O interaction v2
Date: Wed, 24 May 2023 08:37:59 +0200 [thread overview]
Message-ID: <20230524063810.1595778-1-hch@lst.de> (raw)
Hi all,
this series cleans up some of the generic write helper calling
conventions and the page cache writeback / invalidation for
direct I/O. This is a spinoff from the no-bufferhead kernel
project, for which we'll want to an use iomap based buffered
write path in the block layer.
Changes since v1:
- remove current->backing_dev_info entirely
- fix the pos/end calculation in direct_write_fallback
- rename kiocb_invalidate_post_write to
kiocb_invalidate_post_direct_write
- typo fixes
diffstat:
block/fops.c | 18 ----
fs/btrfs/file.c | 6 -
fs/ceph/file.c | 6 -
fs/direct-io.c | 10 --
fs/ext4/file.c | 11 --
fs/f2fs/file.c | 3
fs/fuse/file.c | 36 +++-----
fs/gfs2/file.c | 6 -
fs/iomap/buffered-io.c | 9 +-
fs/iomap/direct-io.c | 88 ++++++++-------------
fs/libfs.c | 36 ++++++++
fs/nfs/file.c | 6 -
fs/ntfs/file.c | 2
fs/ntfs3/file.c | 3
fs/xfs/xfs_file.c | 6 -
fs/zonefs/file.c | 4
include/linux/fs.h | 7 -
include/linux/pagemap.h | 4
include/linux/sched.h | 3
mm/filemap.c | 194 +++++++++++++++++++++---------------------------
20 files changed, 193 insertions(+), 265 deletions(-)
next reply other threads:[~2023-05-24 6:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 6:37 Christoph Hellwig [this message]
2023-05-24 6:38 ` [Cluster-devel] [PATCH 01/11] backing_dev: remove current->backing_dev_info Christoph Hellwig
2023-05-24 14:50 ` Darrick J. Wong
2023-05-30 6:56 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 02/11] iomap: update ki_pos a little later in iomap_dio_complete Christoph Hellwig
2023-05-30 6:57 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 03/11] filemap: update ki_pos in generic_perform_write Christoph Hellwig
2023-05-30 6:57 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 04/11] filemap: add a kiocb_write_and_wait helper Christoph Hellwig
2023-05-30 6:58 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 05/11] filemap: add a kiocb_invalidate_pages helper Christoph Hellwig
2023-05-30 6:59 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 06/11] filemap: add a kiocb_invalidate_post_direct_write helper Christoph Hellwig
2023-05-30 6:59 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 07/11] iomap: update ki_pos in iomap_file_buffered_write Christoph Hellwig
2023-05-25 16:02 ` Andreas Gruenbacher
2023-05-30 7:00 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 08/11] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages Christoph Hellwig
2023-05-30 7:02 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 09/11] fs: factor out a direct_write_fallback helper Christoph Hellwig
2023-05-24 7:00 ` Miklos Szeredi
2023-05-25 10:05 ` Christoph Hellwig
2023-05-30 7:03 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 10/11] fuse: update ki_pos in fuse_perform_write Christoph Hellwig
2023-05-24 7:07 ` Miklos Szeredi
2023-05-25 10:09 ` Christoph Hellwig
2023-05-30 7:04 ` Hannes Reinecke
2023-05-24 6:38 ` [Cluster-devel] [PATCH 11/11] fuse: drop redundant arguments to fuse_perform_write Christoph Hellwig
2023-05-24 7:09 ` Miklos Szeredi
2023-05-30 7:04 ` Hannes Reinecke
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=20230524063810.1595778-1-hch@lst.de \
--to=hch@lst.de \
/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).