From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 4/6] cleanup btree record / key / ptr addressing macros
Date: Tue, 16 Sep 2008 15:53:33 +1000 [thread overview]
Message-ID: <20080916055333.GW5811@disturbed> (raw)
In-Reply-To: <20080915004653.GE12213@lst.de>
On Mon, Sep 15, 2008 at 02:46:53AM +0200, Christoph Hellwig wrote:
> Replace the generic record / key / ptr addressing macros that use cpp token
> pasting with simpler macros that do the job for just one given btree type.
> The new macros lose the cur argument and thus can be used outside the core
> btree code, but also gain an xfs_mount * argument to allow for checking the
> CRC flag in the near future. Note that many of these macros aren't actually
> used in the kernel code, but only in userspace (mostly in xfs_repair).
......
> @@ -85,9 +84,9 @@ xfs_bmdr_to_bmbt(
> rblock->bb_leftsib = cpu_to_be64(NULLDFSBNO);
> rblock->bb_rightsib = cpu_to_be64(NULLDFSBNO);
> dmxr = xfs_bmdr_maxrecs(mp, dblocklen, 0);
> - fkp = XFS_BTREE_KEY_ADDR(xfs_bmdr, dblock, 1);
> - tkp = XFS_BMAP_BROOT_KEY_ADDR(rblock, 1, rblocklen);
> - fpp = XFS_BTREE_PTR_ADDR(xfs_bmdr, dblock, 1, dmxr);
> + fkp = XFS_BMDR_KEY_ADDR(dblock, 1);
> + tkp = XFS_BMBT_KEY_ADDR(mp, rblock, 1);
> + fpp = XFS_BMDR_PTR_ADDR(dblock, 1, dmxr);
> tpp = XFS_BMAP_BROOT_PTR_ADDR(mp, rblock, 1, rblocklen);
Why did you change XFS_BMAP_BROOT_KEY_ADDR and not
XFS_BMAP_BROOT_PTR_ADDR?
> dmxr = be16_to_cpu(dblock->bb_numrecs);
> memcpy(tkp, fkp, sizeof(*fkp) * dmxr);
> @@ -448,10 +447,10 @@ xfs_bmbt_to_bmdr(
> dblock->bb_level = rblock->bb_level;
> dblock->bb_numrecs = rblock->bb_numrecs;
> dmxr = xfs_bmdr_maxrecs(mp, dblocklen, 0);
> - fkp = XFS_BMAP_BROOT_KEY_ADDR(rblock, 1, rblocklen);
> - tkp = XFS_BTREE_KEY_ADDR(xfs_bmdr, dblock, 1);
> - fpp = XFS_BMAP_BROOT_PTR_ADDR(mp, rblock, 1, rblocklen);
> - tpp = XFS_BTREE_PTR_ADDR(xfs_bmdr, dblock, 1, dmxr);
> + fkp = XFS_BMBT_KEY_ADDR(mp, rblock, 1);
> + tkp = XFS_BMDR_KEY_ADDR(dblock, 1);
> + fpp = XFS_BMAP_BROOT_PTR_ADDR(mp, rblock, 1, rblocklen);
^^
Stray whitespace.
> @@ -79,15 +79,24 @@ typedef struct xfs_btree_sblock xfs_allo
> /*
> * Record, key, and pointer address macros for btree blocks.
> */
> -#define XFS_ALLOC_REC_ADDR(bb,i,cur) \
> - XFS_BTREE_REC_ADDR(xfs_alloc, bb, i)
> +#define XFS_ALLOC_REC_ADDR(mp, block, index) \
> + ((xfs_alloc_rec_t *) \
> + ((char *)(block) + \
> + sizeof(struct xfs_btree_sblock) + \
> + (((index) - 1) * sizeof(xfs_alloc_rec_t))))
Shouldn't these become inline functions rather than macros now
that the token substitution is gone? Same for rest as well?
That would remove a bunch of shouting that you're changing
anyway....
> -
> - if (root) {
> - keyp = XFS_BMAP_BROOT_KEY_ADDR(block, i, sz);
> - } else {
> - keyp = XFS_BTREE_KEY_ADDR(xfs_bmbt, block, i);
> - }
> + keyp = XFS_BMBT_KEY_ADDR(mp, block, i);
>
> if (prevp) {
> ASSERT(be64_to_cpu(prevp->br_startoff) <
> @@ -6203,19 +6200,16 @@ xfs_check_block(
> /*
> * Compare the block numbers to see if there are dups.
> */
> -
> - if (root) {
> + if (root)
> pp = XFS_BMAP_BROOT_PTR_ADDR(mp, block, i, sz);
> - } else {
> - pp = XFS_BTREE_PTR_ADDR(xfs_bmbt, block, i, dmxr);
> - }
> + else
> + pp = XFS_BMBT_PTR_ADDR(mp, block, i, dmxr);
Why the assymetry in the interfaces for key and ptr?
> -#define XFS_BMAP_BROOT_REC_ADDR(bb,i,sz) \
> - (XFS_BTREE_REC_ADDR(xfs_bmbt,bb,i))
> -#define XFS_BMAP_BROOT_KEY_ADDR(bb,i,sz) \
> - (XFS_BTREE_KEY_ADDR(xfs_bmbt,bb,i))
> -#define XFS_BMAP_BROOT_PTR_ADDR(mp, bb,i,sz) \
> - (XFS_BTREE_PTR_ADDR(xfs_bmbt,bb,i,xfs_bmbt_maxrecs(mp, sz, 0)))
> +#define XFS_BMAP_BROOT_PTR_ADDR(mp, bb, i, sz) \
> + XFS_BMBT_PTR_ADDR(mp, bb, i, xfs_bmbt_maxrecs(mp, sz, 0))
Ah, that explains why that macro didn't change. Why keep just this
one?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-09-16 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 0:46 [PATCH 4/6] cleanup btree record / key / ptr addressing macros Christoph Hellwig
2008-09-16 5:53 ` Dave Chinner [this message]
2008-09-16 17:41 ` Christoph Hellwig
2008-09-17 0:57 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2008-09-22 11:06 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=20080916055333.GW5811@disturbed \
--to=david@fromorbit.com \
--cc=hch@lst.de \
--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