[lkml]   [2018]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2] libnvdimm: re-enable deep flush for pmem devices
On Tue, Feb 13, 2018 at 5:17 AM, Jeff Moyer <> wrote:
> Dan Williams <> writes:
>> On Mon, Feb 12, 2018 at 2:53 PM, Jeff Moyer <> wrote:
>>> Dave Jiang <> writes:
>>>> Re-enable deep flush so that users always have a way to be sure that a write
>>>> does make it all the way out to the NVDIMM. The PMEM driver writes always
>>>> make it "all the way to the NVDIMM", and it relies on the ADR mechanism to
>>>> flush the write buffers on power failure. Deep flush is there to explicitly
>>>> flush those write buffers to protect against (rare) ADR failure.
>>>> This change prevents a regression in deep flush behavior so that applications
>>>> can continue to depend on fsync() as a mechanism to trigger deep flush in the
>>>> filesystem-dax case.
>>> That's still very confusing text. Specifically, the part where you say
>>> that pmem driver writes always make it to the DIMM. I think the
>>> changelog could start with "Deep flush is there to explicitly flush
>>> write buffers...." Anyway, the fix looks right to me.
>> I ended up changing the commit message to this, let me know if it reads better:
> Thanks. It's still unclear to me what the text, "The PMEM driver writes
> always arrive at the NVDIMM" means. However, it's good enough.

Yeah, Dave, had similar feedback. A better way of saying it is that
the writes always arrive at the persistence domain, but deep flush
pushes them to the smallest platform failure domain. On current
platforms that's to the ADR domain and past the ADR domain.

 \ /
  Last update: 2018-02-13 16:58    [W:0.114 / U:0.948 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site