linux-kernel - Re: [PATCH] perf tools: Exit recording if events have non matching sample type

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: <1317722412.25926.16.camel@twins>
Date:	Tue, 04 Oct 2011 12:00:12 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	David Ahern <dsahern@...il.com>
Cc:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Jiri Olsa <jolsa@...hat.com>, mingo@...e.hu, paulus@...ba.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf tools: Exit recording if events have non matching
 sample type

On Mon, 2011-10-03 at 22:14 -0600, David Ahern wrote:
> On 09/30/2011 01:39 AM, Peter Zijlstra wrote:
> > On Thu, 2011-09-29 at 17:33 -0600, David Ahern wrote:
> >>> For record that means we need to dump each per-sample_id mmap onto a
> >>> separate file, i.e. use a directory, etc.
> >>
> >> That seems like a major re-write of perf. 
> > 
> > Well we want to go there anyway. A file per cpu stream can be a lot less
> > overhead than one file for all cpu streams.
> > 
> 
> really it becomes file per cpu stream and per sample type. So a dual
> socket, quad core with HT means 16 files per sample type. ie., the
> number of files explodes quick.
> 
> I understand the allure for simplicity during the data collection. Has
> any thought been given on management of the files in such a scenario?
> User specifies a directory path instead of a file path - or both to
> handle backward compatibility?

I think the idea was a directory and a script to convert old data files
to the new format. But it was a while ago acme and I talked about this.
--
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/