From: Christoph Hellwig <hch@infradead.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
Alex Elder <aelder@sgi.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] xfs: Convert some trace events to DEFINE_TRACE
Date: Thu, 31 Dec 2009 04:36:04 -0500 [thread overview]
Message-ID: <20091231093604.GA29917@infradead.org> (raw)
In-Reply-To: <4B3C64D4.3060706@cn.fujitsu.com>
On Thu, Dec 31, 2009 at 04:46:12PM +0800, Li Zefan wrote:
> Use DECLARE_EVENT_CLASS/DEFINE_EVENT to remove duplicate code:
>
> text data bss dec hex filename
> 871963 35416 3612 910991 de68f fs/xfs/xfs.o.orig
> 575027 35416 3404 613847 95dd7 fs/xfs/xfs.o
>
> To test this patch, I compared the format files of trace events,
> before and after patching:
I already sent this patch a long time ago, still waiting for Alex to
pick it up.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-12-31 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 8:46 [PATCH] xfs: Convert some trace events to DEFINE_TRACE Li Zefan
2009-12-31 9: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=20091231093604.GA29917@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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