On Mon, Mar 11, 2019 at 5:08 PM Linus Torvalds <torva...@linux-foundation.org> wrote: > > On Mon, Mar 11, 2019 at 8:37 AM Dan Williams <dan.j.willi...@intel.com> wrote: > > > > Another feature the userspace tooling can support for the PMEM as RAM > > case is the ability to complete an Address Range Scrub of the range > > before it is added to the core-mm. I.e at least ensure that previously > > encountered poison is eliminated. > > Ok, so this at least makes sense as an argument to me. > > In the "PMEM as filesystem" part, the errors have long-term history, > while in "PMEM as RAM" the memory may be physically the same thing, > but it doesn't have the history and as such may not be prone to > long-term errors the same way. > > So that validly argues that yes, when used as RAM, the likelihood for > errors is much lower because they don't accumulate the same way.
In case anyone is looking for the above mentioned tooling for use with the v5.1 kernel, Vishal has released ndctl-v65 with the new "clear-errors" command . : https://pmem.io/ndctl/ndctl-clear-errors.html