From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 1/2] tracing/core: make the per cpu trace files in per cpu directories
Date: Thu, 26 Feb 2009 08:06:52 +0100 [thread overview]
Message-ID: <20090226070651.GA6325@nowhere> (raw)
In-Reply-To: <49a632a5.0707d00a.296d.24b3@mx.google.com>
On Thu, Feb 26, 2009 at 12:41:38AM +0100, Frederic Weisbecker wrote:
> Impact: scale per cpu tracing
>
> The per cpu trace files are all in a single directory: /debug/tracing/per_cpu.
> In case of a large number of cpu, the content of this directory becomes messy
> so we create now one directory per cpu inside /debug/tracing/per_cpu which contain
> each their own trace_pipe and trace files.
>
> Ie:
>
> nobody@nowhere:/debug/tracing$ ls -R per_cpu
> per_cpu:
> cpu0 cpu1
>
> per_cpu/cpu0:
> trace trace_pipe
>
> per_cpu/cpu1:
> trace trace_pipe
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
Oh, I forgot to mention: they apply on top of latest -tip + the ftrace_bprintk 3 patches.
next prev parent reply other threads:[~2009-02-26 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 23:41 [PATCH 1/2] tracing/core: make the per cpu trace files in per cpu directories Frederic Weisbecker
2009-02-26 7:06 ` Frederic Weisbecker [this message]
2009-02-26 13:14 ` Ingo Molnar
2009-02-26 13: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=20090226070651.GA6325@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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