From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v4 03/11] xfs: track allocation busy state in allocation cursor
Date: Wed, 18 Sep 2019 11:48:32 -0700 [thread overview]
Message-ID: <20190918184832.GR2229799@magnolia> (raw)
In-Reply-To: <20190916121635.43148-4-bfoster@redhat.com>
On Mon, Sep 16, 2019 at 08:16:27AM -0400, Brian Foster wrote:
> Extend the allocation cursor to track extent busy state for an
> allocation attempt. No functional changes.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
> fs/xfs/libxfs/xfs_alloc.c | 25 ++++++++++++++-----------
> 1 file changed, 14 insertions(+), 11 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c
> index d159377ed603..5c34d4c41761 100644
> --- a/fs/xfs/libxfs/xfs_alloc.c
> +++ b/fs/xfs/libxfs/xfs_alloc.c
> @@ -716,6 +716,8 @@ struct xfs_alloc_cur {
> struct xfs_btree_cur *cnt; /* btree cursors */
> struct xfs_btree_cur *bnolt;
> struct xfs_btree_cur *bnogt;
> + unsigned busy_gen;/* busy state */
Nit: unsigned int here?
'unsigned' without the 'int' looks a little funny to me, but eh
whatever, I guess we do that in the iomap code so:
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> + bool busy;
> };
>
> /*
> @@ -733,6 +735,9 @@ xfs_alloc_cur_setup(
>
> ASSERT(args->alignment == 1 || args->type != XFS_ALLOCTYPE_THIS_BNO);
>
> + acur->busy = false;
> + acur->busy_gen = 0;
> +
> /*
> * Perform an initial cntbt lookup to check for availability of maxlen
> * extents. If this fails, we'll return -ENOSPC to signal the caller to
> @@ -1185,8 +1190,6 @@ xfs_alloc_ag_vextent_near(
> xfs_extlen_t ltlena; /* aligned ... */
> xfs_agblock_t ltnew; /* useful start bno of left side */
> xfs_extlen_t rlen; /* length of returned extent */
> - bool busy;
> - unsigned busy_gen;
> #ifdef DEBUG
> /*
> * Randomly don't execute the first algorithm.
> @@ -1211,7 +1214,6 @@ xfs_alloc_ag_vextent_near(
> ltlen = 0;
> gtlena = 0;
> ltlena = 0;
> - busy = false;
>
> /*
> * Set up cursors and see if there are any free extents as big as
> @@ -1290,8 +1292,8 @@ xfs_alloc_ag_vextent_near(
> if (error)
> goto out;
> XFS_WANT_CORRUPTED_GOTO(args->mp, i == 1, out);
> - busy = xfs_alloc_compute_aligned(args, ltbno, ltlen,
> - <bnoa, <lena, &busy_gen);
> + acur.busy = xfs_alloc_compute_aligned(args, ltbno, ltlen,
> + <bnoa, <lena, &acur.busy_gen);
> if (ltlena < args->minlen)
> continue;
> if (ltbnoa < args->min_agbno || ltbnoa > args->max_agbno)
> @@ -1373,8 +1375,8 @@ xfs_alloc_ag_vextent_near(
> if (error)
> goto out;
> XFS_WANT_CORRUPTED_GOTO(args->mp, i == 1, out);
> - busy |= xfs_alloc_compute_aligned(args, ltbno, ltlen,
> - <bnoa, <lena, &busy_gen);
> + acur.busy |= xfs_alloc_compute_aligned(args, ltbno,
> + ltlen, <bnoa, <lena, &acur.busy_gen);
> if (ltlena >= args->minlen && ltbnoa >= args->min_agbno)
> break;
> error = xfs_btree_decrement(acur.bnolt, 0, &i);
> @@ -1388,8 +1390,8 @@ xfs_alloc_ag_vextent_near(
> if (error)
> goto out;
> XFS_WANT_CORRUPTED_GOTO(args->mp, i == 1, out);
> - busy |= xfs_alloc_compute_aligned(args, gtbno, gtlen,
> - >bnoa, >lena, &busy_gen);
> + acur.busy |= xfs_alloc_compute_aligned(args, gtbno,
> + gtlen, >bnoa, >lena, &acur.busy_gen);
> if (gtlena >= args->minlen && gtbnoa <= args->max_agbno)
> break;
> error = xfs_btree_increment(acur.bnogt, 0, &i);
> @@ -1449,9 +1451,10 @@ xfs_alloc_ag_vextent_near(
> */
> if (!xfs_alloc_cur_active(acur.bnolt) &&
> !xfs_alloc_cur_active(acur.bnogt)) {
> - if (busy) {
> + if (acur.busy) {
> trace_xfs_alloc_near_busy(args);
> - xfs_extent_busy_flush(args->mp, args->pag, busy_gen);
> + xfs_extent_busy_flush(args->mp, args->pag,
> + acur.busy_gen);
> goto restart;
> }
> trace_xfs_alloc_size_neither(args);
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-09-18 18:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 12:16 [PATCH v4 00/11] xfs: rework near mode extent allocation Brian Foster
2019-09-16 12:16 ` [PATCH v4 01/11] xfs: track active state of allocation btree cursors Brian Foster
2019-09-18 18:38 ` Darrick J. Wong
2019-09-19 14:57 ` Brian Foster
2019-09-16 12:16 ` [PATCH v4 02/11] xfs: introduce allocation cursor data structure Brian Foster
2019-09-18 18:46 ` Darrick J. Wong
2019-09-16 12:16 ` [PATCH v4 03/11] xfs: track allocation busy state in allocation cursor Brian Foster
2019-09-18 18:48 ` Darrick J. Wong [this message]
2019-09-19 14:58 ` Brian Foster
2019-09-16 12:16 ` [PATCH v4 04/11] xfs: track best extent from cntbt lastblock scan in alloc cursor Brian Foster
2019-09-18 18:56 ` Darrick J. Wong
2019-09-19 15:00 ` Brian Foster
2019-09-16 12:16 ` [PATCH v4 05/11] xfs: refactor cntbt lastblock scan best extent logic into helper Brian Foster
2019-09-18 19:03 ` Darrick J. Wong
2019-09-19 15:01 ` Brian Foster
2019-09-16 12:16 ` [PATCH v4 06/11] xfs: reuse best extent tracking logic for bnobt scan Brian Foster
2019-09-18 20:43 ` Darrick J. Wong
2019-09-19 15:04 ` Brian Foster
2019-10-04 22:44 ` Darrick J. Wong
2019-10-07 11:08 ` Brian Foster
2019-09-16 12:16 ` [PATCH v4 07/11] xfs: refactor allocation tree fixup code Brian Foster
2019-09-18 20:44 ` Darrick J. Wong
2019-09-16 12:16 ` [PATCH v4 08/11] xfs: refactor and reuse best extent scanning logic Brian Foster
2019-09-18 21:03 ` Darrick J. Wong
2019-09-19 15:04 ` Brian Foster
2019-09-16 12:16 ` [PATCH v4 09/11] xfs: refactor near mode alloc bnobt scan into separate function Brian Foster
2019-09-18 20:55 ` Darrick J. Wong
2019-09-16 12:16 ` [PATCH v4 10/11] xfs: factor out tree fixup logic into helper Brian Foster
2019-09-18 20:56 ` Darrick J. Wong
2019-09-16 12:16 ` [PATCH v4 11/11] xfs: optimize near mode bnobt scans with concurrent cntbt lookups Brian Foster
2019-09-18 21:11 ` Darrick J. Wong
2019-09-19 15:05 ` Brian Foster
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=20190918184832.GR2229799@magnolia \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--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