Re: [PATCH v8 1/2] hugetlb: don't delete vma_lock in hugetlb MADV_DONTNEED processing

On Thu, Nov 10, 2022 at 01:48:06PM -0800, Mike Kravetz wrote:

However, Peter seems to prefer just exposing the current zap_page_range_single. The issue with exposing zap_page_range_single as it is today, is that we also need to expose 'struct zap_details' which currently is not visible outside mm/memory.c.

Ah I see, that's okay to me. Thanks,