Messages in this thread | | | Subject | Re: [PATCH RESEND v6 1/9] pagemap: Introduce ->memory_failure() | From | Jane Chu <> | Date | Thu, 5 Aug 2021 18:17:33 -0700 |
| |
The filesystem part of the pmem failure handling is at minimum built on PAGE_SIZE granularity - an inheritance from general memory_failure handling. However, with Intel's DCPMEM technology, the error blast radius is no more than 256bytes, and might get smaller with future hardware generation, also advanced atomic 64B write to clear the poison. But I don't see any of that could be incorporated in, given that the filesystem is notified a corruption with pfn, rather than an exact address.
So I guess this question is also for Dan: how to avoid unnecessarily repairing a PMD range for a 256B corrupt range going forward?
thanks, -jane
On 7/30/2021 3:01 AM, Shiyang Ruan wrote: > When memory-failure occurs, we call this function which is implemented > by each kind of devices. For the fsdax case, pmem device driver > implements it. Pmem device driver will find out the filesystem in which > the corrupted page located in. And finally call filesystem handler to > deal with this error. > > The filesystem will try to recover the corrupted data if necessary.
| |