From: Nico Pache <npache@redhat.com>
To: Klara Modin <klarasmodin@gmail.com>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
rientjes@google.com, hannes@cmpxchg.org,
lorenzo.stoakes@oracle.com, rdunlap@infradead.org,
mhocko@suse.com, Liam.Howlett@oracle.com, zokeefe@google.com,
surenb@google.com, jglisse@google.com, cl@gentwo.org,
jack@suse.cz, dave.hansen@linux.intel.com, will@kernel.org,
tiwai@suse.de, catalin.marinas@arm.com,
anshuman.khandual@arm.com, dev.jain@arm.com, raquini@redhat.com,
aarcange@redhat.com, kirill.shutemov@linux.intel.com,
yang@os.amperecomputing.com, thomas.hellstrom@linux.intel.com,
vishal.moola@gmail.com, sunnanyong@huawei.com,
usamaarif642@gmail.com, wangkefeng.wang@huawei.com,
ziy@nvidia.com, shuah@kernel.org, peterx@redhat.com,
willy@infradead.org, ryan.roberts@arm.com,
baolin.wang@linux.alibaba.com, baohua@kernel.org,
david@redhat.com, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, rostedt@goodmis.org, corbet@lwn.net,
akpm@linux-foundation.org
Subject: Re: [PATCH v6 1/4] mm: defer THP insertion to khugepaged
Date: Tue, 17 Jun 2025 11:52:26 -0600 [thread overview]
Message-ID: <CAA1CXcDgu3bT-aUEXoFrVVYaTy_rAbdNmwMhzrkwb0+VxQM47w@mail.gmail.com> (raw)
In-Reply-To: <fcd3phzewpgzghrzse3stxi7jz7b6l5uwnhqtswcfnqvuvktip@apqh2achkutn>
On Sat, Jun 14, 2025 at 5:25 AM Klara Modin <klarasmodin@gmail.com> wrote:
>
> Hi,
>
> On 2025-05-14 21:38:54 -0600, Nico Pache wrote:
> > setting /transparent_hugepages/enabled=always allows applications
> > to benefit from THPs without having to madvise. However, the page fault
> > handler takes very few considerations to decide weather or not to actually
> > use a THP. This can lead to a lot of wasted memory. khugepaged only
> > operates on memory that was either allocated with enabled=always or
> > MADV_HUGEPAGE.
> >
> > Introduce the ability to set enabled=defer, which will prevent THPs from
> > being allocated by the page fault handler unless madvise is set,
> > leaving it up to khugepaged to decide which allocations will collapse to a
> > THP. This should allow applications to benefits from THPs, while curbing
> > some of the memory waste.
> >
> > Acked-by: Zi Yan <ziy@nvidia.com>
> > Co-developed-by: Rafael Aquini <raquini@redhat.com>
> > Signed-off-by: Rafael Aquini <raquini@redhat.com>
> > Signed-off-by: Nico Pache <npache@redhat.com>
>
> ...
>
> > @@ -315,13 +318,20 @@ static ssize_t enabled_store(struct kobject *kobj,
> >
> > if (sysfs_streq(buf, "always")) {
> > clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG, &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG, &transparent_hugepage_flags);
> > set_bit(TRANSPARENT_HUGEPAGE_FLAG, &transparent_hugepage_flags);
> > + } else if (sysfs_streq(buf, "defer")) {
> > + clear_bit(TRANSPARENT_HUGEPAGE_FLAG, &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG, &transparent_hugepage_flags);
> > + set_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG, &transparent_hugepage_flags);
> > } else if (sysfs_streq(buf, "madvise")) {
> > clear_bit(TRANSPARENT_HUGEPAGE_FLAG, &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG, &transparent_hugepage_flags);
> > set_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG, &transparent_hugepage_flags);
> > } else if (sysfs_streq(buf, "never")) {
> > clear_bit(TRANSPARENT_HUGEPAGE_FLAG, &transparent_hugepage_flags);
> > clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG, &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG, &transparent_hugepage_flags);
> > } else
> > ret = -EINVAL;
> >
> > @@ -954,18 +964,31 @@ static int __init setup_transparent_hugepage(char *str)
> > &transparent_hugepage_flags);
> > clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG,
> > &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG,
> > + &transparent_hugepage_flags);
> > ret = 1;
> > + } else if (!strcmp(str, "defer")) {
> > + clear_bit(TRANSPARENT_HUGEPAGE_FLAG,
> > + &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG,
> > + &transparent_hugepage_flags);
> > + set_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG,
> > + &transparent_hugepage_flags);
>
> There should probably be a corresponding
> ret = 1;
> here. Otherwise the cannot parse message will displayed even if defer
> was set.
Thanks Klara-- I will make sure to add it on the next version!
>
> > } else if (!strcmp(str, "madvise")) {
> > clear_bit(TRANSPARENT_HUGEPAGE_FLAG,
> > &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG,
> > + &transparent_hugepage_flags);
> > set_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG,
> > - &transparent_hugepage_flags);
> > + &transparent_hugepage_flags);
> > ret = 1;
> > } else if (!strcmp(str, "never")) {
> > clear_bit(TRANSPARENT_HUGEPAGE_FLAG,
> > &transparent_hugepage_flags);
> > clear_bit(TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG,
> > &transparent_hugepage_flags);
> > + clear_bit(TRANSPARENT_HUGEPAGE_DEFER_PF_FLAG,
> > + &transparent_hugepage_flags);
> > ret = 1;
> > }
> > out:
> > --
> > 2.49.0
> >
>
> Regards,
> Klara Modin
>
next prev parent reply other threads:[~2025-06-17 17:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 3:38 [PATCH v6 0/4] mm: introduce THP deferred setting Nico Pache
2025-05-15 3:38 ` [PATCH v6 1/4] mm: defer THP insertion to khugepaged Nico Pache
2025-05-20 7:43 ` Yafang Shao
2025-06-14 11:25 ` Klara Modin
2025-06-17 17:52 ` Nico Pache [this message]
2025-05-15 3:38 ` [PATCH v6 2/4] mm: document (m)THP defer usage Nico Pache
2025-05-15 3:38 ` [PATCH v6 3/4] khugepaged: add defer option to mTHP options Nico Pache
2025-05-15 3:38 ` [PATCH v6 4/4] selftests: mm: add defer to thp setting parser Nico Pache
2025-05-20 9:24 ` [PATCH v6 0/4] mm: introduce THP deferred setting Yafang Shao
2025-05-21 10:19 ` Nico Pache
2025-05-21 11:35 ` Yafang Shao
2025-05-20 9:42 ` Lorenzo Stoakes
2025-05-21 10:41 ` Nico Pache
2025-05-21 11:24 ` Lorenzo Stoakes
2025-05-21 11:46 ` David Hildenbrand
2025-05-21 12:00 ` Lorenzo Stoakes
2025-05-21 12:24 ` David Hildenbrand
2025-05-21 12:33 ` Lorenzo Stoakes
2025-05-21 12:40 ` David Hildenbrand
2025-05-29 4:26 ` Nico Pache
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=CAA1CXcDgu3bT-aUEXoFrVVYaTy_rAbdNmwMhzrkwb0+VxQM47w@mail.gmail.com \
--to=npache@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jglisse@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=klarasmodin@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=raquini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tiwai@suse.de \
--cc=usamaarif642@gmail.com \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=ziy@nvidia.com \
--cc=zokeefe@google.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