Re: [PATCH v2 00/10] btrfs: inode management and memory consumption improvements

[David Sterba <dsterba@suse.cz>]

On Fri, May 10, 2024 at 06:32:48PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Some inode related improvements, to use an xarray to track open inodes per
> root instead of a red black tree, reduce lock contention and use less memory
> per btrfs inode, so now we can fit 4 inodes per 4K page instead of 3.
> More details in the change logs.
> 
> V2: Added two more patches (9/10 and 10/10) to make sure btrfs_inode size
>     is reduced to 1024 bytes when CONFIG_FS_ENCRYPTION and CONFIG_FS_VERITY
>     are set. I wasn't using these configs before, and with them the final
>     size for btrfs_inode was 1032 bytes and not 1016 bytes as I initially
>     had - now the final size is 1024 bytes with those configs enabled.
> 
> Filipe Manana (10):
>   btrfs: use an xarray to track open inodes in a root
>   btrfs: preallocate inodes xarray entry to avoid transaction abort
>   btrfs: reduce nesting and deduplicate error handling at btrfs_iget_path()
>   btrfs: remove inode_lock from struct btrfs_root and use xarray locks
>   btrfs: unify index_cnt and csum_bytes from struct btrfs_inode
>   btrfs: don't allocate file extent tree for non regular files
>   btrfs: remove location key from struct btrfs_inode
>   btrfs: remove objectid from struct btrfs_inode on 64 bits platforms
>   btrfs: rename rb_root member of extent_map_tree from map to root
>   btrfs: use a regular rb_root instead of cached rb_root for extent_map_tree

Reviewed-by: David Sterba <dsterba@suse.com>