From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Usama Arif <usamaarif642@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
david@redhat.com, linux-mm@kvack.org, hannes@cmpxchg.org,
shakeel.butt@linux.dev, riel@surriel.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
hughd@google.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-team@meta.com
Subject: Re: [RFC] mm: khugepaged: use largest enabled hugepage order for min_free_kbytes
Date: Sat, 7 Jun 2025 09:44:47 +0100 [thread overview]
Message-ID: <83afc94d-707e-4da2-830c-e5fcfd93374d@lucifer.local> (raw)
In-Reply-To: <063273aa-a852-492a-93da-ba5229f544ca@lucifer.local>
OK a 'reviewlet' :P (have to say I like this terminology...)
I see we are already ostensibly 'dynamic' in that hugepage_pmd_enabled() changes
our algorithm.
So my comments about dynamic alterting are probably not quite valid. Are we not
in a weird situation where, with mTHP-only enabled we just use
calculate_min_free_kbytes()??
That probably needs addressing (perhaps separately...)
Lord I hate how we do this (not your fault!)
Rest of review still applicable :>)
Thanks for raising these important issues, while I am raising technical
criticism of the patch, I do very much think you're identifying a real (and
really very significant for those using v. large page table sizes) problem we
need to address one way or another.
Cheers, Lorenzo
next prev parent reply other threads:[~2025-06-07 8:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 14:37 Usama Arif
2025-06-06 15:01 ` Usama Arif
2025-06-06 15:18 ` Zi Yan
2025-06-06 15:38 ` Usama Arif
2025-06-06 16:10 ` Zi Yan
2025-06-07 8:35 ` Lorenzo Stoakes
2025-06-08 0:04 ` Zi Yan
2025-06-09 11:13 ` Usama Arif
2025-06-09 13:19 ` Zi Yan
2025-06-09 14:11 ` Usama Arif
2025-06-09 14:16 ` Lorenzo Stoakes
2025-06-09 14:37 ` Zi Yan
2025-06-09 14:50 ` Lorenzo Stoakes
2025-06-09 15:20 ` Zi Yan
2025-06-09 19:40 ` Lorenzo Stoakes
2025-06-09 19:49 ` Zi Yan
2025-06-09 20:03 ` Usama Arif
2025-06-09 20:24 ` Zi Yan
2025-06-10 10:41 ` Usama Arif
2025-06-10 14:03 ` Lorenzo Stoakes
2025-06-10 14:20 ` Zi Yan
2025-06-10 15:16 ` Usama Arif
2025-06-09 15:32 ` Zi Yan
2025-06-06 17:37 ` David Hildenbrand
2025-06-09 11:34 ` Usama Arif
2025-06-09 13:28 ` Zi Yan
2025-06-07 8:18 ` Lorenzo Stoakes
2025-06-07 8:44 ` Lorenzo Stoakes [this message]
2025-06-09 12:07 ` Usama Arif
2025-06-09 12:12 ` Usama Arif
2025-06-09 14:58 ` Lorenzo Stoakes
2025-06-09 14:57 ` Lorenzo Stoakes
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=83afc94d-707e-4da2-830c-e5fcfd93374d@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kernel-team@meta.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=usamaarif642@gmail.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