linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: akpm@linux-foundation.org, hughd@google.com, david@redhat.com,
	lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: shmem: disallow hugepages if the system-wide shmem THP sysfs settings are disabled
Date: Thu, 29 May 2025 22:17:15 -0400	[thread overview]
Message-ID: <D61B9FA2-4EAC-4F0E-AF56-236D37A766BE@nvidia.com> (raw)
In-Reply-To: <bd89651e-0ee0-4819-87da-d3a5db04c5b3@linux.alibaba.com>

On 29 May 2025, at 21:58, Baolin Wang wrote:

> On 2025/5/29 23:21, Zi Yan wrote:
>> On 29 May 2025, at 4:23, Baolin Wang wrote:
>>
>>> The MADV_COLLAPSE will ignore the system-wide shmem THP sysfs settings, which
>>> means that even though we have disabled the shmem THP configuration, MADV_COLLAPSE
>>> will still attempt to collapse into a shmem THP. This violates the rule we have
>>> agreed upon: never means never.
>>>
>>> Then the current strategy is:
>>> For shmem, if none of always, madvise, within_size, and inherit have enabled
>>> PMD-sized mTHP, then MADV_COLLAPSE will be prohibited from collapsing PMD-sized mTHP.
>>>
>>> For tmpfs, if the mount option is set with the 'huge=never' parameter, then
>>> MADV_COLLAPSE will be prohibited from collapsing PMD-sized mTHP.
>>>
>>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>>> ---
>>>   mm/huge_memory.c |  2 +-
>>>   mm/shmem.c       | 12 ++++++------
>>>   2 files changed, 7 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index d3e66136e41a..a8cfa37cae72 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -166,7 +166,7 @@ unsigned long __thp_vma_allowable_orders(struct vm_area_struct *vma,
>>>   	 * own flags.
>>>   	 */
>>>   	if (!in_pf && shmem_file(vma->vm_file))
>>> -		return shmem_allowable_huge_orders(file_inode(vma->vm_file),
>>> +		return orders & shmem_allowable_huge_orders(file_inode(vma->vm_file),
>>>   						   vma, vma->vm_pgoff, 0,
>>>   						   !enforce_sysfs);
>>
>> OK, here orders is checked against allowed orders.
>>
>>>
>>> diff --git a/mm/shmem.c b/mm/shmem.c
>>> index 4b42419ce6b2..4dbb28d85cd9 100644
>>> --- a/mm/shmem.c
>>> +++ b/mm/shmem.c
>>> @@ -613,7 +613,7 @@ static unsigned int shmem_get_orders_within_size(struct inode *inode,
>>>   }
>>>
>>>   static unsigned int shmem_huge_global_enabled(struct inode *inode, pgoff_t index,
>>> -					      loff_t write_end, bool shmem_huge_force,
>>> +					      loff_t write_end,
>>>   					      struct vm_area_struct *vma,
>>>   					      unsigned long vm_flags)
>>>   {
>>> @@ -625,7 +625,7 @@ static unsigned int shmem_huge_global_enabled(struct inode *inode, pgoff_t index
>>>   		return 0;
>>>   	if (shmem_huge == SHMEM_HUGE_DENY)
>>>   		return 0;
>>> -	if (shmem_huge_force || shmem_huge == SHMEM_HUGE_FORCE)
>>> +	if (shmem_huge == SHMEM_HUGE_FORCE)
>>>   		return maybe_pmd_order;
>>
>> shmem_huge is set by sysfs?
>
> Yes, through the '/sys/kernel/mm/transparent_hugepage/shmem_enabled' interface.
>
>>>   	/*
>>> @@ -860,7 +860,7 @@ static unsigned long shmem_unused_huge_shrink(struct shmem_sb_info *sbinfo,
>>>   }
>>>
>>>   static unsigned int shmem_huge_global_enabled(struct inode *inode, pgoff_t index,
>>> -					      loff_t write_end, bool shmem_huge_force,
>>> +					      loff_t write_end,
>>>   					      struct vm_area_struct *vma,
>>>   					      unsigned long vm_flags)
>>>   {
>>> @@ -1261,7 +1261,7 @@ static int shmem_getattr(struct mnt_idmap *idmap,
>>>   			STATX_ATTR_NODUMP);
>>>   	generic_fillattr(idmap, request_mask, inode, stat);
>>>
>>> -	if (shmem_huge_global_enabled(inode, 0, 0, false, NULL, 0))
>>> +	if (shmem_huge_global_enabled(inode, 0, 0, NULL, 0))
>>>   		stat->blksize = HPAGE_PMD_SIZE;
>>>
>>>   	if (request_mask & STATX_BTIME) {
>>> @@ -1768,7 +1768,7 @@ unsigned long shmem_allowable_huge_orders(struct inode *inode,
>>>   		return 0;
>>>
>>>   	global_orders = shmem_huge_global_enabled(inode, index, write_end,
>>> -						  shmem_huge_force, vma, vm_flags);
>>> +						  vma, vm_flags);
>>>   	/* Tmpfs huge pages allocation */
>>>   	if (!vma || !vma_is_anon_shmem(vma))
>>>   		return global_orders;
>>> @@ -1790,7 +1790,7 @@ unsigned long shmem_allowable_huge_orders(struct inode *inode,
>>>   	/* Allow mTHP that will be fully within i_size. */
>>>   	mask |= shmem_get_orders_within_size(inode, within_size_orders, index, 0);
>>>
>>> -	if (vm_flags & VM_HUGEPAGE)
>>> +	if (shmem_huge_force || (vm_flags & VM_HUGEPAGE))
>>>   		mask |= READ_ONCE(huge_shmem_orders_madvise);
>>>
>>>   	if (global_orders > 0)
>>> -- 
>>> 2.43.5
>>
>> shmem_huge_force comes from !enforce_sysfs in __thp_vma_allowable_orders().
>> Do you know when sysfs is not enforced and why?
>
> IIUC, shmem_huge_force will only be set during MADV_COLLAPSE. Originally, MADV_COLLAPSE was intended to ignore the system-wide THP sysfs settings. However, if all system-wide shmem THP settings are disabled, we should not allow MADV_COLLAPSE to collapse a THP. This is the issue this patchset aims to fix. Thanks for the review.

Got it. If we want to enforce sysfs, why not just get rid of TVA_ENFORCE_SYSFS
and make everyone follow sysfs?

Best Regards,
Yan, Zi


  reply	other threads:[~2025-05-30  2:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29  8:23 [PATCH 0/2] fix MADV_COLLAPSE issue if THP " 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 [this message]
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
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=D61B9FA2-4EAC-4F0E-AF56-236D37A766BE@nvidia.com \
    --to=ziy@nvidia.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=lorenzo.stoakes@oracle.com \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.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