From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Tim Bird <tim.bird@am.sony.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] tracing/function-graph-tracer: improve duration output
Date: Wed, 03 Dec 2008 11:27:06 +0100 [thread overview]
Message-ID: <1228300026.9673.122.camel@twins> (raw)
In-Reply-To: <c62985530812030223o4af19ab7idec0894bcdd275d@mail.gmail.com>
On Wed, 2008-12-03 at 11:23 +0100, Frédéric Weisbecker wrote:
> 2008/12/3 Peter Zijlstra <a.p.zijlstra@chello.nl>:
> > On Wed, 2008-12-03 at 11:07 +0100, Frédéric Weisbecker wrote:
> >>
> >>
> >> >
> >> > btw., i tested the graph tracer on a 16-way 64-bit box as well, and
> >> the
> >> > multi-digit CPU field printout magic works fine there too:
> >> >
> >> > 9) | pick_next_task() {
> >> > 9) 0.283 us | pick_next_task_fair();
> >> > 9) 0.276 us | pick_next_task_rt();
> >> > 9) 0.273 us | pick_next_task_fair();
> >> > 9) 0.279 us | pick_next_task_idle();
> >> > 9) 2.596 us | }
> >> > 9) 0.566 us | __lock_text_start();
> >> > 10) 0.299 us | }
> >> > 10) | mm_init() {
> >> > 10) | pgd_alloc() {
> >> > 10) | __get_free_pages() {
> >> > 10) | alloc_pages_current() {
> >> > 10) 0.330 us | policy_zonelist();
> >> > 10) | __alloc_pages_internal() {
> >> >
> >> > Ingo
> >> >
> >>
> >> Hmm not really, there should be one space more before the 9 to fit the
> >> log10(MAX_CPU) here and not break
> >> the column.
> >
> > It did in my copy of Ingo's email...
>
>
> So perhaps I should drop gmail...... :-(
I've been told that gmail has ways of extracting email through POP3.
Perhaps that manages to preserve layout.. if not, I'll file a bug with
google and get a real mail account pronto :-)
next prev parent reply other threads:[~2008-12-03 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 1:32 [PATCH 2/2] tracing/function-graph-tracer: improve duration output Frederic Weisbecker
2008-12-03 1:34 ` Frederic Weisbecker
2008-12-03 8:19 ` Ingo Molnar
2008-12-03 8:33 ` Ingo Molnar
2008-12-03 10:07 ` Frédéric Weisbecker
2008-12-03 10:21 ` Peter Zijlstra
2008-12-03 10:23 ` Frédéric Weisbecker
2008-12-03 10:27 ` Peter Zijlstra [this message]
2008-12-03 10:29 ` Frédéric Weisbecker
2008-12-03 11:52 ` Steven Rostedt
2008-12-03 13:11 ` Frédéric Weisbecker
2008-12-03 13:17 ` Peter Zijlstra
2008-12-03 13:21 ` Steven Rostedt
2008-12-03 15:44 ` Frédéric Weisbecker
2008-12-03 16:31 ` Steven Rostedt
2008-12-03 14:22 ` Ingo Molnar
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=1228300026.9673.122.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.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