From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
akpm@linux-foundation.org, hughd@google.com,
Liam.Howlett@oracle.com, npache@redhat.com, dev.jain@arm.com,
ziy@nvidia.com, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] fix MADV_COLLAPSE issue if THP settings are disabled
Date: Fri, 30 May 2025 10:34:36 +0100 [thread overview]
Message-ID: <60a81a60-b7da-4439-b177-9d1bca82828d@lucifer.local> (raw)
In-Reply-To: <6caefe0b-c909-4692-a006-7f8b9c0299a6@redhat.com>
On Fri, May 30, 2025 at 11:16:51AM +0200, David Hildenbrand wrote:
[snip]
> It kind-of contradicts the linked
> Documentation/admin-guide/mm/transhuge.rst, where we have this *beautiful*
> comment
>
> "Transparent Hugepage Support for anonymous memory can be entirely disable
> (mostly for debugging purposes".
>
> I mean, "entirely" is also pretty clear to me.
>
> I would assume that the man page of MADV_COLLAPSE should have talked about
> ignoring *khugepaged* toggles (max_ptes_none ...), at least that's what I
> recall from the discussions back then.
Sorry I don't want to turn this stuff into too much of a mega-thread but
just a small comment here - I think we should go and update the
documentation/man pages to be clearer and consistent.
There is enough confusion around this as it is...
>
> --
> Cheers,
>
> David / dhildenb
>
next prev parent reply other threads:[~2025-05-30 9:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 8:23 Baolin Wang
2025-05-29 8:23 ` [PATCH 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs " Baolin Wang
2025-05-29 15:10 ` Zi Yan
2025-05-30 1:51 ` Baolin Wang
2025-05-30 2:04 ` Zi Yan
2025-05-30 2:21 ` Baolin Wang
2025-05-30 2:22 ` Zi Yan
2025-05-29 8:23 ` [PATCH 2/2] mm: shmem: disallow hugepages if the system-wide shmem " Baolin Wang
2025-05-29 15:21 ` Zi Yan
2025-05-30 1:58 ` Baolin Wang
2025-05-30 2:17 ` Zi Yan
2025-05-30 2:32 ` Baolin Wang
2025-05-30 2:35 ` Zi Yan
2025-05-30 2:39 ` Baolin Wang
2025-05-30 8:04 ` [PATCH 0/2] fix MADV_COLLAPSE issue if THP " Ryan Roberts
2025-05-30 8:44 ` David Hildenbrand
2025-05-30 8:47 ` Lorenzo Stoakes
2025-05-30 8:52 ` David Hildenbrand
2025-05-30 9:07 ` Ryan Roberts
2025-05-30 9:14 ` Lorenzo Stoakes
2025-05-30 8:59 ` Ryan Roberts
2025-05-30 9:10 ` David Hildenbrand
2025-05-30 9:16 ` David Hildenbrand
2025-05-30 9:34 ` Lorenzo Stoakes [this message]
2025-05-30 9:52 ` Baolin Wang
2025-05-30 10:45 ` 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=60a81a60-b7da-4439-b177-9d1bca82828d@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=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.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