All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, chandan.babu@oracle.com, hch@lst.de
Subject: Re: [PATCH 04/15] xfs: dynamically allocate btree scrub context structure
Date: Wed, 13 Oct 2021 09:29:41 -0700	[thread overview]
Message-ID: <20211013162941.GU24307@magnolia> (raw)
In-Reply-To: <20211013045738.GW2361455@dread.disaster.area>

On Wed, Oct 13, 2021 at 03:57:38PM +1100, Dave Chinner wrote:
> On Tue, Oct 12, 2021 at 04:32:55PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > Reorganize struct xchk_btree so that we can dynamically size the context
> > structure to fit the type of btree cursor that we have.  This will
> > enable us to use memory more efficiently once we start adding very tall
> > btree types.  Right-size the lastkey array so that we stop wasting the
> > first array element.
> 
> "right size"?
> 
> I'm assuming this is the "nlevels - 1" bit?

Yep.  I'll change the last sentence to:

"Right-size the lastkey array to match the number of node levels in the
btree so that we stop wasting space."

> > 
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> >  fs/xfs/scrub/btree.c |   23 ++++++++++++-----------
> >  fs/xfs/scrub/btree.h |   11 ++++++++++-
> >  2 files changed, 22 insertions(+), 12 deletions(-)
> > 
> > 
> > diff --git a/fs/xfs/scrub/btree.c b/fs/xfs/scrub/btree.c
> > index d5e1ca521fc4..6d4eba85ef77 100644
> > --- a/fs/xfs/scrub/btree.c
> > +++ b/fs/xfs/scrub/btree.c
> > @@ -189,9 +189,9 @@ xchk_btree_key(
> >  
> >  	/* If this isn't the first key, are they in order? */
> >  	if (cur->bc_ptrs[level] > 1 &&
> > -	    !cur->bc_ops->keys_inorder(cur, &bs->lastkey[level], key))
> > +	    !cur->bc_ops->keys_inorder(cur, &bs->lastkey[level - 1], key))
> >  		xchk_btree_set_corrupt(bs->sc, cur, level);
> > -	memcpy(&bs->lastkey[level], key, cur->bc_ops->key_len);
> > +	memcpy(&bs->lastkey[level - 1], key, cur->bc_ops->key_len);
> >  
> >  	if (level + 1 >= cur->bc_nlevels)
> >  		return;
> > @@ -631,17 +631,24 @@ xchk_btree(
> >  	union xfs_btree_ptr		*pp;
> >  	union xfs_btree_rec		*recp;
> >  	struct xfs_btree_block		*block;
> > -	int				level;
> >  	struct xfs_buf			*bp;
> >  	struct check_owner		*co;
> >  	struct check_owner		*n;
> > +	size_t				cur_sz;
> > +	int				level;
> >  	int				error = 0;
> >  
> >  	/*
> >  	 * Allocate the btree scrub context from the heap, because this
> > -	 * structure can get rather large.
> > +	 * structure can get rather large.  Don't let a caller feed us a
> > +	 * totally absurd size.
> >  	 */
> > -	bs = kmem_zalloc(sizeof(struct xchk_btree), KM_NOFS | KM_MAYFAIL);
> > +	cur_sz = xchk_btree_sizeof(cur->bc_nlevels);
> > +	if (cur_sz > PAGE_SIZE) {
> > +		xchk_btree_set_corrupt(sc, cur, 0);
> > +		return 0;
> > +	}
> > +	bs = kmem_zalloc(cur_sz, KM_NOFS | KM_MAYFAIL);
> >  	if (!bs)
> >  		return -ENOMEM;
> >  	bs->cur = cur;
> > @@ -653,12 +660,6 @@ xchk_btree(
> >  	/* Initialize scrub state */
> >  	INIT_LIST_HEAD(&bs->to_check);
> >  
> > -	/* Don't try to check a tree with a height we can't handle. */
> > -	if (cur->bc_nlevels > XFS_BTREE_MAXLEVELS) {
> > -		xchk_btree_set_corrupt(sc, cur, 0);
> > -		goto out;
> > -	}
> > -
> >  	/*
> >  	 * Load the root of the btree.  The helper function absorbs
> >  	 * error codes for us.
> > diff --git a/fs/xfs/scrub/btree.h b/fs/xfs/scrub/btree.h
> > index 7671108f9f85..62c3091ef20f 100644
> > --- a/fs/xfs/scrub/btree.h
> > +++ b/fs/xfs/scrub/btree.h
> > @@ -39,9 +39,18 @@ struct xchk_btree {
> >  
> >  	/* internal scrub state */
> >  	union xfs_btree_rec		lastrec;
> > -	union xfs_btree_key		lastkey[XFS_BTREE_MAXLEVELS];
> >  	struct list_head		to_check;
> > +
> > +	/* this element must come last! */
> > +	union xfs_btree_key		lastkey[];
> >  };
> > +
> > +static inline size_t
> > +xchk_btree_sizeof(unsigned int nlevels)
> > +{
> > +	return struct_size((struct xchk_btree *)NULL, lastkey, nlevels - 1);
> > +}
> 
> I'd like a comment here indicating that the max number of keys is
> "nlevels - 1" because the last level of the tree is records and
> that's held in a separate lastrec field...
> 
> That way there's a reminder of why there's a "- 1" here without
> having work it out from first principles every time we look at this
> code...

Ok; I've added the comment:

/*
 * Calculate the size of a xchk_btree structure.  There are nlevels-1
 * slots for keys because we track leaf records separately in lastrec.
 */

> Otherwise it seems reasonable.

<nod>

--D

> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

  reply	other threads:[~2021-10-13 16:29 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 23:32 [PATCHSET v3 00/15] xfs: support dynamic btree cursor height Darrick J. Wong
2021-10-12 23:32 ` [PATCH 01/15] xfs: remove xfs_btree_cur.bc_blocklog Darrick J. Wong
2021-10-13  0:56   ` Dave Chinner
2021-10-12 23:32 ` [PATCH 02/15] xfs: reduce the size of nr_ops for refcount btree cursors Darrick J. Wong
2021-10-13  0:57   ` Dave Chinner
2021-10-12 23:32 ` [PATCH 03/15] xfs: don't track firstrec/firstkey separately in xchk_btree Darrick J. Wong
2021-10-13  1:02   ` Dave Chinner
2021-10-12 23:32 ` [PATCH 04/15] xfs: dynamically allocate btree scrub context structure Darrick J. Wong
2021-10-13  4:57   ` Dave Chinner
2021-10-13 16:29     ` Darrick J. Wong [this message]
2021-10-12 23:33 ` [PATCH 05/15] xfs: support dynamic btree cursor heights Darrick J. Wong
2021-10-13  5:31   ` Dave Chinner
2021-10-13 16:52     ` Darrick J. Wong
2021-10-13 21:14       ` Dave Chinner
2021-10-12 23:33 ` [PATCH 06/15] xfs: rearrange xfs_btree_cur fields for better packing Darrick J. Wong
2021-10-13  5:34   ` Dave Chinner
2021-10-12 23:33 ` [PATCH 07/15] xfs: refactor btree cursor allocation function Darrick J. Wong
2021-10-13  5:34   ` Dave Chinner
2021-10-12 23:33 ` [PATCH 08/15] xfs: encode the max btree height in the cursor Darrick J. Wong
2021-10-13  5:38   ` Dave Chinner
2021-10-12 23:33 ` [PATCH 09/15] xfs: dynamically allocate cursors based on maxlevels Darrick J. Wong
2021-10-13  5:40   ` Dave Chinner
2021-10-13 16:55     ` Darrick J. Wong
2021-10-12 23:33 ` [PATCH 10/15] xfs: compute actual maximum btree height for critical reservation calculation Darrick J. Wong
2021-10-13  5:49   ` Dave Chinner
2021-10-13 17:07     ` Darrick J. Wong
2021-10-13 20:18       ` Dave Chinner
2021-10-12 23:33 ` [PATCH 11/15] xfs: compute the maximum height of the rmap btree when reflink enabled Darrick J. Wong
2021-10-13  7:25   ` Dave Chinner
2021-10-13 17:47     ` Darrick J. Wong
2021-10-12 23:33 ` [PATCH 12/15] xfs: kill XFS_BTREE_MAXLEVELS Darrick J. Wong
2021-10-13  7:25   ` Dave Chinner
2021-10-12 23:33 ` [PATCH 13/15] xfs: widen btree maxlevels computation to handle 64-bit record counts Darrick J. Wong
2021-10-13  7:28   ` Dave Chinner
2021-10-12 23:33 ` [PATCH 14/15] xfs: compute absolute maximum nlevels for each btree type Darrick J. Wong
2021-10-13  7:57   ` Dave Chinner
2021-10-13 21:36     ` Darrick J. Wong
2021-10-13 23:48       ` Dave Chinner
2021-10-12 23:33 ` [PATCH 15/15] xfs: use separate btree cursor cache " Darrick J. Wong
2021-10-13  8:01   ` Dave Chinner
2021-10-13 21:42     ` Darrick J. Wong

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=20211013162941.GU24307@magnolia \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.