linux-kernel - Re: [RESEND PATCH v7 00/10] Small-sized THP for anonymous memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9379cf06-8f91-41ca-98dc-0f57b486952f@arm.com>
Date:   Fri, 24 Nov 2023 15:23:00 +0000
From:   Ryan Roberts <ryan.roberts@....com>
To:     Matthew Wilcox <willy@...radead.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Yin Fengwei <fengwei.yin@...el.com>,
        David Hildenbrand <david@...hat.com>,
        Yu Zhao <yuzhao@...gle.com>,
        Catalin Marinas <catalin.marinas@....com>,
        Anshuman Khandual <anshuman.khandual@....com>,
        Yang Shi <shy828301@...il.com>,
        "Huang, Ying" <ying.huang@...el.com>, Zi Yan <ziy@...dia.com>,
        Luis Chamberlain <mcgrof@...nel.org>,
        Itaru Kitayama <itaru.kitayama@...il.com>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        John Hubbard <jhubbard@...dia.com>,
        David Rientjes <rientjes@...gle.com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Hugh Dickins <hughd@...gle.com>,
        Kefeng Wang <wangkefeng.wang@...wei.com>, linux-mm@...ck.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH v7 00/10] Small-sized THP for anonymous memory

On 24/11/2023 15:13, Matthew Wilcox wrote:
> On Fri, Nov 24, 2023 at 09:56:37AM +0000, Ryan Roberts wrote:
>> On 23/11/2023 15:59, Matthew Wilcox wrote:
>>> On Wed, Nov 22, 2023 at 04:29:40PM +0000, Ryan Roberts wrote:
>>>> This is v7 of a series to implement small-sized THP for anonymous memory
>>>> (previously called "large anonymous folios"). The objective of this is to
>>>
>>> I'm still against small-sized THP.  We've now got people asking whether
>>> the THP counters should be updated when dealing with large folios that
>>> are smaller than PMD sized.  It's sowing confusion, and we should go
>>> back to large anon folios as a name.
>>
>> I suspect I'm labouring the point here, but I'd like to drill into exactly what
>> you are objecting to. Is it:
>>
>> A) Using the name "small-sized THP" (which is currently only used in the commit
>> logs and a couple of times in the documentation).
> 
> Yes, this is what I'm objecting to.
> 
>> B) Exposing the controls for this feature as an extension to the existing
>> /sys/kernel/mm/transparent_hugepage/* sysfs interface (note the interface never
>> uses the term "small-sized").
> 
> I don't object to the controls being here.  I still wish we didn't need
> an interface to control them at all, but I don't have the time to become
> an expert in anonymous memory and figure out how to make that happen.
> 
>> If A) then this is easily solved by choosing another descriptive name and
>> updating those places. Personally I think it would be best to continue to use
>> "THP" since we are exposing the feature through that interface. Perhaps "large
>> folio THP".
> 
> I think that continues the confusion about the existing interfaces we
> have which count THP (and mean "PMD sized THP").  I'd really prefer the
> term "THP" to unambiguously mean PMD sized THP.  I don't understand why
> you felt the need to move away from Large Anon Folios as a name.
> 

Because the controls are exposed in the sysfs THP directory (and therefore
documented in the transhuge.rst document). It seems odd to refer to them as
large anon folios within the kernel but expose them as as part of the THP interface.

But I'm certainly open to the idea of changing the name in the commit logs and
being careful to distance it from THP transhuge.rst if that's the concensus. I
am opposed to moving/changing the interface though - that's actually what I
thought you were suggesting.