[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250320120250.4087011-1-john.g.garry@oracle.com>
Date: Thu, 20 Mar 2025 12:02:47 +0000
From: John Garry <john.g.garry@...cle.com>
To: brauner@...nel.org, djwong@...nel.org, hch@....de
Cc: linux-fsdevel@...r.kernel.org, dchinner@...hat.com,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org,
ojaswin@...ux.ibm.com, ritesh.list@...il.com,
martin.petersen@...cle.com, tytso@....edu, linux-ext4@...r.kernel.org,
John Garry <john.g.garry@...cle.com>
Subject: [PATCH 0/3] further iomap large atomic writes changes
These iomap changes are spun-off the XFS large atomic writes series at
https://lore.kernel.org/linux-xfs/86a64256-497a-453b-bbba-a5ac6b4cb056@oracle.com/T/#ma99c763221de9d49ea2ccfca9ff9b8d71c8b2677
The XFS parts there are not ready yet, but it is worth having the iomap
changes queued in advance.
Some much earlier changes from that same series were already queued in the
vfs tree, and these patches rework those changes - specifically the
first patch in this series does.
The most other significant change is the patch to rework how the bio flags
are set in the DIO patch.
The baseline is c7be0d72d551 (vfs/vfs-6.15.iomap) Merge patch series
"iomap preliminaries for large atomic write for xfs with CoW"
John Garry (3):
iomap: inline iomap_dio_bio_opflags()
iomap: comment on atomic write checks in iomap_dio_bio_iter()
iomap: rework IOMAP atomic flags
.../filesystems/iomap/operations.rst | 35 ++---
fs/ext4/inode.c | 6 +-
fs/iomap/direct-io.c | 125 ++++++++----------
fs/iomap/trace.h | 2 +-
fs/xfs/xfs_iomap.c | 4 +
include/linux/iomap.h | 12 +-
6 files changed, 91 insertions(+), 93 deletions(-)
--
2.31.1
Powered by blists - more mailing lists