LKML Archive on
help / color / mirror / Atom feed
From: David Ahern <>
To: Namhyung Kim <>,
	Arnaldo Carvalho de Melo <>
Cc: "Adrian Hunter" <>,
	"Jiri Olsa" <>, "Ingo Molnar" <>,
	"Frédéric Weisbecker" <>,
	"Linux Kernel Mailing List" <>
Subject: Re: heads up/RFC: 'perf trace' using ordered_events
Date: Tue, 10 Mar 2015 08:25:27 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20150310060644.GC943@sejong>

On 3/10/15 12:06 AM, Namhyung Kim wrote:
> Hi Arnaldo,
> On Mon, Mar 09, 2015 at 10:21:35AM -0300, Arnaldo Carvalho de Melo wrote:
>> For trace I need to take advantage of the fact that each mmap is ordered
>> already and then just sort by the timestamp in the mmap head, etc.
>> In retrospect, the file should have kept that ordering, i.e.
>> have one file per mmap, that would be saved in parallel, without any of
>> But I have to experiment with that, leaving the existing code around to
>> deal with older files.
> It seems like what you said is almost same as my multi-thread work.
> It saves data files per mmap and then merges them with an index
> table so that they can be processed in parallel.

I think you and Jiri both have worked on saving a file per mmap. Where 
does that stand? I would like to try it out.

With the 1024 cpu systems I am seeing 5GB files in 1 second runs and 
perf is not handling it well. The perf-script/perf-report (stdio) will 
'hang' for 45 minutes munging through the file. I have to connect gdb 
from time to time to verify it is making progress (file_offset is 
increasing). I believe what happens is that there is 'no round' -- it 
has to process all mmaps (1024 cpus and 6 or 7 events) through the 
ordered events queue before it can push out results. I need to look at 
that once I figure out the task scheduler problem.


  reply	other threads:[~2015-03-10 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 16:49 Arnaldo Carvalho de Melo
2015-03-04  1:01 ` Namhyung Kim
2015-03-04  1:07   ` Arnaldo Carvalho de Melo
2015-03-07 12:45     ` Adrian Hunter
2015-03-09 13:21       ` Arnaldo Carvalho de Melo
2015-03-10  6:06         ` Namhyung Kim
2015-03-10 14:25           ` David Ahern [this message]
2015-03-11  0:33             ` Namhyung Kim

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: heads up/RFC: '\''perf trace'\'' using ordered_events' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).