linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: akpm@linux-foundation.org, hughd@google.com, david@redhat.com,
	Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
	dev.jain@arm.com, ziy@nvidia.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] fix MADV_COLLAPSE issue if THP settings are disabled
Date: Wed, 11 Jun 2025 15:05:40 +0800	[thread overview]
Message-ID: <a23c547b-d775-4d8d-a34f-b9b0f200e7f3@linux.alibaba.com> (raw)
In-Reply-To: <2e30bffd-bda5-4f83-b88d-c51940651a49@lucifer.local>



On 2025/6/7 20:28, Lorenzo Stoakes wrote:
> Before I get into technical criticism, to be clear - thank you very much
> for doing this :) I'm just getting into details as to the implementation,
> but am a fan of this change and consider it important.
> 
> On Thu, Jun 05, 2025 at 04:00:57PM +0800, Baolin Wang wrote:
>> As we discussed in the previous thread [1], the MADV_COLLAPSE will ignore
>> the system-wide anon/shmem THP sysfs settings, which means that even though
>> we have disabled the anon/shmem THP configuration, MADV_COLLAPSE will still
>> attempt to collapse into a anon/shmem THP. This violates the rule we have
>> agreed upon: never means never. This patch set will address this issue.
> 
> Hm this cover letter could be expanded upon quite a bit - you are doing a
> lot here and it's not only MADV_COLLAPSE, more a general change.
> 
> I'd mention that, even when TVA_ENFORCE_SYSFS is not set, callers checking
> THP order validity will not be able to specify THP orders that are either
> specifically marked as 'never' or set to 'inherit' and the global hugepage
> mode is 'never'.
> 
> Then say something like 'importantly, this changes alters the madvise(...,
> MADV_COLLAPSE) call, which previously would collapse ranges into huge pages
> even if THP was set to never. This corrects this behaviour'.
> 
> I suspect you are unable to write sensible tests here given the need to
> manipulate sysfs (though perhaps worth quickly looking at
> tools/testing/selftests/mm/khugepaged.c, transhuge-stress.c, run_vmtests.sh
> to see), but it'd be at least useful for you to give details here of how
> you have tested this and ensured it functions correctly.
> 
> It might also be worth giving a quick justification, i.e. 'system
> administrators who disabled THP everywhere must indeed very much not want
> THP to be used for whatever reason - having individual programs being able
> to quietly override this is very surprising and likely to cause headaches
> for those who desire this not to happen on their systems'.
> 

Ah, missed this comment. Good suggestion, I will update the cover 
letter. Thanks.


  reply	other threads:[~2025-06-11  7:05 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  8:00 Baolin Wang
2025-06-05  8:00 ` [PATCH v2 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs " Baolin Wang
2025-06-06 16:49   ` Dev Jain
2025-06-06 18:47     ` Dev Jain
2025-06-09  5:57       ` Baolin Wang
2025-06-07 11:55   ` Lorenzo Stoakes
2025-06-07 12:21     ` Lorenzo Stoakes
2025-06-09  6:18       ` Baolin Wang
2025-06-09 15:12         ` Lorenzo Stoakes
2025-06-09  6:10     ` Baolin Wang
2025-06-09 15:17       ` Lorenzo Stoakes
2025-06-11  6:59         ` Baolin Wang
2025-06-08 18:37   ` Nico Pache
2025-06-09  6:36     ` Baolin Wang
2025-06-11 12:34   ` David Hildenbrand
2025-06-12  7:51     ` Baolin Wang
2025-06-12  8:46       ` Dev Jain
2025-06-12  8:52         ` David Hildenbrand
2025-06-12  8:51       ` David Hildenbrand
2025-06-12 12:45         ` Baolin Wang
2025-06-12 13:05           ` David Hildenbrand
2025-06-12 13:25             ` Baolin Wang
2025-06-12 13:40               ` Baolin Wang
2025-06-12 13:27             ` Lorenzo Stoakes
2025-06-12 13:29               ` Lorenzo Stoakes
2025-06-12 14:13                 ` Baolin Wang
2025-06-12 14:16                   ` David Hildenbrand
2025-06-12 14:20                   ` Lorenzo Stoakes
2025-06-12 14:09               ` David Hildenbrand
2025-06-12 14:49                 ` Lorenzo Stoakes
2025-06-13  2:07                   ` Baolin Wang
2025-06-13  5:18                     ` Lorenzo Stoakes
2025-06-12 13:07         ` Lorenzo Stoakes
2025-06-12 13:13           ` David Hildenbrand
2025-06-12 13:31             ` Lorenzo Stoakes
2025-06-05  8:00 ` [PATCH v2 2/2] mm: shmem: disallow hugepages if the system-wide shmem " Baolin Wang
2025-06-07 12:14   ` Lorenzo Stoakes
2025-06-07 12:17     ` Lorenzo Stoakes
2025-06-09  6:34       ` Baolin Wang
2025-06-09 19:30         ` Lorenzo Stoakes
2025-06-09  6:31     ` Baolin Wang
2025-06-09 15:33       ` Lorenzo Stoakes
2025-06-11  7:02         ` Baolin Wang
2025-06-07 12:28 ` [PATCH v2 0/2] fix MADV_COLLAPSE issue if THP " Lorenzo Stoakes
2025-06-11  7:05   ` Baolin Wang [this message]
2025-06-13 14:23 ` Usama Arif
2025-06-13 14:29   ` Lorenzo Stoakes
2025-06-13 14:39     ` Usama Arif
2025-06-13 14:42       ` 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=a23c547b-d775-4d8d-a34f-b9b0f200e7f3@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --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