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.
