All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: Zi Yan <ziy@nvidia.com>
Cc: willy@infradead.org, songliubraving@fb.com, clm@fb.com,
	dsterba@suse.com, viro@zeniv.linux.org.uk, brauner@kernel.org,
	jack@suse.cz, akpm@linux-foundation.org, david@kernel.org,
	ljs@kernel.org, baolin.wang@linux.alibaba.com,
	Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
	dev.jain@arm.com, baohua@kernel.org, vbabka@kernel.org,
	rppt@kernel.org, surenb@google.com, mhocko@suse.com,
	shuah@kernel.org, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 7.2 v3 01/12] mm/khugepaged: remove READ_ONLY_THP_FOR_FS check
Date: Thu, 23 Apr 2026 12:47:39 +0800	[thread overview]
Message-ID: <268e0f1e-8575-4ee1-8a0c-48e1b9ae05f0@linux.dev> (raw)
In-Reply-To: <20BA865A-1B69-48DA-BE12-9BFC6EA5A4CE@nvidia.com>



On 2026/4/23 10:51, Zi Yan wrote:
> On 22 Apr 2026, at 22:43, Lance Yang wrote:
> 
>> On Fri, Apr 17, 2026 at 10:44:18PM -0400, Zi Yan wrote:
>>> collapse_file() requires FSes supporting large folio with at least
>>> PMD_ORDER, so replace the READ_ONLY_THP_FOR_FS check with that.
>>> MADV_COLLAPSE ignores shmem huge config, so exclude the check for shmem.
>>>
>>> While at it, replace VM_BUG_ON with VM_WARN_ON_ONCE.
>>>
>>> Add a helper function mapping_pmd_thp_support() for FSes supporting large
>>> folio with at least PMD_ORDER.
>>>
>>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>>> ---
>>> include/linux/pagemap.h | 10 ++++++++++
>>> mm/khugepaged.c         |  5 +++--
>>> 2 files changed, 13 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
>>> index ec442af3f886..c3cb1ec982cd 100644
>>> --- a/include/linux/pagemap.h
>>> +++ b/include/linux/pagemap.h
>>> @@ -524,6 +524,16 @@ static inline bool mapping_large_folio_support(const struct address_space *mappi
>>> 	return mapping_max_folio_order(mapping) > 0;
>>> }
>>>
>>> +static inline bool mapping_pmd_thp_support(const struct address_space *mapping)
>>> +{
>>> +	/* AS_FOLIO_ORDER is only reasonable for pagecache folios */
>>> +	VM_WARN_ONCE((unsigned long)mapping & FOLIO_MAPPING_ANON,
>>> +			"Anonymous mapping always supports PMD THP");
>>
>> Nit: afraid not, at least when running on architectures without PMD leaf
>> entries ...
>>
>> Maybe better to say this helper is only meaningful for pagecache-backed
>> mappings. Anonymous mappings should not reach here.
> 
> Good suggestion. Will fix it.
> 
>>
>>> +
>>> +	return mapping_max_folio_order(mapping) >= PMD_ORDER;
>>> +}
>>> +
>>> +
>>> /* Return the maximum folio size for this pagecache mapping, in bytes. */
>>> static inline size_t mapping_max_folio_size(const struct address_space *mapping)
>>> {
>>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>>> index b8452dbdb043..3eb5d982d3d3 100644
>>> --- a/mm/khugepaged.c
>>> +++ b/mm/khugepaged.c
>>> @@ -1892,8 +1892,9 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
>>> 	int nr_none = 0;
>>> 	bool is_shmem = shmem_file(file);
>>>
>>> -	VM_BUG_ON(!IS_ENABLED(CONFIG_READ_ONLY_THP_FOR_FS) && !is_shmem);
>>> -	VM_BUG_ON(start & (HPAGE_PMD_NR - 1));
>>> +	/* MADV_COLLAPSE ignores shmem huge config, so do not check shmem */
>>> +	VM_WARN_ON_ONCE(!is_shmem && !mapping_pmd_thp_support(mapping));
>>
>> With [1], can we drop !is_shmem here as well? shmem would then always
>> call mapping_set_large_folios(inode->i_mapping):
>>
>> ---8<---
>> diff --git a/mm/shmem.c b/mm/shmem.c
>> index 4ecefe02881d..dafbea53b22d 100644
>> --- a/mm/shmem.c
>> +++ b/mm/shmem.c
>> @@ -3087,10 +3087,7 @@ static struct inode *__shmem_get_inode(struct mnt_idmap *idmap,
>>   	cache_no_acl(inode);
>>   	if (sbinfo->noswap)
>>   		mapping_set_unevictable(inode->i_mapping);
>> -
>> -	/* Don't consider 'deny' for emergencies and 'force' for testing */
>> -	if (sbinfo->huge)
>> -		mapping_set_large_folios(inode->i_mapping);
>> +	mapping_set_large_folios(inode->i_mapping);
>>
>>   	switch (mode & S_IFMT) {
>>   	default:
>> --
>>
>> But we can do that in a follow-up, once the revert lands :)
> 
> Right. That would make this patchset depend on Baolin’s fix. A follow-up
> patch is easier for managing these patches. I will add a TODO in the
> comment, so that we will not forget. Thank you for the suggestion.

OK. With the changes above,

Reviewed-by: Lance Yang <lance.yang@linux.dev>

  reply	other threads:[~2026-04-23  4:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18  2:44 [PATCH 7.2 v3 00/12] Remove read-only THP support for FSes without large folio support Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 01/12] mm/khugepaged: remove READ_ONLY_THP_FOR_FS check Zi Yan
2026-04-20  6:07   ` Baolin Wang
2026-04-23  2:43   ` Lance Yang
2026-04-23  2:51     ` Zi Yan
2026-04-23  4:47       ` Lance Yang [this message]
2026-04-18  2:44 ` [PATCH 7.2 v3 02/12] mm/khugepaged: add folio dirty check after try_to_unmap() Zi Yan
2026-04-20  6:28   ` Baolin Wang
2026-04-23  8:30   ` Lance Yang
2026-04-23 13:14     ` Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 03/12] mm/huge_memory: remove READ_ONLY_THP_FOR_FS from file_thp_enabled() Zi Yan
2026-04-20  6:31   ` Baolin Wang
2026-04-25 12:00   ` Zi Yan
2026-04-27  8:06     ` David Hildenbrand (Arm)
2026-04-27 11:52       ` Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 04/12] mm/khugepaged: remove READ_ONLY_THP_FOR_FS check in hugepage_pmd_enabled() Zi Yan
2026-04-20  6:55   ` Baolin Wang
2026-04-20 14:57     ` Zi Yan
2026-04-21  2:12       ` Baolin Wang
2026-04-18  2:44 ` [PATCH 7.2 v3 05/12] mm: remove READ_ONLY_THP_FOR_FS Kconfig option Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 06/12] mm: fs: remove filemap_nr_thps*() functions and their users Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 07/12] fs: remove nr_thps from struct address_space Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 08/12] mm/huge_memory: remove folio split check for READ_ONLY_THP_FOR_FS Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 09/12] mm/truncate: use folio_split() in truncate_inode_partial_folio() Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 10/12] fs/btrfs: remove a comment referring to READ_ONLY_THP_FOR_FS Zi Yan
2026-04-18  2:44 ` [PATCH 7.2 v3 11/12] selftests/mm: remove READ_ONLY_THP_FOR_FS in khugepaged Zi Yan
2026-04-20  7:56   ` Baolin Wang
2026-04-18  2:44 ` [PATCH 7.2 v3 12/12] selftests/mm: remove READ_ONLY_THP_FOR_FS code from guard-regions Zi Yan
2026-04-18  9:27 ` [PATCH 7.2 v3 00/12] Remove read-only THP support for FSes without large folio support 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=268e0f1e-8575-4ee1-8a0c-48e1b9ae05f0@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=clm@fb.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=dsterba@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=npache@redhat.com \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.