Re: [Patch v3 3/4] mm/huge_memory: optimize and simplify folio stat update after split

[wang lian <lianux.mm@gmail.com>]

> The loop executed after a successful folio split currently has two
> combined responsibilities:

>  * updating statistics for the new folios
>  * determining the folio for the next split iteration.

> This commit refactors the logic to directly calculate and update folio
> statistics, eliminating the need for the iteration step.

> We can do this because all necessary information is already available:

> * All resulting new folios have the same order, which is @split_order.
>  * The exact number of new folios can be calculated directly using
>    @old_order and @split_order.
>  * The folio for the subsequent split is simply the one containing
>    @split_at.

> By leveraging this knowledge, we can achieve the stat update more
> cleanly and efficiently without the looping logic.

> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> Cc: Zi Yan <ziy@nvidia.com>
> Cc: wang lian <lianux.mm@gmail.com>
---

LGTM.

Reviewed-by: wang lian <lianux.mm@gmail.com>

--
Best Regards,
wang lian