|| ||Steven Rostedt <rostedt-AT-goodmis.org>|
|| ||Andrew Morton <akpm-AT-linux-foundation.org>|
|| ||Re: [PATCH][RFC] vsprintf: unify the format decoding layer for its
|| ||Fri, 27 Feb 2009 10:03:03 -0500 (EST)|
|| ||Frederic Weisbecker <fweisbec-AT-gmail.com>,
Ingo Molnar <mingo-AT-elte.hu>,
Linus Torvalds <torvalds-AT-linux-foundation.org>,
linux-kernel-AT-vger.kernel.org, Lai Jiangshan <laijs-AT-cn.fujitsu.com>,
Peter Zijlstra <peterz-AT-infradead.org>|
|| ||Article, Thread
On Thu, 26 Feb 2009, Andrew Morton wrote:
> On Fri, 27 Feb 2009 07:19:37 +0100 Frederic Weisbecker <firstname.lastname@example.org> wrote:
> > An new optimization is making its way to ftrace. Its purpose is to
> > make ftrace_printk() consuming less memory and be faster.
> > Written by Lai Jiangshan, the approach is to delay the formatting
> > job from tracing time to output time.
> > Currently, a call to ftrace_printk will format the whole string and
> > insert it into the ring buffer.
> It does that? eek.
Yes, I remember when Linus suggested having a pointer to the format and
the args saved. There was two issues I found.
1) You still needed to read the format string to find out what arguments
2) The format string could be part of module data, and if the module is
unloaded between the time of recording and the time of reading the
trace, we now have a format pointer pointing to God knows what.
When posting ftrace_printk, I said this was for debugging purposes only,
and I was not about to work on optimizations there of. But Frederic and
Lai are doing a great job in that aspect ;-)
HAHAHAHHAAAA!!!! My evil scheme is working! I post some sub-optimal code,
and have others do the nasty work for me!!!!
Oh, did I just say that out loud?
to post comments)