From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Alexey Budankov <alexey.budankov@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team@lge.com
Subject: Re: [PATCH v15 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads
Date: Tue, 13 Nov 2018 11:47:16 +0900 [thread overview]
Message-ID: <20181113024716.GA27910@sejong> (raw)
In-Reply-To: <20181109082242.GJ29732@krava>
Hi,
On Fri, Nov 09, 2018 at 09:22:42AM +0100, Jiri Olsa wrote:
> On Tue, Nov 06, 2018 at 11:53:02AM +0300, Alexey Budankov wrote:
> >
> > Currently in record mode the tool implements trace writing serially.
> > The algorithm loops over mapped per-cpu data buffers and stores
> > ready data chunks into a trace file using write() system call.
> >
> > At some circumstances the kernel may lack free space in a buffer
> > because the other buffer's half is not yet written to disk due to
> > some other buffer's data writing by the tool at the moment.
> >
> > Thus serial trace writing implementation may cause the kernel
> > to loose profiling data and that is what observed when profiling
> > highly parallel CPU bound workloads on machines with big number
> > of cores.
> >
> > Experiment with profiling matrix multiplication code executing 128
> > threads on Intel Xeon Phi (KNM) with 272 cores, like below,
> > demonstrates data loss metrics value of 98%:
> >
> > /usr/bin/time perf record -o /tmp/perf-ser.data -a -N -B -T -R -g \
> > --call-graph dwarf,1024 --user-regs=IP,SP,BP --switch-events \
> > -e cycles,instructions,ref-cycles,software/period=1,name=cs,config=0x3/Duk -- \
> > matrix.gcc
> >
> > Data loss metrics is the ratio lost_time/elapsed_time where
> > lost_time is the sum of time intervals containing PERF_RECORD_LOST
> > records and elapsed_time is the elapsed application run time
> > under profiling.
> >
> > Applying asynchronous trace streaming thru Posix AIO API [1] lowers
> > data loss metrics value providing 2x improvement (from 98% to ~1%)
> >
> > Asynchronous trace streaming is currently limited to glibc linkage.
> > musl libc [5] also provides Posix AIO API implementation, however
> > the patchkit is not tested with it. There may be other libc libraries
> > linked by Perf tool that currently lack Posix AIO API support [2],
> > [3], [4] so NO_AIO define may be used to limit Perf tool binary to
> > serial streaming only.
> >
> > ---
> > Alexey Budankov (3):
> > perf util: map data buffer for preserving collected data
> > perf record: enable asynchronous trace writing
> > perf record: extend trace writing to multi AIO
>
> FYI I was rebasing my threads branch on top of this and
> first 2 won't apply anymore on Arnaldo's perf/core
>
> Arnaldo,
> could we get this merged soon? the world around is moving
> fast and we don't want 20th revision on this ;-)
I think I gave my ack to this already too.
Thanks,
Namhyung
prev parent reply other threads:[~2018-11-13 2:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 8:53 [PATCH v15 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads Alexey Budankov
2018-11-06 9:03 ` [PATCH v15 1/3]: perf util: map data buffer for preserving collected data Alexey Budankov
2018-12-14 20:28 ` [tip:perf/core] tools build feature: Check if libaio is available tip-bot for Alexey Budankov
2018-12-14 20:28 ` [tip:perf/core] perf mmap: Map data buffer for preserving collected data tip-bot for Alexey Budankov
2018-12-18 13:55 ` [tip:perf/core] tools build feature: Check if libaio is available tip-bot for Alexey Budankov
2018-12-18 13:55 ` [tip:perf/core] perf mmap: Map data buffer for preserving collected data tip-bot for Alexey Budankov
2018-11-06 9:04 ` [PATCH v15 2/3]: perf record: enable asynchronous trace writing Alexey Budankov
2018-12-14 20:29 ` [tip:perf/core] perf record: Enable " tip-bot for Alexey Budankov
2018-12-18 13:56 ` tip-bot for Alexey Budankov
2018-11-06 9:07 ` [PATCH v15 3/3]: perf record: extend trace writing to multi AIO Alexey Budankov
2018-12-14 20:30 ` [tip:perf/core] perf record: Extend " tip-bot for Alexey Budankov
2018-12-18 13:57 ` tip-bot for Alexey Budankov
2018-11-09 8:22 ` [PATCH v15 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads Jiri Olsa
2018-11-09 17:29 ` Alexey Budankov
2018-11-13 2:47 ` Namhyung Kim [this message]
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=20181113024716.GA27910@sejong \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox