[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yekxd1/MboidZo4C@infradead.org>
Date: Thu, 20 Jan 2022 01:55:03 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Jane Chu <jane.chu@...cle.com>
Cc: david@...morbit.com, djwong@...nel.org, dan.j.williams@...el.com,
hch@...radead.org, vishal.l.verma@...el.com, dave.jiang@...el.com,
agk@...hat.com, snitzer@...hat.com, dm-devel@...hat.com,
ira.weiny@...el.com, willy@...radead.org, vgoyal@...hat.com,
linux-fsdevel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org
Subject: Re: [PATCH v3 0/7] DAX poison recovery
On Tue, Jan 11, 2022 at 11:59:23AM -0700, Jane Chu wrote:
> In v3, dax recovery code path is independent of that of
> normal write. Competing dax recovery threads are serialized,
> racing read threads are guaranteed not overlapping with the
> recovery process.
>
> In this phase, the recovery granularity is page, future patch
> will explore recovery in finer granularity.
What tree is this against? I can't apply it to either 5.16 or Linus'
current tree.
Powered by blists - more mailing lists