Re: [External] : [PATCH v3 3/4] xfs: calculate AGFL max to support multiple-alloc transactions

[Mark Tinguely <mark.tinguely@oracle.com>]

On 9/2/26 12:40 PM, Brian Foster wrote:
> Rework xfs_alloc_min_freelist() to return an (optional) max value
> along with the historical min freelist value. The max value
> includes an extra level in the btree based calculation to account
> for btree splits in the first allocation of a multi-alloc sequence.
> 
> This value reflects the worst case AGFL requirement that can be
> expected across multiple allocations within a single AG and single
> transaction. For example, consider the case of allocating an inode
> chunk and then an inobt block on inode record insertion.
> 
> While here, rename the need variable in xfs_alloc_fix_freelist() for
> clarity with upcoming changes.
> 
> Note that no callers calculate the max AGFL value as of yet. No
> functional changes in this patch.
> 
> Assisted-by: LLM
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>   fs/xfs/libxfs/xfs_alloc.c  | 35 ++++++++++++++++++++++-------------
>   fs/xfs/libxfs/xfs_alloc.h  |  4 ++--
>   fs/xfs/libxfs/xfs_bmap.c   |  5 +++--
>   fs/xfs/libxfs/xfs_ialloc.c |  4 +++-
>   4 files changed, 30 insertions(+), 18 deletions(-)
> 
looks good

Reviewed-by: Mark Tinguely <mark.tinguely@oracle.com>