[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35c5217d-eb8f-6f70-544a-a3e8bd009a46@oracle.com>
Date: Mon, 8 Nov 2021 11:33:08 -0800
From: Mike Kravetz <mike.kravetz@...cle.com>
To: Muchun Song <songmuchun@...edance.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Oscar Salvador <osalvador@...e.de>,
Michal Hocko <mhocko@...e.com>,
David Hildenbrand <david@...hat.com>,
Jonathan Corbet <corbet@....net>,
Matthew Wilcox <willy@...radead.org>
Cc: Xiongchun duan <duanxiongchun@...edance.com>,
fam.zheng@...edance.com, Muchun Song <smuchun@...il.com>,
Qi Zheng <zhengqi.arch@...edance.com>,
linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
"Song Bao Hua (Barry Song)" <song.bao.hua@...ilicon.com>,
Barry Song <21cnbao@...il.com>,
Chen Huang <chenhuang5@...wei.com>,
"Bodeddula, Balasubramaniam" <bodeddub@...zon.com>
Subject: Re: [PATCH v7 0/5] Free the 2nd vmemmap page associated with each
HugeTLB page
On 11/8/21 12:16 AM, Muchun Song wrote:
> On Mon, Nov 1, 2021 at 11:22 AM Muchun Song <songmuchun@...edance.com> wrote:
>>
>> This series can minimize the overhead of struct page for 2MB HugeTLB pages
>> significantly. It further reduces the overhead of struct page by 12.5% for
>> a 2MB HugeTLB compared to the previous approach, which means 2GB per 1TB
>> HugeTLB. It is a nice gain. Comments and reviews are welcome. Thanks.
>>
>
> Hi,
>
> Ping guys. Does anyone have any comments or suggestions
> on this series?
>
> Thanks.
>
I did look over the series earlier. I have no issue with the hugetlb and
vmemmap modifications as they are enhancements to the existing
optimizations. My primary concern is the (small) increased overhead
for the helpers as outlined in your cover letter. Since these helpers
are not limited to hugetlb and used throughout the kernel, I would
really like to get comments from others with a better understanding of
the potential impact.
--
Mike Kravetz
Powered by blists - more mailing lists