Re: [PATCH 0/6] dax poison recovery with RWF_RECOVERY_DATA flag

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

Subject: Re: [PATCH 0/6] dax poison recovery with RWF_RECOVERY_DATA flag
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 21 Oct 2021 04:31:08 -0700
Cc: nvdimm@xxxxxxxxxxxxxxx, dave.jiang@xxxxxxxxx, snitzer@xxxxxxxxxx, djwong@xxxxxxxxxx, david@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, willy@xxxxxxxxxxxxx, hch@xxxxxxxxxxxxx, dm-devel@xxxxxxxxxx, vgoyal@xxxxxxxxxx, vishal.l.verma@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, dan.j.williams@xxxxxxxxx, ira.weiny@xxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, agk@xxxxxxxxxx
In-reply-to: <20211021001059.438843-1-jane.chu@oracle.com>
References: <20211021001059.438843-1-jane.chu@oracle.com>

Looking over the series I have serious doubts that overloading the
slow path clear poison operation over the fast path read/write
path is such a great idea.

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/dm-devel

Follow-Ups:
- Re: [PATCH 0/6] dax poison recovery with RWF_RECOVERY_DATA flag
  - From: Jane Chu

References:
- [PATCH 0/6] dax poison recovery with RWF_RECOVERY_DATA flag
  - From: Jane Chu

Prev by Date: Re: [PATCH 5/6] dax, pmem: Add data recovery feature to pmem_copy_to/from_iter()
Next by Date: Re: [PATCH 2/6] dax: prepare dax_direct_access() API with DAXDEV_F_RECOVERY flag
Previous by thread: [PATCH 6/6] dm: Ensure dm honors DAXDEV_F_RECOVERY flag on dax only
Next by thread: Re: [PATCH 0/6] dax poison recovery with RWF_RECOVERY_DATA flag
Index(es):
- Date
- Thread

[Index of Archives] [DM Crypt] [Fedora Desktop] [ATA RAID] [Fedora Marketing] [Fedora Packaging] [Fedora SELinux] [Yosemite Discussion] [KDE Users] [Fedora Docs]

Powered by Linux