Re: [PATCH v7 02/12] perf record: implement -f,--mmap-flush= option

2019-03-13 Thread Alexey Budankov
On 13.03.2019 17:36, Jiri Olsa wrote: > On Tue, Mar 12, 2019 at 08:12:23AM +0300, Alexey Budankov wrote: > > SNIP > >> record__aio_mmap_read_sync(rec); >> >> if (forks) { >> @@ -1815,6 +1863,7 @@ static struct record record = { >> .uses_mmap = true, >>

Re: [PATCH v7 02/12] perf record: implement -f,--mmap-flush= option

2019-03-13 Thread Jiri Olsa
On Tue, Mar 12, 2019 at 08:12:23AM +0300, Alexey Budankov wrote: SNIP > record__aio_mmap_read_sync(rec); > > if (forks) { > @@ -1815,6 +1863,7 @@ static struct record record = { > .uses_mmap = true, > .default_per_cpu = true, >

[PATCH v7 02/12] perf record: implement -f,--mmap-flush= option

2019-03-11 Thread Alexey Budankov
Implemented -f,--mmap-flush option that specifies minimal size of data chunk that is extracted from mmaped kernel buffer to store into a trace. The default option value is 1 byte what means every time trace writing thread finds some new data in the mmaped buffer the data is extracted, possibly