Re: [PATCH 0/7] spanning write related cleanup

["Liam R. Howlett" <Liam.Howlett@oracle.com>]

* Wei Yang <richard.weiyang@gmail.com> [241126 20:28]:
> Here is some cleanup related to spanning write.

None of these fix anything, but do fiddle with code that's pretty
critical to the kernel.  Most of the changes will be immeasurable in
change but carry risk to causing subtle changes.

Some are simple removal of returns that aren't used while others change
things because you think they are probably the equivalent.  This seems
like unnecessary chrun at this point.  I'm all for efficient code but
this is getting a bit much, some of these are just preference of what to
use that will already exist in the cpu cache.

I'll get back to you when I dig through them, as some need a deeper look
for sure.

Liam

> 
> Wei Yang (7):
>   maple_tree: not necessary to check ahead if !content
>   maple_tree: validate we won't split on NULL
>   maple_tree: check mid_split only may have
>   maple_tree: the return value of mast_spanning_rebalance() is not used
>   maple_tree: the type of left subtree is already saved in bnode->type
>   maple_tree: always need to update max of new left node
>   maple_tree: only ascend left subtree to get the old node for
>     replacement
> 
>  lib/maple_tree.c | 56 +++++++++++++++++++++++++-----------------------
>  1 file changed, 29 insertions(+), 27 deletions(-)
> 
> -- 
> 2.34.1
>