On Thu, Nov 10, 2016 at 4:16 PM, Joel Fernandes wrote:
> On Thu, Nov 10, 2016 at 4:13 PM, Kees Cook wrote:
>> On Thu, Oct 20, 2016 at 12:34 AM, Joel Fernandes wrote:
>>> If FTRACE_PER_CPU flag is passed to ramoops pdata, split the space into
>>> multiple zones depending on the number of CPUs.
>>
On Thu, Nov 10, 2016 at 4:13 PM, Kees Cook wrote:
> On Thu, Oct 20, 2016 at 12:34 AM, Joel Fernandes wrote:
>> If FTRACE_PER_CPU flag is passed to ramoops pdata, split the space into
>> multiple zones depending on the number of CPUs.
>>
>> This speeds up the performance of function tracing by abo
On Thu, Oct 20, 2016 at 12:34 AM, Joel Fernandes wrote:
> If FTRACE_PER_CPU flag is passed to ramoops pdata, split the space into
> multiple zones depending on the number of CPUs.
>
> This speeds up the performance of function tracing by about 280% in my tests
> as
> we avoid the locking. The tra
If FTRACE_PER_CPU flag is passed to ramoops pdata, split the space into
multiple zones depending on the number of CPUs.
This speeds up the performance of function tracing by about 280% in my tests as
we avoid the locking. The trade off being lesser space available per CPU. Let
the ramoops user de
4 matches
Mail list logo
