From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
mingo@elte.hu, paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Exit recording if events have non matching sample type
Date: Tue, 4 Oct 2011 10:41:55 -0300 [thread overview]
Message-ID: <20111004134155.GA31979@ghostprotocols.net> (raw)
In-Reply-To: <1317722412.25926.16.camel@twins>
Em Tue, Oct 04, 2011 at 12:00:12PM +0200, Peter Zijlstra escreveu:
> 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.
I don't remember the script idea, but that would work too.
WRT major rewrites, well, as we go on developing any piece of software,
those kinds of things happen :-)
If it is to improve things, make them faster, cope with new hardware
realities, keep our jobs, so be it! ;-)
- Arnaldo
next prev parent reply other threads:[~2011-10-04 13:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 23:06 [PATCH] perf tools: Exit recording if events have non matching sample type Arnaldo Carvalho de Melo
2011-09-29 23:33 ` David Ahern
2011-09-30 0:40 ` Arnaldo Carvalho de Melo
2011-09-30 0:58 ` David Ahern
2011-09-30 2:21 ` Arnaldo Carvalho de Melo
2011-09-30 2:41 ` David Ahern
2011-09-30 7:39 ` Peter Zijlstra
2011-10-04 4:14 ` David Ahern
2011-10-04 10:00 ` Peter Zijlstra
2011-10-04 13:41 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-29 16:01 Jiri Olsa
2011-09-29 22:05 ` Arnaldo Carvalho de Melo
2011-09-29 22:55 ` David Ahern
2011-10-03 10:22 ` Jiri Olsa
2011-10-03 16:27 ` Arnaldo Carvalho de Melo
2011-10-03 19:15 ` Jiri Olsa
2011-10-17 12:50 ` Jiri Olsa
2011-10-21 7:18 ` Xu, Anhua
2011-10-21 8:10 ` Jiri Olsa
2011-10-21 14:16 ` David Ahern
2011-10-21 14:29 ` David Ahern
2011-10-21 14:43 ` Jiri Olsa
2011-10-21 14:42 ` Jiri Olsa
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=20111004134155.GA31979@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.