[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f178dde-751f-9ac9-f5a0-fd1bfba3ca32@linux.intel.com>
Date: Thu, 6 May 2021 15:43:55 +0300
From: "Bayduraev, Alexey V" <alexey.v.bayduraev@...ux.intel.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...hat.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Andi Kleen <ak@...ux.intel.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Alexander Antonov <alexander.antonov@...ux.intel.com>,
Alexei Budankov <abudankov@...wei.com>
Subject: Re: [PATCH v5 00/20] Introduce threaded trace streaming for basic
perf record operation
Hi,
On 06.05.2021 9:20, Namhyung Kim wrote:
> Hello,
>
> On Tue, May 4, 2021 at 12:05 AM Alexey Bayduraev
> <alexey.v.bayduraev@...ux.intel.com> wrote:
>>
<SNIP>>>
>> Basic analysis of data directories is provided in perf report mode.
>> Raw dump and aggregated reports are available for data directories,
>> still with no memory consumption optimizations.
>
> Do you have an idea how to improve it?
>
> I have to say again that I don't like merely adding more threads to
> record. Yeah, parallelizing the perf record is good, but we have to
> think about the perf report (and others) too.
There is your idea about separating tracking records and process them
first, but these changes can be much larger than my patch and I think
they looks like independent patch and could be introduced as extension
of parallel data loading.
I also thought and experimented with the intermediate flushing of
the ordered queue. This is simple for per-cpu data files (sorted
by time), but not clear for arbitrary CPU masks.
I think my patch can be the first step to introduce parallel mode
to the perf tool. It just extends perf-record (already used in our
vtune tool) and allows to load parallel data in experimental mode.
Next patches could optimize and extend parallel data loading.
Regards,
Alexey
>
> Thanks,
> Namhyung
>
>
>>
>> Tested:
>>
>> tools/perf/perf record -o prof.data --threads -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads= -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads=cpu -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads=core -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads=socket -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads=numa -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads=0-3/3:4-7/4 -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data -C 2,5 --threads=0-3/3:4-7/4 -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data -C 3,4 --threads=0-3/3:4-7/4 -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data -C 0,4,2,6 --threads=core -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data -C 0,4,2,6 --threads=numa -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads -g --call-graph dwarf,4096 -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads -g --call-graph dwarf,4096 --compression-level=3 -- matrix.gcc.g.O3
>> tools/perf/perf record -o prof.data --threads -a
>> tools/perf/perf record -D -1 -e cpu-cycles -a --control fd:10,11 -- sleep 30
>> tools/perf/perf record --threads -D -1 -e cpu-cycles -a --control fd:10,11 -- sleep 30
>>
>> tools/perf/perf report -i prof.data
>> tools/perf/perf report -i prof.data --call-graph=callee
>> tools/perf/perf report -i prof.data --stdio --header
>> tools/perf/perf report -i prof.data -D --header
>>
>> [1] git clone https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git -b perf/record_threads
>> [2] https://lore.kernel.org/lkml/20180913125450.21342-1-jolsa@kernel.org/
>>
>> ---
>>
>> Alexey Bayduraev (20):
>> perf record: introduce thread affinity and mmap masks
>> perf record: introduce thread specific data array
>> perf record: introduce thread local variable
>> perf record: stop threads in the end of trace streaming
>> perf record: start threads in the beginning of trace streaming
>> perf record: introduce data file at mmap buffer object
>> perf record: introduce data transferred and compressed stats
>> perf record: init data file at mmap buffer object
>> tools lib: introduce bitmap_intersects() operation
>> perf record: introduce --threads=<spec> command line option
>> perf record: document parallel data streaming mode
>> perf report: output data file name in raw trace dump
>> perf session: move reader structure to the top
>> perf session: introduce reader_state in reader object
>> perf session: introduce reader objects in session object
>> perf session: introduce decompressor into trace reader object
>> perf session: move init into reader__init function
>> perf session: move map/unmap into reader__mmap function
>> perf session: load single file for analysis
>> perf session: load data directory files for analysis
>>
>> tools/include/linux/bitmap.h | 11 +
>> tools/lib/api/fd/array.c | 17 +
>> tools/lib/api/fd/array.h | 1 +
>> tools/lib/bitmap.c | 14 +
>> tools/perf/Documentation/perf-record.txt | 30 +
>> tools/perf/builtin-inject.c | 3 +-
>> tools/perf/builtin-record.c | 1066 ++++++++++++++++++++--
>> tools/perf/util/evlist.c | 16 +
>> tools/perf/util/evlist.h | 1 +
>> tools/perf/util/mmap.c | 6 +
>> tools/perf/util/mmap.h | 6 +
>> tools/perf/util/ordered-events.h | 1 +
>> tools/perf/util/record.h | 2 +
>> tools/perf/util/session.c | 491 +++++++---
>> tools/perf/util/session.h | 5 +
>> tools/perf/util/tool.h | 3 +-
>> 16 files changed, 1474 insertions(+), 199 deletions(-)
>>
>> --
>> 2.19.0
>>
Powered by blists - more mailing lists