From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 08/21] make btree tracing generic
Date: Wed, 30 Jul 2008 11:39:20 +1000 [thread overview]
Message-ID: <20080730013920.GI13395@disturbed> (raw)
In-Reply-To: <20080729193044.GI19104@lst.de>
On Tue, Jul 29, 2008 at 09:30:44PM +0200, Christoph Hellwig wrote:
> make the existing bmap btree tracing generic so that it applies to all
> btree types.
>
> Some fragments lifted from a patch by Dave Chinner.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Index: linux-2.6-xfs/fs/xfs/xfs_btree.h
> ===================================================================
> --- linux-2.6-xfs.orig/fs/xfs/xfs_btree.h 2008-07-29 16:23:23.000000000 +0200
> +++ linux-2.6-xfs/fs/xfs/xfs_btree.h 2008-07-29 16:52:06.000000000 +0200
> @@ -190,6 +190,25 @@ struct xfs_btree_ops {
>
> /* get inode rooted btree root */
> struct xfs_btree_block *(*get_root_from_inode)(struct xfs_btree_cur *);
> +
> + /* btree tracing */
> +#ifdef XFS_BTREE_TRACE
> + void (*trace_enter)(struct xfs_btree_cur *, const char *,
> + char *, int, int, __psunsigned_t,
> + __psunsigned_t, __psunsigned_t,
> + __psunsigned_t, __psunsigned_t,
> + __psunsigned_t, __psunsigned_t,
> + __psunsigned_t, __psunsigned_t,
> + __psunsigned_t, __psunsigned_t);
Would it be better to use a 'trace args' structure here rather
than passing a heap of parameters? memset(args, 0,...) rather than
passing a whole heap of zeros in most cases seems like a better
approach to me, esp. as they all get cast to (void *) anyway....
> +static void
> +xfsidb_btree_trace_record(
shouldn't these all use "xfsidbg" prefixes?
Otherwise looks ok.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-07-30 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 19:30 [PATCH 08/21] make btree tracing generic Christoph Hellwig
2008-07-30 1:39 ` Dave Chinner [this message]
2008-08-01 19:36 ` 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=20080730013920.GI13395@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 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.