lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 28 Feb 2019 23:19:44 +0300
From:   Alexey Budankov <>
To:     Arnaldo Carvalho de Melo <>
Cc:     Jiri Olsa <>, Namhyung Kim <>,
        Alexander Shishkin <>,
        Peter Zijlstra <>,
        Ingo Molnar <>,
        Andi Kleen <>,
        linux-kernel <>
Subject: Re: [PATCH v4 02/10] perf record: implement
 -f,--mmap-flush=<threshold> option

On 28.02.2019 21:44, Arnaldo Carvalho de Melo wrote:
> Em Thu, Feb 28, 2019 at 12:00:41PM +0300, Alexey Budankov escreveu:
>> Implemented -f,--mmap-flush option that specifies threshold to postpone
>> and/or trigger the move of data from mmaped kernel buffers to a storage.
>> The option can be used to avoid capturing every single byte of data into
>> the stored trace. The default option value is 1.
> Can you add something here explain more clearly what this means, and
> also on the tools/perf/Documentation/perf-record.txt file? Something
> like a paragraph explaining when is that there is a mmap flush normally,
> or rephrase what you wrote if you think you said that.

Will try to rephrase and may be provide some description of 
cases that this option can specifically address.


> - Arnaldo

Powered by blists - more mailing lists