diff options
author | Daniel Bristot de Oliveira <bristot@kernel.org> | 2023-06-06 19:12:19 +0300 |
---|---|---|
committer | Steven Rostedt (Google) <rostedt@goodmis.org> | 2023-06-13 23:31:35 +0300 |
commit | c66552be9ec9f83705a911cb2219cffc39c42a0c (patch) | |
tree | 894317667eac682e68096b88a312db732941dfb5 /Documentation/tools/rtla/rtla-timerlat-hist.rst | |
parent | c58a3f8c7f974d171d1b6897a71a078a3bc7afd3 (diff) | |
download | linux-c66552be9ec9f83705a911cb2219cffc39c42a0c.tar.xz |
rtla/timerlat: Give timerlat auto analysis its own instance
Currently, the auto-analysis is attached to the timerlat top instance.
The idea was to avoid creating another instance just for that, so one
instance could be reused.
The drawback is that, by doing so, the auto-analysis run for the entire
session, consuming CPU time. On my 24 box CPUs for timerlat with a 100
us period consumed 50 % with auto analysis, but only 16 % without.
By creating an instance for auto-analysis, we can keep the processing
stopped until a stop tracing condition is hit. Once it happens,
timerlat auto-analysis can use its own trace instance to parse only
the end of the trace.
By doing so, auto-analysis stop consuming cpu time when it is not
needed.
If the --aa-only is passed, the timerlat top instance is reused for
auto analysis.
Link: https://lkml.kernel.org/r/346b7168c1bae552a415715ec6d23c129a43bdb7.1686066600.git.bristot@kernel.org
Cc: William White <chwhite@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Tested-by: Juri Lelli <juri.lelli@redhat.com>
Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'Documentation/tools/rtla/rtla-timerlat-hist.rst')
0 files changed, 0 insertions, 0 deletions