Re: [PATCH] mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported()

Wei Yang
2025-11-05T02:44:08Z

On Tue, Nov 04, 2025 at 09:14:31PM -0500, Zi Yan wrote:
>On 4 Nov 2025, at 2:53, Wei Yang wrote:
[...]
>>>>>
>>>>
>>>> How about this one:
>>>>
>>>> swapcache folio could only be split to order 0
>>>
>>> This looks good.
>>>
>>>>
>>>> For non-uniform split or uniform split targeting a large folio, return
>>>> false.
>>>
>>> You are just describing the code.
>>>
>>> non-uniform split creates after-split folios with orders from
>>> folio_order(folio) - 1 to new_order, making it not suitable for any swapcache
>>> folio split. Only uniform split to order-0 can be used here.
>>>
>>
>> Below is the updated version:
>>
>> swapcache folio could only be split to order 0
>>
>> non-uniform split creates after-split folios with orders from
>> folio_order(folio) - 1 to new_order, making it not suitable for any
>> swapcache folio split. Only uniform split to order-0 can be used here.
>
>LGTM.
>
>Thank you for updating the comments. Looking forward to your updated patch.

Thanks for you time and patience, will prepare a new version.

--
Wei Yang
Help you, Help me