From: David Hildenbrand <david@redhat.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
John Hubbard <jhubbard@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
Yang Shi <shy828301@gmail.com>,
"Yin, Fengwei" <fengwei.yin@intel.com>,
Yu Zhao <yuzhao@google.com>, Zi Yan <ziy@nvidia.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: ANON_LARGE_FOLIOS meeting follow-up & refined proposal
Date: Tue, 26 Sep 2023 20:31:43 +0200 [thread overview]
Message-ID: <5fa4aa95-6982-7879-e067-69fdb8b76d01@redhat.com> (raw)
In-Reply-To: <92937776-1e16-47e5-bef9-4c1a04bc98c0@arm.com>
On 25.09.23 10:51, Ryan Roberts wrote:
> On 23/09/2023 01:33, John Hubbard wrote:
>> On 9/22/23 08:48, Ryan Roberts wrote:
>> ...
>>> I never had any feedback on the below; I'm not sure if that means everyone is
>>> happy or that nobody read it??
>>
>> One can never really know: zero or more people read it, and of those, no
>> one hated it enough to send out a quick NAK. So that's a *possible*,
>> lukewarm endorsement of sorts. Success! :)
>
> You really know how to fill a guy with confidence! ;-)
>
>>
>> ...
>>
>>> BUT I've had yet another idea on the controls front, which would enable exposing
>>> this to user space as an extension to transparent_hugepage, while continuing to
>>> support THP as is and also be able to control THP and ALF (anon large folio)
>>
>> The new ALF / ANON_LARGE_FOLIO naming looks good to me. The grep aspect
>> is a nice touch.
>
> Well if we go the route of the newest proposal, then I guess the naming is less
> important, because it all attaches to transparent_hugepage.
I agree that ALF is better. But having something under "THP", that is
not THP and not accounted as THP ... I don't quite like it (although,
before we discussed that approach in the past, I did like it).
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-09-26 18:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 8:16 Ryan Roberts
2023-09-22 15:48 ` Ryan Roberts
2023-09-23 0:33 ` John Hubbard
2023-09-25 8:51 ` Ryan Roberts
2023-09-26 18:31 ` David Hildenbrand [this message]
2023-09-27 7:23 ` Ryan Roberts
2023-09-27 15:32 ` David Hildenbrand
2023-09-27 19:04 ` Ryan Roberts
2023-10-02 12:58 ` David Hildenbrand
2023-10-05 7:37 ` Ryan Roberts
[not found] ` <c60321ef-8596-8fa0-7367-f43e69e1d894@redhat.com>
2023-10-05 9:46 ` Ryan Roberts
2023-10-06 11:53 ` David Hildenbrand
2023-09-26 18:34 ` David Hildenbrand
2023-09-26 8:13 ` Kirill A. Shutemov
2023-09-26 18:29 ` David Hildenbrand
2023-09-26 18:26 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fa4aa95-6982-7879-e067-69fdb8b76d01@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fengwei.yin@intel.com \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox