linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Hugh Dickins <hughd@google.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	akpm@linux-foundation.org, ziy@nvidia.com,
	Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
	dev.jain@arm.com, baohua@kernel.org, zokeefe@google.com,
	shy828301@gmail.com, usamaarif642@gmail.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] fix MADV_COLLAPSE issue if THP settings are disabled
Date: Wed, 25 Jun 2025 08:42:16 +0100	[thread overview]
Message-ID: <3b6db0c3-aef3-4a21-a154-6aafd639dbc7@lucifer.local> (raw)
In-Reply-To: <8691d74b-67ee-4e26-81ac-f6bf1725361e@redhat.com>

On Wed, Jun 25, 2025 at 09:36:53AM +0200, David Hildenbrand wrote:
> On 25.06.25 09:30, Lorenzo Stoakes wrote:
> > I _guarantee_ you that's what nearly everybody except a handful of people will
> > expect.
>
> I know, See my other mail, the problem is rather if there is no somebody
> relying on never+MADV_COLLAPSE from doing the MADV_COLLAPSE-documented
> thing.
>
> It's a mess.

Well now we have an almost philosophical debate - we have different sets of
users, 99% of whom believe the uAPI is X, and 1% of whom believe it is Y.

Now what is the uAPI? What is 'breaking userspace'? :)

Temptation to cc Linus here ;)

>
> (I have the suspicion that Hugh might know of such a user :) )

Speak up Hugh we're all friends here haha ;)

I mean if this really is a problem for real users then I'll concede the point.

Let me reply on other thread...

> > I really really dislike this. 'Deny' is weaker than 'never'. And now we have to
> > add even more complexity to the thing.
>
> See my other mail, for shmem_enabled "deny" is stronger than "never", lol.

OK so we're past the throwing up stage, can I cry now? :P


  reply	other threads:[~2025-06-25  7:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  1:40 Baolin Wang
2025-06-25  1:40 ` [PATCH v4 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs " Baolin Wang
2025-06-25  4:34   ` Dev Jain
2025-06-25  1:40 ` [PATCH v4 2/2] mm: shmem: disallow hugepages if the system-wide shmem " Baolin Wang
2025-06-25  5:53 ` [PATCH v4 0/2] fix MADV_COLLAPSE issue if THP " Hugh Dickins
2025-06-25  6:05   ` Dev Jain
2025-06-25  6:26   ` Baolin Wang
2025-06-25  6:49     ` Dev Jain
2025-06-25  6:55       ` Baolin Wang
2025-06-25  7:20   ` Lorenzo Stoakes
2025-06-25  7:34     ` David Hildenbrand
2025-06-25  7:55       ` Lorenzo Stoakes
2025-06-25  8:12         ` Lorenzo Stoakes
2025-06-25  8:24           ` David Hildenbrand
2025-06-25  8:37             ` Lorenzo Stoakes
2025-06-25  8:52               ` Baolin Wang
2025-06-25  9:31                 ` Lorenzo Stoakes
2025-06-25 10:02                   ` Baolin Wang
2025-06-25 10:07                     ` David Hildenbrand
2025-06-25 10:15                       ` Lorenzo Stoakes
2025-06-25 10:29                         ` David Hildenbrand
2025-06-25  8:53               ` David Hildenbrand
2025-06-25 11:03       ` Usama Arif
2025-06-25 11:09         ` David Hildenbrand
2025-06-26  3:49           ` Hugh Dickins
2025-06-25  7:23   ` David Hildenbrand
2025-06-25  7:30     ` Lorenzo Stoakes
2025-06-25  7:36       ` David Hildenbrand
2025-06-25  7:42         ` Lorenzo Stoakes [this message]
2025-06-25  7:49           ` David Hildenbrand
2025-06-25  8:16             ` David Hildenbrand
2025-06-25  8:22               ` Lorenzo Stoakes
2025-06-25  8:40                 ` David Hildenbrand
2025-06-25  8:45                   ` Lorenzo Stoakes
2025-06-25 21:51         ` Hugh Dickins
2025-07-09 12:36 ` Lorenzo Stoakes
2025-07-10  1:58   ` Baolin Wang

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=3b6db0c3-aef3-4a21-a154-6aafd639dbc7@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --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=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=usamaarif642@gmail.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