linux-kernel - Re: [PATCH 1/2] tracing/core: make the per cpu trace files in per cpu directories

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090226070651.GA6325@nowhere>
Date:	Thu, 26 Feb 2009 08:06:52 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [PATCH 1/2] tracing/core: make the per cpu trace files in per
	cpu directories

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@...here:/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@...il.com>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Lai Jiangshan <laijs@...fujitsu.com>


Oh, I forgot to mention: they apply on top of latest -tip + the ftrace_bprintk 3 patches.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/