On 1/22/21 1:50 PM, Mike Kravetz wrote: > On 1/22/21 10:42 AM, shu wang wrote: >> Our use case is: >> We maps both PMEM and hugetlb DRAM to process’s address space to provide large amount of memory to the application. Periodically, we clear the soft dirty bit by writing ‘4’ to the clear_refs. Then, we check the page’s soft dirty bit from pagemap and use this information to track write activity to memory. We migrate the data between DRAM and PMEM based the write activity for better performance. >> > > Thank you for the information! > > If someone does not beat me to it, I should be able to look at this next week. Just a quick update. The /proc clear_refs code handles THP pages and 'normal' pages. There is no check/processing for hugetlb pages. All the code will do is clear the VM_SOFTDIRTY vma flag and vma_set_page_prot. None of the individual ptes or page flags are touched. The only soft dirty checking done by the /proc pagemap code is at the vma level. It checks the VM_SOFTDIRTY flag. It does not look for soft dirty on the individual ptes. That explains the behavior described in the bug report. With a quick and dirty hack I could make the code work in limited testing. Much work remains. If anyone wants to jump in and help, feel free. -- Mike Kravetz
