From: Christoph Hellwig <hch@lst.de>
To: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: [PATCH 08/21] make btree tracing generic
Date: Fri, 1 Aug 2008 21:36:25 +0200 [thread overview]
Message-ID: <20080801193625.GB1263@lst.de> (raw)
In-Reply-To: <20080730013920.GI13395@disturbed>
On Wed, Jul 30, 2008 at 11:39:20AM +1000, Dave Chinner wrote:
> > + 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....
Well, we need to case to void * somewhere, and going from struct
to arguments list isn't helpful either.
Changing the whole ktrace thing to an args strucutr and/or varags
would be nice, but is not in scope for this patchset..
> > +static void
> > +xfsidb_btree_trace_record(
>
> shouldn't these all use "xfsidbg" prefixes?
Probably.
prev parent reply other threads:[~2008-08-01 19:35 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
2008-08-01 19:36 ` Christoph Hellwig [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=20080801193625.GB1263@lst.de \
--to=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