iomap write invalidation v2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: iomap write invalidation v2
From: Christoph Hellwig <hch@xxxxxx>
Date: Tue, 21 Jul 2020 20:31:54 +0200
Cc: Damien Le Moal <damien.lemoal@xxxxxxx>, Naohiro Aota <naohiro.aota@xxxxxxx>, Johannes Thumshirn <jth@xxxxxxxxxx>, Matthew Wilcox <willy@xxxxxxxxxxxxx>, linux-btrfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, cluster-devel@xxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx


Changes since v1:
 - use -ENOTBLK for the direct to buffered I/O fallback everywhere
 - document the choice of -ENOTBLK better
 - update a comment in XFS

Follow-Ups:
- [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
  - From: Christoph Hellwig
- [PATCH 1/3] xfs: use ENOTBLK for direct I/O to buffered I/O fallback
  - From: Christoph Hellwig
- [PATCH 2/3] iomap: Only invalidate page cache pages on direct IO writes
  - From: Christoph Hellwig

Prev by Date: [PATCH 3/3] iomap: fall back to buffered writes for invalidation failures
Next by Date: Re: [PATCH v4 5/7] f2fs: support direct I/O with fscrypt using blk-crypto
Previous by thread: [PATCH v11 00/25] xfs: Delay Ready Attributes
Next by thread: [PATCH 2/3] iomap: Only invalidate page cache pages on direct IO writes
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux