From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 15/20] xfs: add an extent to the rmap btree
Date: Thu, 25 Jun 2015 12:41:23 -0400 [thread overview]
Message-ID: <20150625164123.GD36162@bfoster.bfoster> (raw)
In-Reply-To: <1433311497-10245-16-git-send-email-david@fromorbit.com>
On Wed, Jun 03, 2015 at 04:04:52PM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Now all the btree, free space and transaction infrastructure is in
> place, we can finally add the code to insert reverse mappings to the
> rmap btree. Freeing will be done in a spearate patch, so just the
> addition operation can be focussed on here.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/libxfs/xfs_rmap.c | 139 ++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 138 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/libxfs/xfs_rmap.c b/fs/xfs/libxfs/xfs_rmap.c
> index 38a92a1..c1e5d23 100644
> --- a/fs/xfs/libxfs/xfs_rmap.c
> +++ b/fs/xfs/libxfs/xfs_rmap.c
> @@ -120,6 +120,18 @@ out_error:
> return error;
> }
>
> +/*
> + * When we allocate a new block, the first thing we do is add a reference to the
> + * extent in the rmap btree. This takes the form of a [agbno, length, owner]
> + * record. Newly inserted extents should never overlap with an existing extent
> + * in the rmap btree. Hence the insertion is a relatively trivial exercise,
> + * involving checking for adjacent records and merging if the new extent is
> + * contiguous and has the same owner.
> + *
> + * Note that we have no MAXEXTLEN limits here when merging as the length in the
> + * record has the full 32 bits available and hence a single record can track the
> + * entire space in the AG.
> + */
> int
> xfs_rmap_alloc(
> struct xfs_trans *tp,
> @@ -130,18 +142,143 @@ xfs_rmap_alloc(
> uint64_t owner)
> {
> struct xfs_mount *mp = tp->t_mountp;
> + struct xfs_btree_cur *cur;
> + struct xfs_rmap_irec ltrec;
> + struct xfs_rmap_irec gtrec;
> + int have_gt;
> int error = 0;
> + int i;
>
> if (!xfs_sb_version_hasrmapbt(&mp->m_sb))
> return 0;
>
> trace_xfs_rmap_alloc_extent(mp, agno, bno, len, owner);
> - if (1)
> + cur = xfs_rmapbt_init_cursor(mp, tp, agbp, agno);
> +
> + /*
> + * For the initial lookup, look for and exact match or the left-adjacent
> + * record for our insertion point. This will also give us the record for
> + * start block contiguity tests.
> + */
> + error = xfs_rmap_lookup_le(cur, bno, len, owner, &i);
> + if (error)
> + goto out_error;
> + XFS_WANT_CORRUPTED_GOTO(mp, i == 1, out_error);
> +
Are we intentionally relying on the fact that a left record will always
exist due to the static metadata blocks that start the AG? If so, I'd
just suggest to note that in the comment above.
Brian
> + error = xfs_rmap_get_rec(cur, <rec, &i);
> + if (error)
> goto out_error;
> + XFS_WANT_CORRUPTED_GOTO(mp, i == 1, out_error);
> + //printk("rmalloc ag %d bno 0x%x/0x%x/0x%llx, ltrec 0x%x/0x%x/0x%llx\n",
> + // agno, bno, len, owner, ltrec.rm_startblock,
> + // ltrec.rm_blockcount, ltrec.rm_owner);
> +
> + XFS_WANT_CORRUPTED_GOTO(mp,
> + ltrec.rm_startblock + ltrec.rm_blockcount <= bno, out_error);
> +
> + /*
> + * Increment the cursor to see if we have a right-adjacent record to our
> + * insertion point. This will give us the record for end block
> + * contiguity tests.
> + */
> + error = xfs_btree_increment(cur, 0, &have_gt);
> + if (error)
> + goto out_error;
> + if (have_gt) {
> + error = xfs_rmap_get_rec(cur, >rec, &i);
> + if (error)
> + goto out_error;
> + XFS_WANT_CORRUPTED_GOTO(mp, i == 1, out_error);
> + //printk("rmalloc ag %d bno 0x%x/0x%x/0x%llx, gtrec 0x%x/0x%x/0x%llx\n",
> + // agno, bno, len, owner, gtrec.rm_startblock,
> + // gtrec.rm_blockcount, gtrec.rm_owner);
> + XFS_WANT_CORRUPTED_GOTO(mp, bno + len <= gtrec.rm_startblock,
> + out_error);
> + } else {
> + gtrec.rm_owner = XFS_RMAP_OWN_NULL;
> + }
> +
> + /*
> + * Note: cursor currently points one record to the right of ltrec, even
> + * if there is no record in the tree to the right.
> + */
> + if (ltrec.rm_owner == owner &&
> + ltrec.rm_startblock + ltrec.rm_blockcount == bno) {
> + /*
> + * left edge contiguous, merge into left record.
> + *
> + * ltbno ltlen
> + * orig: |ooooooooo|
> + * adding: |aaaaaaaaa|
> + * result: |rrrrrrrrrrrrrrrrrrr|
> + * bno len
> + */
> + //printk("add left\n");
> + ltrec.rm_blockcount += len;
> + if (gtrec.rm_owner == owner &&
> + bno + len == gtrec.rm_startblock) {
> + //printk("add middle\n");
> + /*
> + * right edge also contiguous, delete right record
> + * and merge into left record.
> + *
> + * ltbno ltlen gtbno gtlen
> + * orig: |ooooooooo| |ooooooooo|
> + * adding: |aaaaaaaaa|
> + * result: |rrrrrrrrrrrrrrrrrrrrrrrrrrrrr|
> + */
> + ltrec.rm_blockcount += gtrec.rm_blockcount;
> + error = xfs_btree_delete(cur, &i);
> + if (error)
> + goto out_error;
> + XFS_WANT_CORRUPTED_GOTO(mp, i == 1, out_error);
> + }
> +
> + /* point the cursor back to the left record and update */
> + error = xfs_btree_decrement(cur, 0, &have_gt);
> + if (error)
> + goto out_error;
> + error = xfs_rmap_update(cur, <rec);
> + if (error)
> + goto out_error;
> + } else if (gtrec.rm_owner == owner &&
> + bno + len == gtrec.rm_startblock) {
> + /*
> + * right edge contiguous, merge into right record.
> + *
> + * gtbno gtlen
> + * Orig: |ooooooooo|
> + * adding: |aaaaaaaaa|
> + * Result: |rrrrrrrrrrrrrrrrrrr|
> + * bno len
> + */
> + //printk("add right\n");
> + gtrec.rm_startblock = bno;
> + gtrec.rm_blockcount += len;
> + error = xfs_rmap_update(cur, >rec);
> + if (error)
> + goto out_error;
> + } else {
> + //printk("add no match\n");
> + /*
> + * no contiguous edge with identical owner, insert
> + * new record at current cursor position.
> + */
> + cur->bc_rec.r.rm_startblock = bno;
> + cur->bc_rec.r.rm_blockcount = len;
> + cur->bc_rec.r.rm_owner = owner;
> + error = xfs_btree_insert(cur, &i);
> + if (error)
> + goto out_error;
> + XFS_WANT_CORRUPTED_GOTO(mp, i == 1, out_error);
> + }
> +
> trace_xfs_rmap_alloc_extent_done(mp, agno, bno, len, owner);
> + xfs_btree_del_cursor(cur, XFS_BTREE_NOERROR);
> return 0;
>
> out_error:
> trace_xfs_rmap_alloc_extent_error(mp, agno, bno, len, owner);
> + xfs_btree_del_cursor(cur, XFS_BTREE_ERROR);
> return error;
> }
> --
> 2.0.0
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-25 16:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 6:04 [RFC PATCH 00/20] xfs: reverse mapping btree support Dave Chinner
2015-06-03 6:04 ` [PATCH 01/20] xfs: xfs_alloc_fix_freelist() can use incore perag structures Dave Chinner
2015-06-15 14:57 ` Brian Foster
2015-06-03 6:04 ` [PATCH 02/20] xfs: factor out free space extent length check Dave Chinner
2015-06-15 14:58 ` Brian Foster
2015-06-03 6:04 ` [PATCH 03/20] xfs: sanitise error handling in xfs_alloc_fix_freelist Dave Chinner
2015-06-15 14:58 ` Brian Foster
2015-06-15 21:51 ` Dave Chinner
2015-06-16 11:27 ` Brian Foster
2015-06-22 0:10 ` Dave Chinner
2015-06-03 6:04 ` [PATCH 04/20] xfs: clean up XFS_MIN_FREELIST macros Dave Chinner
2015-06-15 14:58 ` Brian Foster
2015-06-03 6:04 ` [PATCH 05/20] xfs: introduce rmap btree definitions Dave Chinner
2015-06-03 6:30 ` Darrick J. Wong
2015-06-03 6:34 ` Darrick J. Wong
2015-06-03 6:04 ` [PATCH 06/20] xfs: add rmap btree stats infrastructure Dave Chinner
2015-06-03 6:04 ` [PATCH 07/20] xfs: rmap btree add more reserved blocks Dave Chinner
2015-06-03 6:04 ` [PATCH 08/20] xfs: add owner field to extent allocation and freeing Dave Chinner
2015-06-24 19:09 ` Brian Foster
2015-06-24 21:13 ` Dave Chinner
2015-06-25 13:03 ` Brian Foster
2015-06-03 6:04 ` [PATCH 09/20] xfs: introduce rmap extent operation stubs Dave Chinner
2015-06-03 6:04 ` [PATCH 10/20] xfs: define the on-disk rmap btree format Dave Chinner
2015-06-03 6:04 ` [PATCH 11/20] xfs: add rmap btree growfs support Dave Chinner
2015-06-03 6:04 ` [PATCH 12/20] xfs: rmap btree transaction reservations Dave Chinner
2015-06-03 6:04 ` [PATCH 13/20] xfs: rmap btree requires more reserved free space Dave Chinner
2015-06-25 16:41 ` Brian Foster
2015-07-10 0:37 ` Dave Chinner
2015-06-03 6:04 ` [PATCH 14/20] xfs: add rmap btree operations Dave Chinner
2015-06-03 6:04 ` [PATCH 15/20] xfs: add an extent to the rmap btree Dave Chinner
2015-06-25 16:41 ` Brian Foster [this message]
2015-07-10 0:39 ` Dave Chinner
2015-06-03 6:04 ` [PATCH 16/20] xfs: remove an extent from " Dave Chinner
2015-06-03 6:04 ` [PATCH 17/20] xfs: add rmap btree geometry feature flag Dave Chinner
2015-06-03 6:04 ` [PATCH 18/20] xfs: add rmap btree block detection to log recovery Dave Chinner
2015-06-03 6:04 ` [PATCH 19/20] xfs: disable XFS_IOC_SWAPEXT when rmap btree is enabled Dave Chinner
2015-06-03 6:04 ` [PATCH 20/20] xfs: enable the rmap btree functionality Dave Chinner
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=20150625164123.GD36162@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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