[PATCH 2/3] dax: introduce dax clear poison to page aligned dax pwrite operation

Currenty, when pwrite(2) s issued to a dax range that contains poison, the pwrite(2) fails with EIO. Well, if the hardware backend of the dax device is capable of clearing poison, try that and resume the write. Signed-off-by: Jane Chu --- fs/dax.c | 9 + 1 file changed, 9 insertions(+)

[PATCH 1/3] dax: introduce dax_operation dax_clear_poison

Though not all dax backend hardware has the capability of clearing poison on the fly, but dax backed by Intel DCPMEM has such capability, and it's desirable to, first, speed up repairing by means of it; second, maintain backend continuity instead of fragmenting it in search for clean blocks. Signe

[PATCH 2/3] dax: introduce dax_clear_poison to dax pwrite operation

When pwrite(2) encounters poison in a dax range, it fails with EIO. But if the backend hardware of the dax device is capable of clearing poison, try that and resume the write. Signed-off-by: Jane Chu --- fs/dax.c | 9 + 1 file changed, 9 insertions(+) diff --git a/fs/dax.c b/fs/dax.c in

[PATCH 0/3] dax: clear poison on the fly along pwrite

If pwrite(2) encounters poison in a pmem range, it fails with EIO. This is unecessary if hardware is capable of clearing the poison. Though not all dax backend hardware has the capability of clearing poison on the fly, but dax backed by Intel DCPMEM has such capability, and it's desirable to, firs

[PATCH 3/3] libnvdimm/pmem: Provide pmem_dax_clear_poison for dax operation

Provide pmem_dax_clear_poison() to struct dax_operations.clear_poison. Signed-off-by: Jane Chu --- drivers/nvdimm/pmem.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c index 1e0615b8565e..307a53aa3432 100644 --- a/drivers/nvdi

Re: [RESEND PATCH v4 1/4] drivers/nvdimm: Add nvdimm pmu structure

On Thu, Sep 9, 2021 at 12:56 AM kajoljain wrote: > > > > On 9/8/21 3:29 AM, Dan Williams wrote: > > Hi Kajol, > > > > Apologies for the delay in responding to this series, some comments below: > > Hi Dan, > No issues, thanks for reviewing the patches. > > > > > On Thu, Sep 2, 2021 at 10:10 PM

Re: [RESEND PATCH v4 1/4] drivers/nvdimm: Add nvdimm pmu structure

On Tue, Sep 14, 2021 at 9:08 PM Dan Williams wrote: > > On Thu, Sep 9, 2021 at 12:56 AM kajoljain wrote: > > > > > > > > On 9/8/21 3:29 AM, Dan Williams wrote: > > > Hi Kajol, > > > > > > Apologies for the delay in responding to this series, some comments below: > > > > Hi Dan, > > No issues,

Re: [PATCH 0/3] dax: clear poison on the fly along pwrite

On Tue, Sep 14, 2021 at 4:32 PM Jane Chu wrote: > > If pwrite(2) encounters poison in a pmem range, it fails with EIO. > This is unecessary if hardware is capable of clearing the poison. > > Though not all dax backend hardware has the capability of clearing > poison on the fly, but dax backed by I

Re: [PATCH v2] device-dax: use fallback nid when numa node is invalid

On Mon, Sep 13, 2021 at 7:06 PM Justin He wrote: > > Hi Dan, > > > -Original Message- > > From: Dan Williams > > Sent: Friday, September 10, 2021 11:42 PM > > To: Justin He > > Cc: Vishal Verma ; Dave Jiang > > ; David Hildenbrand ; Linux NVDIMM > > ; Linux Kernel Mailing List > ker...@

RE: [PATCH v2] device-dax: use fallback nid when numa node is invalid

> -Original Message- > From: Dan Williams > Sent: Wednesday, September 15, 2021 1:16 PM > To: Justin He > Cc: Vishal Verma ; Dave Jiang > ; David Hildenbrand ; Linux NVDIMM > ; Linux Kernel Mailing List ker...@vger.kernel.org>; nd > Subject: Re: [PATCH v2] device-dax: use fallback nid