From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 20/26] move xfs_bmbt_newroot to common code
Date: Tue, 5 Aug 2008 10:50:13 +1000 [thread overview]
Message-ID: <20080805005013.GK6119@disturbed> (raw)
In-Reply-To: <20080804013530.GU8819@lst.de>
On Mon, Aug 04, 2008 at 03:35:30AM +0200, Christoph Hellwig wrote:
> xfs_bmbt_newroot is a mostly generic implementation of moving from
> an inode root to a real block based root. So move it to xfs_btree.c
> where it can use all the nice infrastructure there and make it pointer
> size agnostic
>
> The new name for it is xfs_btree_iroot_to_root which is not very
> nice but at least slightly more descriptive than the old name.
.....
> +
> + XFS_BTREE_TRACE_CURSOR(cur, XBT_ENTRY);
> + XFS_BTREE_STATS_INC(cur, newroot);
> +
> + level = cur->bc_nlevels - 1;
> + /* XXX(hch): this should be an get_inode_from_root, right? */
> + block = xfs_btree_get_block(cur, level, &bp);
Yes, probably should be. Also an assert to ensure the btree does
have the root in inode falg set might be appropriate....
Otherwise looks fine.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2008-08-05 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 1:35 [PATCH 20/26] move xfs_bmbt_newroot to common code Christoph Hellwig
2008-08-05 0:50 ` Dave Chinner [this message]
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=20080805005013.GK6119@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