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
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
On Sun, Oct 16, 2016 at 10:40 AM, Joel Fernandes wrote:
> Hi Kees,
>
> On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
>> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>>> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes
On Sun, Oct 16, 2016 at 10:40 AM, Joel Fernandes wrote:
> Hi Kees,
>
> On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
>> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>>> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes wrote:
If FTRACE_PER_CPU flag is passed to ramoops pdata,
Hi Kees,
On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes wrote:
>>> If FTRACE_PER_CPU flag is passed to ramoops pdata,
Hi Kees,
On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes wrote:
>>> If FTRACE_PER_CPU flag is passed to ramoops pdata, split the space into
>>> multiple zones depending on the number
On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes wrote:
>>> If FTRACE_PER_CPU flag is passed to ramoops pdata, split the
On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>> On Fri, Oct 7, 2016 at 10:28 PM, 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 Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
> On Fri, Oct 7, 2016 at 10:28 PM, 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
On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
> On Fri, Oct 7, 2016 at 10:28 PM, 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
On Fri, Oct 7, 2016 at 10:28 PM, 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
On Fri, Oct 7, 2016 at 10:28 PM, 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
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
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
14 matches
Mail list logo