[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200721150615.GA10330@lst.de>
Date: Tue, 21 Jul 2020 17:06:15 +0200
From: Christoph Hellwig <hch@....de>
To: Matthew Wilcox <willy@...radead.org>
Cc: Christoph Hellwig <hch@....de>,
Goldwyn Rodrigues <rgoldwyn@...e.de>,
Dave Chinner <david@...morbit.com>,
Damien Le Moal <damien.lemoal@....com>,
Naohiro Aota <naohiro.aota@....com>,
Johannes Thumshirn <jth@...nel.org>,
linux-btrfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
cluster-devel@...hat.com, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org
Subject: Re: RFC: iomap write invalidation
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.
Powered by blists - more mailing lists