From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Date: Tue, 21 Jul 2020 17:06:15 +0200 Subject: [Cluster-devel] RFC: iomap write invalidation In-Reply-To: <20200721150432.GH15516@casper.infradead.org> References: <20200713074633.875946-1-hch@lst.de> <20200720215125.bfz7geaftocy4r5l@fiona> <20200721145313.GA9217@lst.de> <20200721150432.GH15516@casper.infradead.org> Message-ID: <20200721150615.GA10330@lst.de> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Tue, Jul 21, 2020 at 04:04:32PM +0100, Matthew Wilcox wrote: > On Tue, Jul 21, 2020 at 04:53:13PM +0200, Christoph Hellwig wrote: > > On Mon, Jul 20, 2020 at 04:51:25PM -0500, Goldwyn Rodrigues wrote: > > > Hi Christoph, > > > > > > On 9:46 13/07, Christoph Hellwig wrote: > > > > Hi all, > > > > > > > > this series has two parts: the first one picks up Dave's patch to avoid > > > > invalidation entierly for reads, picked up deep down from the btrfs iomap > > > > thread. The second one falls back to buffered writes if invalidation fails > > > > instead of leaving a stale cache around. Let me know what you think about > > > > this approch. > > > > > > Which kernel version are these changes expected? > > > btrfs dio switch to iomap depends on this. > > > > No idea. Darrick, are you ok with picking this up soon so that > > Goldwyn can pull it in? > > I thought you were going to respin this with EREMCHG changed to ENOTBLK? Oh, true. I'll do that ASAP.