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 v2 2/2]: perf record: enable asynchronous trace writing
Date: Mon, 27 Aug 2018 12:45:38 +0300 [thread overview]
Message-ID: <2c525930-fbfd-2ea7-0b80-b67eff9b44cf@linux.intel.com> (raw)
In-Reply-To: <20180827084333.GG24695@krava>
Hi,
On 27.08.2018 11:43, Jiri Olsa wrote:
> On Thu, Aug 23, 2018 at 07:47:01PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>>
>> 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 * 1000 * 1 };
>> +
>> + if (!cblocks_size)
>> + return 0;
>> +
>> + do {
>> + do_suspend = 0;
>> + nanosleep(&timeoutS, NULL);
>> + 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");
>> + break;
>> + }
>> + }
>> + for (i = 0; i < cblocks_size; i++) {
>
> it looks like we could set up the async write to receive the signal
> with the user pointer (sigev_value.sival_ptr), which would allow us
> to get the finished descriptor right away and we wouldn't need
> to iterate all of them and checking on them
Yep. This mechanism is provided by AIO API, but we still need this kind of
synchronizing barrier to avoid memory races on mmap->data buffer between
calls of the loop in record__mmap_read_evlist().
>
> jirka
>> + if (cblocks[i] == NULL) {
>> + continue;
>> + }
>> + aio_errno = aio_error(cblocks[i]);
>> + if (aio_errno == EINPROGRESS) {
>> + do_suspend = 1;
>> + continue;
>> + }
>
> SNIP
>
prev parent reply other threads:[~2018-08-27 9:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 16:33 [PATCH v2 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads Alexey Budankov
2018-08-23 16:42 ` [PATCH v2 1/2]: perf util: map data buffer for preserving collected data Alexey Budankov
2018-08-27 8:28 ` Jiri Olsa
2018-08-27 8:58 ` Alexey Budankov
2018-08-27 8:33 ` Jiri Olsa
2018-08-27 9:02 ` Alexey Budankov
2018-08-28 8:45 ` Jiri Olsa
2018-08-28 9:19 ` Alexey Budankov
2018-08-23 16:47 ` [PATCH v2 2/2]: perf record: enable asynchronous trace writing Alexey Budankov
2018-08-27 8:34 ` Jiri Olsa
2018-08-27 9:12 ` Alexey Budankov
2018-08-27 8:38 ` Jiri Olsa
2018-08-27 9:33 ` Alexey Budankov
2018-08-27 10:05 ` Namhyung Kim
2018-08-27 10:25 ` Alexey Budankov
2018-08-27 10:38 ` Jiri Olsa
2018-08-27 10:48 ` Alexey Budankov
2018-08-27 8:43 ` Jiri Olsa
2018-08-27 9:45 ` Alexey Budankov [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=2c525930-fbfd-2ea7-0b80-b67eff9b44cf@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