From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chandan Babu R <chandan.babu@oracle.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/6] xfs: call xfs_bmap_exact_minlen_extent_alloc from xfs_bmap_btalloc
Date: Wed, 21 Aug 2024 09:04:34 -0700 [thread overview]
Message-ID: <20240821160434.GZ865349@frogsfrogsfrogs> (raw)
In-Reply-To: <20240820170517.528181-6-hch@lst.de>
On Tue, Aug 20, 2024 at 07:04:56PM +0200, Christoph Hellwig wrote:
> xfs_bmap_exact_minlen_extent_alloc duplicates the args setup in
> xfs_bmap_btalloc. Switch to call it from xfs_bmap_btalloc after
> doing the basic setup.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
AFAICT this looks good, though it might be useful to get an ack from
Chandan since he wrote the minlen allocator and might know about any
weird subtleties.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/libxfs/xfs_bmap.c | 61 +++++++++-------------------------------
> 1 file changed, 13 insertions(+), 48 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index 1db9d084a44c47..b5eeaea164ee46 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
> @@ -3471,28 +3471,17 @@ xfs_bmap_process_allocated_extent(
> #ifdef DEBUG
> static int
> xfs_bmap_exact_minlen_extent_alloc(
> - struct xfs_bmalloca *ap)
> + struct xfs_bmalloca *ap,
> + struct xfs_alloc_arg *args)
> {
> - struct xfs_mount *mp = ap->ip->i_mount;
> - struct xfs_alloc_arg args = { .tp = ap->tp, .mp = mp };
> - xfs_fileoff_t orig_offset;
> - xfs_extlen_t orig_length;
> - int error;
> -
> - ASSERT(ap->length);
> -
> if (ap->minlen != 1) {
> - ap->blkno = NULLFSBLOCK;
> - ap->length = 0;
> + args->fsbno = NULLFSBLOCK;
> return 0;
> }
>
> - orig_offset = ap->offset;
> - orig_length = ap->length;
> -
> - args.alloc_minlen_only = 1;
> -
> - xfs_bmap_compute_alignments(ap, &args);
> + args->alloc_minlen_only = 1;
> + args->minlen = args->maxlen = ap->minlen;
> + args->total = ap->total;
>
> /*
> * Unlike the longest extent available in an AG, we don't track
> @@ -3502,33 +3491,9 @@ xfs_bmap_exact_minlen_extent_alloc(
> * we need not be concerned about a drop in performance in
> * "debug only" code paths.
> */
> - ap->blkno = XFS_AGB_TO_FSB(mp, 0, 0);
> + ap->blkno = XFS_AGB_TO_FSB(ap->ip->i_mount, 0, 0);
>
> - args.oinfo = XFS_RMAP_OINFO_SKIP_UPDATE;
> - args.minlen = args.maxlen = ap->minlen;
> - args.total = ap->total;
> -
> - args.alignment = 1;
> - args.minalignslop = 0;
> -
> - args.minleft = ap->minleft;
> - args.wasdel = ap->wasdel;
> - args.resv = XFS_AG_RESV_NONE;
> - args.datatype = ap->datatype;
> -
> - error = xfs_alloc_vextent_first_ag(&args, ap->blkno);
> - if (error)
> - return error;
> -
> - if (args.fsbno != NULLFSBLOCK) {
> - xfs_bmap_process_allocated_extent(ap, &args, orig_offset,
> - orig_length);
> - } else {
> - ap->blkno = NULLFSBLOCK;
> - ap->length = 0;
> - }
> -
> - return 0;
> + return xfs_alloc_vextent_first_ag(args, ap->blkno);
> }
> #else
>
> @@ -3792,8 +3757,11 @@ xfs_bmap_btalloc(
> /* Trim the allocation back to the maximum an AG can fit. */
> args.maxlen = min(ap->length, mp->m_ag_max_usable);
>
> - if ((ap->datatype & XFS_ALLOC_USERDATA) &&
> - xfs_inode_is_filestream(ap->ip))
> + if (unlikely(XFS_TEST_ERROR(false, mp,
> + XFS_ERRTAG_BMAP_ALLOC_MINLEN_EXTENT)))
> + error = xfs_bmap_exact_minlen_extent_alloc(ap, &args);
> + else if ((ap->datatype & XFS_ALLOC_USERDATA) &&
> + xfs_inode_is_filestream(ap->ip))
> error = xfs_bmap_btalloc_filestreams(ap, &args, stripe_align);
> else
> error = xfs_bmap_btalloc_best_length(ap, &args, stripe_align);
> @@ -4208,9 +4176,6 @@ xfs_bmapi_allocate(
> if ((bma->datatype & XFS_ALLOC_USERDATA) &&
> XFS_IS_REALTIME_INODE(bma->ip))
> error = xfs_bmap_rtalloc(bma);
> - else if (unlikely(XFS_TEST_ERROR(false, mp,
> - XFS_ERRTAG_BMAP_ALLOC_MINLEN_EXTENT)))
> - error = xfs_bmap_exact_minlen_extent_alloc(bma);
> else
> error = xfs_bmap_btalloc(bma);
> if (error)
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-08-21 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 17:04 fix a DEBUG-only assert failure in xfs/538 Christoph Hellwig
2024-08-20 17:04 ` [PATCH 1/6] xfs: merge xfs_attr_leaf_try_add into xfs_attr_leaf_addname Christoph Hellwig
2024-08-21 15:52 ` Darrick J. Wong
2024-08-20 17:04 ` [PATCH 2/6] xfs: return bool from xfs_attr3_leaf_add Christoph Hellwig
2024-08-21 15:56 ` Darrick J. Wong
2024-08-20 17:04 ` [PATCH 3/6] xfs: distinguish extra split from real ENOSPC from xfs_attr3_leaf_split Christoph Hellwig
2024-08-21 15:57 ` Darrick J. Wong
2024-08-22 3:40 ` Christoph Hellwig
2024-08-20 17:04 ` [PATCH 4/6] xfs: fold xfs_bmap_alloc_userdata into xfs_bmapi_allocate Christoph Hellwig
2024-08-21 15:59 ` Darrick J. Wong
2024-08-20 17:04 ` [PATCH 5/6] xfs: call xfs_bmap_exact_minlen_extent_alloc from xfs_bmap_btalloc Christoph Hellwig
2024-08-21 8:24 ` Christoph Hellwig
2024-08-21 16:04 ` Darrick J. Wong [this message]
2024-08-20 17:04 ` [PATCH 6/6] xfs: support lowmode allocations in xfs_bmap_exact_minlen_extent_alloc Christoph Hellwig
2024-08-21 16:07 ` Darrick J. Wong
2024-08-22 3:41 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2024-08-24 3:40 fix a DEBUG-only assert failure in xfs/538 v2 Christoph Hellwig
2024-08-24 3:40 ` [PATCH 5/6] xfs: call xfs_bmap_exact_minlen_extent_alloc from xfs_bmap_btalloc Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240821160434.GZ865349@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox