Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Logging the accesses
|January 2021
|First public release
|-
|2.0.0
|January 2022
|Added the section "Example: embedded Linux system equipped with SanDisk SDINBDG4-8G-XI1 eMMC and <code>ext4</code> file system"
|}
=Introduction=
! colspan="2" |vmlinux data size
! colspan="2" |vmlinux source files
!rowspan="2" |instrumentation code size (*)!rowspan="2" |instrumentation data size (*)
|-
!Asbolute
[MByte]
!Change Increment w.r.t. the "Clean" setupbaseline
[%]
!Absolute
[MByte]
!Change Increment w.r.t. the "Clean" baseline setup
[%]
!#
!Change Increment w.r.t. the "Clean" baseline setup!instrumentation code size (*)!instrumentation data size (*)
|-
|Baseline
(**) the actual size of the <code>ftrace</code> ring buffer can be configured during runtime but is typically in the 10—100 MByte range .
In the ftrace-based solution, an increase in kernel size of approximately 15% (code) and 9% (data) is observed compared to the kernel without ftrace. During the execution of ftrace it’s also necessary to reserve additional memory for the ring buffer. The number of source files used in building the kernel increases by 18% when the ftrace framework is included. The weight of the instrumentation required by TRACE32, on the other hand, is practically negligible both in terms of code and data.
==== Conclusion ====
