Dan Williams writes:
> [ adding Christoph ]
>
> On Mon, Apr 24, 2017 at 9:43 AM, Jeff Moyer wrote:
>> Dan Williams writes:
>>
>>> On Mon, Apr 24, 2017 at 9:26 AM, Jeff Moyer wrote:
Dan Williams
[ adding Christoph ]
On Mon, Apr 24, 2017 at 9:43 AM, Jeff Moyer wrote:
> Dan Williams writes:
>
>> On Mon, Apr 24, 2017 at 9:26 AM, Jeff Moyer wrote:
>>> Dan Williams writes:
>>>
The nvdimm_flush()
Dan Williams writes:
> On Mon, Apr 24, 2017 at 9:26 AM, Jeff Moyer wrote:
>> Dan Williams writes:
>>
>>> The nvdimm_flush() mechanism helps to reduce the impact of an ADR
>>> (asynchronous-dimm-refresh) failure. The ADR
On Mon, Apr 24, 2017 at 9:26 AM, Jeff Moyer wrote:
> Dan Williams writes:
>
>> The nvdimm_flush() mechanism helps to reduce the impact of an ADR
>> (asynchronous-dimm-refresh) failure. The ADR mechanism handles flushing
>> platform WPQ
Dan Williams writes:
> The nvdimm_flush() mechanism helps to reduce the impact of an ADR
> (asynchronous-dimm-refresh) failure. The ADR mechanism handles flushing
> platform WPQ (write-pending-queue) buffers when power is removed. The
> nvdimm_flush() mechanism performs
The nvdimm_flush() mechanism helps to reduce the impact of an ADR
(asynchronous-dimm-refresh) failure. The ADR mechanism handles flushing
platform WPQ (write-pending-queue) buffers when power is removed. The
nvdimm_flush() mechanism performs that same function on-demand.
When a pmem namespace is