[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ea7651bc-0ea9-bdf8-f595-cf42dba4314d@linux.intel.com>
Date: Wed, 20 Feb 2019 18:19:49 +0300
From: Alexey Budankov <alexey.budankov@...ux.intel.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Andi Kleen <ak@...ux.intel.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/4] perf record: implement -z=<level> and
--mmap-flush=<thres> options
On 12.02.2019 16:09, Jiri Olsa wrote:
> On Mon, Feb 11, 2019 at 11:22:38PM +0300, Alexey Budankov wrote:
>>
>> Implement -z,--compression_level=<n> and --mmap-flush=<dump_least_size>
>> options as well as a special PERF_RECORD_COMPRESSED record that contains
>> compressed parts of kernel data buffer.
>>
>> Because compression requires auxilary memory to implement encoding of
>> kernel data record->opts.nr_cblocks == -1 signifies to preallocate single
>> AIO data buffer aio.data[0] without accompnying AIO control blocks.
>>
>> Signed-off-by: Alexey Budankov <alexey.budankov@...ux.intel.com>
>> ---
>> Changes in v2:
>> - enabled allocation aio data buffers for compression
>>
>> ---
>> tools/perf/Documentation/perf-record.txt | 9 ++
>> tools/perf/builtin-record.c | 110 +++++++++++++++++++----
>> tools/perf/perf.h | 2 +
>> tools/perf/util/env.h | 10 +++
>> tools/perf/util/event.c | 1 +
>> tools/perf/util/event.h | 7 ++
>> tools/perf/util/evlist.c | 6 +-
>> tools/perf/util/evlist.h | 3 +-
>> tools/perf/util/header.c | 45 +++++++++-
>> tools/perf/util/header.h | 1 +
>> tools/perf/util/mmap.c | 98 ++++++++++++--------
>> tools/perf/util/mmap.h | 7 +-
>> tools/perf/util/session.h | 2 +
>> 13 files changed, 240 insertions(+), 61 deletions(-)
>
> this patch is super complicated.. please think of reviewers
> when writing code ;-)
>
> it needs to be split to small logical patches,
> where each change is explained in changelog
Yes, Will do.
Thanks,
Alexey
>
> jirka
>
Powered by blists - more mailing lists