From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 2/2]: perf record: enable asynchronous trace writing
Date: Mon, 27 Aug 2018 12:20:50 +0300 [thread overview]
Message-ID: <3a8286ff-124f-fb56-1d1c-5d5e1f3b8512@linux.intel.com> (raw)
In-Reply-To: <20180826214856.GA24518@krava>
Hi,
On 27.08.2018 0:48, Jiri Olsa wrote:
> On Tue, Aug 21, 2018 at 11:27:03AM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> -static int record__pushfn(void *to, void *bf, size_t size)
>> +static int record__pushfn(void *to, void *bf, size_t size, off_t off)
>> {
>> struct record *rec = to;
>> + struct perf_mmap *map = bf;
>>
>> rec->samples++;
>> - return record__write(rec, bf, size);
>> + return record__aio_write(rec->session->data->file.fd, &map->cblock,
>> + map->data, size, off);
>> }
>>
>> static volatile int done;
>> @@ -528,13 +530,85 @@ static struct perf_event_header finished_round_event = {
>> .type = PERF_RECORD_FINISHED_ROUND,
>> };
>>
>> +static int record__mmap_read_sync(int trace_fd, struct aiocb **cblocks,
>> + int cblocks_size, struct record *rec)
>> +{
>> + size_t rem;
>> + ssize_t size;
>> + off_t rem_off;
>> + int i, aio_ret, aio_errno, do_suspend;
>> + struct perf_mmap *md;
>> + struct timespec timeout0 = { 0, 0 };
>> + struct timespec timeoutS = { 0, 1000 * 500 * 1 };
>> +
>> + if (!cblocks_size)
>> + return 0;
>> +
>> + do {
>> + do_suspend = 0;
>> + nanosleep(&timeoutS, NULL);
>
> why the extra sleep in here and not sleeping through aio_suspend call?
Yep. Good question. That requires explicit explanation:
+ /* aio_suspend() implementation inside glibc (as of v2.27) is
+ * intrusive and not just blocks waiting io requests completion
+ * but polls requests queue inducing context switches in perf
+ * tool process. When profiling in system wide mode with tracing
+ * context switches the trace may be polluted by context switches
+ * from the perf process and the trace size becomes about 3-5
+ * times bigger than that of when writing the trace serially.
+ * To limit the volume of context switches from perf tool
+ * process nonsleep() call limits aio_suspend()
+ * polling till every half of the kernel timer tick which is
+ * usually 1ms (depends on CONFIG_HZ value).
+ */
>
> jirka
>
>> + if (aio_suspend((const struct aiocb**)cblocks, cblocks_size, &timeout0)) {
>> + if (errno == EAGAIN || errno == EINTR) {
>> + do_suspend = 1;
>> + continue;
>> + } else {
>> + pr_err("failed to sync perf data, error: %m\n");
>
> SNIP
>
next prev parent reply other threads:[~2018-08-27 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 8:22 [PATCH v1 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads Alexey Budankov
2018-08-21 8:25 ` [PATCH v1 1/2]: perf util: map data buffer for preserving collected data Alexey Budankov
2018-08-21 8:27 ` [PATCH v1 2/2]: perf record: enable asynchronous trace writing Alexey Budankov
2018-08-26 21:48 ` Jiri Olsa
2018-08-27 9:20 ` Alexey Budankov [this message]
2018-08-23 10:26 [PATCH v1 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads Alexey Budankov
2018-08-23 10:31 ` [PATCH v1 2/2]: perf record: enable asynchronous trace writing Alexey Budankov
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=3a8286ff-124f-fb56-1d1c-5d5e1f3b8512@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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
Powered by JetHome