lkml.org 
[lkml]   [2017]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default
On Wed, Oct 18, 2017 at 12:09:44PM +0200, Ingo Molnar wrote:
> BTW., have you attempted limiting the depth of the stack traces? I suspect more
> than 2-4 are rarely required to disambiguate the calling context.

I did it for you. Let me show you the result.

1. No lockdep

Performance counter stats for 'qemu_booting_time.sh bzImage' (10 runs):

2.756558155 seconds time elapsed ( +- 0.09% )

2. Lockdep

Performance counter stats for 'qemu_booting_time.sh bzImage' (10 runs):

2.968710420 seconds time elapsed ( +- 0.12% )

3. Lockdep + Crossrelease 5 entries

Performance counter stats for 'qemu_booting_time.sh bzImage' (10 runs):

3.153839636 seconds time elapsed ( +- 0.31% )

4. Lockdep + Crossrelease 3 entries

Performance counter stats for 'qemu_booting_time.sh bzImage' (10 runs):

3.137205534 seconds time elapsed ( +- 0.87% )

5. Lockdep + Crossrelease + This patch

Performance counter stats for 'qemu_booting_time.sh bzImage' (10 runs):

2.963669551 seconds time elapsed ( +- 0.11% )

And I will add the result in commit message at the next spin.

Thanks,
Byungchul

\
 
 \ /
  Last update: 2017-10-22 17:20    [W:0.103 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site