Re: [External] Re: [PATCH v11 03/11] mm/hugetlb: Free the vmemmap pages associated with each HugeTLB page

2020-12-22 Thread Muchun Song
On Wed, Dec 23, 2020 at 12:32 AM Oscar Salvador wrote: > > On Tue, Dec 22, 2020 at 10:24:32PM +0800, Muchun Song wrote: > > diff --git a/include/linux/mmdebug.h b/include/linux/mmdebug.h > > index 5d0767cb424a..eff5b13a6945 100644 > > --- a/include/linux/mmdebug.h > > +++ b/include/linux/mmdebug.h

Re: [PATCH v11 03/11] mm/hugetlb: Free the vmemmap pages associated with each HugeTLB page

2020-12-22 Thread Oscar Salvador
On Tue, Dec 22, 2020 at 10:24:32PM +0800, Muchun Song wrote: > diff --git a/include/linux/mmdebug.h b/include/linux/mmdebug.h > index 5d0767cb424a..eff5b13a6945 100644 > --- a/include/linux/mmdebug.h > +++ b/include/linux/mmdebug.h > @@ -37,6 +37,13 @@ void dump_mm(const struct mm_struct *mm); >

[PATCH v11 03/11] mm/hugetlb: Free the vmemmap pages associated with each HugeTLB page

2020-12-22 Thread Muchun Song
Every HugeTLB has more than one struct page structure. We __know__ that we only use the first 4(HUGETLB_CGROUP_MIN_ORDER) struct page structures to store metadata associated with each HugeTLB. There are a lot of struct page structures associated with each HugeTLB page. For tail pages, the value of