From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
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 14:22:27 +0100 [thread overview]
Message-ID: <20090226132227.GA17530@elte.hu> (raw)
In-Reply-To: <20090226131431.GA14722@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> * Frederic Weisbecker <fweisbec@gmail.com> 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.
>
> Applied to tip:tracing/ftrace, thanks Frederic!
The layout looks much more structured on a 16-way box now:
phoenix:/debug/tracing/per_cpu> ll
total 0
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu0
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu1
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu10
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu11
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu12
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu13
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu14
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu15
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu2
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu3
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu4
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu5
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu6
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu7
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu8
drwxr-xr-x 2 root root 0 2009-02-26 14:19 cpu9
phoenix:/debug/tracing/per_cpu> cd cpu0
phoenix:/debug/tracing/per_cpu/cpu0> ll
total 0
-r--r--r-- 1 root root 0 2009-02-26 14:19 trace
-r--r--r-- 1 root root 0 2009-02-26 14:19 trace_pipe
phoenix:/debug/tracing/per_cpu/cpu0>
Ingo
prev parent reply other threads:[~2009-02-26 13:22 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
2009-02-26 13:14 ` Ingo Molnar
2009-02-26 13:22 ` Ingo Molnar [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=20090226132227.GA17530@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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