From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cleanup the filemap / direct I/O interaction v3
Date: Wed, 31 May 2023 09:19:58 +0200 [thread overview]
Message-ID: <20230531072006.476386-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 v2:
- stick to the existing behavior of returning a short write
if the buffer fallback write or sync fails
- bring back "fuse: use direct_write_fallback" which accidentally
got lost in v2
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 | 4 -
fs/gfs2/file.c | 6 --
fs/iomap/buffered-io.c | 9 ++-
fs/iomap/direct-io.c | 88 ++++++++++++---------------------
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 | 5 -
include/linux/pagemap.h | 4 +
include/linux/sched.h | 3 -
mm/filemap.c | 126 ++++++++++++++++++++++++++----------------------
19 files changed, 125 insertions(+), 195 deletions(-)
next reply other threads:[~2023-05-31 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:19 Christoph Hellwig [this message]
2023-05-31 7:19 ` [Cluster-devel] [PATCH 1/8] backing_dev: remove current->backing_dev_info Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 2/8] iomap: update ki_pos a little later in iomap_dio_complete Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 3/8] filemap: update ki_pos in generic_perform_write Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 4/8] filemap: add a kiocb_write_and_wait helper Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 5/8] filemap: add a kiocb_invalidate_pages helper Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 6/8] filemap: add a kiocb_invalidate_post_direct_write helper Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 7/8] iomap: update ki_pos in iomap_file_buffered_write Christoph Hellwig
2023-05-31 7:20 ` [Cluster-devel] [PATCH 8/8] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages 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=20230531072006.476386-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).