Re: [Patch v2 2/2] mm/huge_memory: Optimize and simplify __split_unmapped_folio() logic

[Wei Yang <richard.weiyang@gmail.com>]

On Thu, Oct 16, 2025 at 12:46:13AM +0000, Wei Yang wrote:
>Existing __split_unmapped_folio() code splits the given folio and update
>stats, but it is complicated to understand.
>
>After simplification, __split_unmapped_folio() directly calculate and
>update the folio statistics upon a successful split:
>
>* All resulting folios are @split_order.
>
>* The number of new folios are calculated directly from @old_order
>  and @split_order.
>
>* The folio for the next split is identified as the one containing
>  @split_at.
>
>* An xas_try_split() error is returned directly without worrying
>  about stats updates.

@Andrew

From David and Zi comment, there is little change in change log.

Would you mind helping update it? Below is the updated version.

---

    Existing __split_unmapped_folio() code splits the given folio and
    updates stats, but it is complicated to understand.
    
    After simplification, __split_unmapped_folio() directly calculates and
    updates the folio statistics upon a successful split:
    
    * All resulting folios are @split_order.
    
    * The number of new folios are calculated directly from @old_order and
      @split_order.
    
    * The folio for the next split is identified as the one containing
      @split_at.
    
    * Stats fixup is no longer needed for an xas_try_split() error,
      since since we now update the stats only after a successful split.

-- 
Wei Yang
Help you, Help me