From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.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>
Subject: Re: [PATCH v3 2/2]: perf record: enable asynchronous trace writing
Date: Tue, 28 Aug 2018 12:39:33 +0300 [thread overview]
Message-ID: <e75ae90b-2ea6-0047-2045-31609c17db47@linux.intel.com> (raw)
In-Reply-To: <20180828085022.GE23727@krava>
Hi,
On 28.08.2018 11:50, Jiri Olsa wrote:
> On Mon, Aug 27, 2018 at 09:16:55PM +0300, Alexey Budankov wrote:
>>
>> Trace file offset are linearly calculated by perf_mmap__push() code
>> for the next possible write operation, but file position is updated by
>> the kernel only in the second lseek() syscall after the loop.
>> The first lseek() syscall reads that file position for
>> the next loop iterations.
>>
>> record__mmap_read_sync implements sort of a barrier between spilling
>> ready profiling data to disk.
>>
>> Signed-off-by: Alexey Budankov <alexey.budankov@linux.intel.com>
>> ---
>> Changes in v3:
>> - written comments about nanosleep(0.5ms) call prior aio_suspend()
>> to cope with intrusiveness of its implementation in glibc;
>> - written comments about rationale behind coping profiling data
>> into mmap->data buffer;
>> ---
>> tools/perf/builtin-record.c | 125 +++++++++++++++++++++++++++++++++++++++++---
>> tools/perf/util/mmap.c | 36 ++++++++-----
>> tools/perf/util/mmap.h | 2 +-
>> 3 files changed, 143 insertions(+), 20 deletions(-)
>>
>> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
>> index 22ebeb92ac51..4ac61399a09a 100644
>> --- a/tools/perf/builtin-record.c
>> +++ b/tools/perf/builtin-record.c
>> @@ -53,6 +53,7 @@
>> #include <sys/mman.h>
>> #include <sys/wait.h>
>> #include <linux/time64.h>
>> +#include <aio.h>
>>
>> struct switch_output {
>> bool enabled;
>> @@ -121,6 +122,23 @@ static int record__write(struct record *rec, void *bf, size_t size)
>> return 0;
>> }
>>
>> +static int record__aio_write(int trace_fd, struct aiocb *cblock,
>> + void *buf, size_t size, off_t off)
>> +{
>> + cblock->aio_fildes = trace_fd;
>> + cblock->aio_buf = buf;
>> + cblock->aio_nbytes = size;
>> + cblock->aio_offset = off;
>> + cblock->aio_sigevent.sigev_notify = SIGEV_NONE;
>> +
>> + if (aio_write(cblock) == -1) {
>> + pr_err("failed to queue perf data, error: %m\n");
>> + return -1;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> static int process_synthesized_event(struct perf_tool *tool,
>> union perf_event *event,
>> struct perf_sample *sample __maybe_unused,
>> @@ -130,12 +148,14 @@ static int process_synthesized_event(struct perf_tool *tool,
>> return record__write(rec, event, event->header.size);
>> }
>>
>> -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;
>
> the argument needs to change for record__pushfn,
> now with your changes, it's no longer 'void *bf',
> but 'struct perf_mmap *map'
Ok. Included into [PATCH v4 2/2].
>
> also I'm little confused why we have '*to' and cast
> it back to 'struct record', but so be it ;-)
Supported. :)
>
> thanks,
> jirka
>
next prev parent reply other threads:[~2018-08-28 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bdd669cd-a6dc-d592-4655-33b7bfc46cbb@linux.intel.com>
2018-08-27 18:16 ` [PATCH v3 1/2]: perf util: map data buffer for preserving collected data Alexey Budankov
2018-08-27 18:16 ` [PATCH v3 2/2]: perf record: enable asynchronous trace writing Alexey Budankov
2018-08-28 8:50 ` Jiri Olsa
2018-08-28 9:39 ` Alexey Budankov [this message]
2018-08-28 8:53 ` Jiri Olsa
2018-08-28 10:28 ` Alexey Budankov
2018-08-28 8:57 ` Jiri Olsa
2018-08-28 11:31 ` Alexey Budankov
2018-08-28 12:21 ` Jiri Olsa
2018-08-28 9:01 ` Jiri Olsa
2018-08-28 12:37 ` Alexey Budankov
2018-08-28 8:59 ` [PATCH v3 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads Jiri Olsa
2018-08-28 11:58 ` Alexey Budankov
2018-08-28 14:17 ` Alexey Budankov
2018-08-28 14:08 ` 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=e75ae90b-2ea6-0047-2045-31609c17db47@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=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