[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yrm/+UoOtDY7G5bi@casper.infradead.org>
Date: Mon, 27 Jun 2022 15:34:33 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Anshuman Khandual <anshuman.khandual@....com>
Cc: Qi Zheng <zhengqi.arch@...edance.com>, mike.kravetz@...cle.com,
songmuchun@...edance.com, akpm@...ux-foundation.org,
catalin.marinas@....com, will@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] mm: hugetlb: kill set_huge_swap_pte_at()
On Mon, Jun 27, 2022 at 01:05:00PM +0530, Anshuman Khandual wrote:
> > For the swap entry of hugetlb, we need to remember that we should
> > call set_huge_swap_pte_at() instead of set_huge_pte_at() every
>
> Which is intuitive, so what is the problem ?
The problem is that HugeTLB is DIFFERENT from the rest of the VM.
This has a huge cost in programmer time, which is infinitely more
valuable than the cycle shaving you're quibbling over. We should take
any and every opportunity to make huge pages work the same way as THP
and order-0 pages.
Powered by blists - more mailing lists