From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yin Fengwei <fengwei.yin@intel.com>, Yu Zhao <yuzhao@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Yang Shi <shy828301@gmail.com>,
"Huang, Ying" <ying.huang@intel.com>, Zi Yan <ziy@nvidia.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Itaru Kitayama <itaru.kitayama@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
John Hubbard <jhubbard@nvidia.com>,
David Rientjes <rientjes@google.com>,
Vlastimil Babka <vbabka@suse.cz>, Hugh Dickins <hughd@google.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v7 00/10] Small-sized THP for anonymous memory
Date: Tue, 28 Nov 2023 09:47:02 +0100 [thread overview]
Message-ID: <a86351ce-60f8-4390-ad97-5d91ca2bc9dd@redhat.com> (raw)
In-Reply-To: <ZWVnBwe8dUO5CgTp@casper.infradead.org>
On 28.11.23 05:05, Matthew Wilcox wrote:
> On Fri, Nov 24, 2023 at 06:34:10PM +0100, David Hildenbrand wrote:
>> On 24.11.23 16:53, Matthew Wilcox wrote:
>>>> * we already have PMD-sized "large anon folios" in THP
>>>
>>> Right, those are already accounted as THP, and that's what users expect.
>>> If we're allocating 1024 x 64kB chunks of memory, the user won't be able
>>> to distinguish that from 32 x 2MB chunks of memory, and yet the
>>> performance profile for some applications will be very different.
>>
>> Very right, and because there will be a difference between 1024 x 64kB, 2048
>> x 32 kB and so forth, we need new memory stats either way.
>>
>> Ryan had some ideas on that, but currently, that's considered future work,
>> just like it likely is for the pagecache as well and needs much more
>> thoughts.
>>
>> Initially, the admin will have to enable all that for anon either way. It
>> all boils down to one memory statistic for anon memory (AnonHugePages)
. >> that's messed-up already.
>
> So we have FileHugePages which is very carefully only PMD-sized large
> folios. If people start making AnonHugePages count non-PMD-sized
> large folios, that's going to be inconsistent.
Right, and that's why we decided to leave these counters alone for now
and rather document that they only apply to PMD-sized THP for historical
reasons.
We'll want new stats either way. Hopefully we'll make it more
future-proof this time.
>
>>> am objecting to the use of the term "small THP" on the grounds of
>>> confusion and linguistic nonsense.
>>
>> Maybe that's the reason why FreeBSD calls them "medium-sized superpages",
>> because "Medium-sized" seems to be more appropriate to express something "in
>> between".
>
> I don't mind "medium" in the name.
>
>> So far I thought the reason was because they focused on 64k only.
>>
>> Never trust a German guy on naming suggestions. John has so far been my
>> naming expert, so I'm hoping he can help.
>>
>> "Sub-pmd-sized THP" is just mouthful. But then, again, this is would just be
>> a temporary name, and in the future THP will just naturally come in multiple
>> sizes (and others here seem to agree on that).
>
> I do not. If we'd come to this fifteen years ago, maybe, but people now
> have an understanding that THPs are necessarily PMD sized.
Well, I still find people being confused about THP vs. hugetlb, so
likely some confusion is unavoidable. :)
In your other mail you write "Perhaps the problem is that people have
turned "THP" into a thing in its own right."
I think that's exactly the case, and I see how that can be confusing
when spelling out THP and reading "small-huge: does it cancel out?".
--
Cheers,
David / dhildenb
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-11-28 8:47 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 16:29 [RESEND PATCH v7 00/10] Small-sized THP for anonymous memory Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 01/10] mm: Allow deferred splitting of arbitrary anon large folios Ryan Roberts
2023-11-27 8:27 ` Barry Song
2023-11-22 16:29 ` [RESEND PATCH v7 02/10] mm: Non-pmd-mappable, large folios for folio_add_new_anon_rmap() Ryan Roberts
2023-11-24 17:40 ` David Hildenbrand
2023-11-27 10:34 ` Ryan Roberts
2023-11-27 4:36 ` Barry Song
2023-11-27 11:30 ` Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 03/10] mm: thp: Introduce per-size thp sysfs interface Ryan Roberts
2023-11-29 3:42 ` John Hubbard
2023-11-29 8:05 ` David Hildenbrand
2023-11-29 11:05 ` Ryan Roberts
2023-11-29 19:40 ` John Hubbard
2023-11-30 12:14 ` Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 04/10] mm: thp: Support allocation of anonymous small-sized THP Ryan Roberts
2023-11-27 3:41 ` Barry Song
2023-11-27 11:28 ` Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 05/10] selftests/mm/kugepaged: Restore thp settings at exit Ryan Roberts
2023-11-23 5:54 ` Alistair Popple
2023-11-22 16:29 ` [RESEND PATCH v7 06/10] selftests/mm: Factor out thp settings management Ryan Roberts
2023-11-23 6:07 ` Alistair Popple
2023-11-27 12:22 ` Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 07/10] selftests/mm: Support small-sized THP interface in thp_settings Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 08/10] selftests/mm/khugepaged: Enlighten for small-sized THP Ryan Roberts
2023-11-22 16:29 ` [RESEND PATCH v7 09/10] selftests/mm/cow: Generalize do_run_with_thp() helper Ryan Roberts
2023-11-24 17:48 ` David Hildenbrand
2023-11-27 10:48 ` Ryan Roberts
2023-11-27 13:59 ` David Hildenbrand
2023-11-27 14:11 ` Ryan Roberts
2023-11-27 14:17 ` David Hildenbrand
2023-11-22 16:29 ` [RESEND PATCH v7 10/10] selftests/mm/cow: Add tests for anonymous small-sized THP Ryan Roberts
2023-11-27 14:02 ` Ryan Roberts
2023-11-27 14:50 ` David Hildenbrand
2023-11-27 14:54 ` Ryan Roberts
2023-11-22 16:32 ` [RESEND PATCH v7 00/10] Small-sized THP for anonymous memory David Hildenbrand
2023-11-23 6:28 ` John Hubbard
2023-11-23 15:59 ` Matthew Wilcox
2023-11-23 16:05 ` David Hildenbrand
2023-11-23 16:18 ` Matthew Wilcox
2023-11-23 16:50 ` David Hildenbrand
2023-11-24 1:14 ` John Hubbard
2023-11-24 1:34 ` Zi Yan
2023-11-24 9:02 ` David Hildenbrand
2023-11-24 9:56 ` Ryan Roberts
2023-11-24 15:13 ` Matthew Wilcox
2023-11-24 15:23 ` Ryan Roberts
2023-11-24 15:25 ` David Hildenbrand
2023-11-24 15:53 ` Matthew Wilcox
2023-11-24 17:34 ` David Hildenbrand
2023-11-27 8:20 ` Alistair Popple
2023-11-27 10:31 ` Ryan Roberts
2023-11-28 2:09 ` John Hubbard
2023-11-28 8:48 ` David Hildenbrand
2023-11-28 12:15 ` Ryan Roberts
2023-11-28 14:09 ` David Hildenbrand
2023-11-28 15:34 ` Ryan Roberts
2023-11-28 16:40 ` David Hildenbrand
2023-11-28 18:39 ` John Hubbard
2023-11-29 9:59 ` Ryan Roberts
2023-11-29 19:46 ` John Hubbard
2023-11-28 4:10 ` Matthew Wilcox
2023-11-28 4:05 ` Matthew Wilcox
2023-11-28 8:47 ` David Hildenbrand [this message]
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=a86351ce-60f8-4390-ad97-5d91ca2bc9dd@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fengwei.yin@intel.com \
--cc=hughd@google.com \
--cc=itaru.kitayama@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=rientjes@google.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).