CONFIG_TRACEPOINT_BENCHMARK: Add tracepoint that benchmarks tracepoints

General informations

The Linux kernel configuration item CONFIG_TRACEPOINT_BENCHMARK:

• prompt: Add tracepoint that benchmarks tracepoints
• type: bool
• depends on: (none)
• defined in kernel/trace/Kconfig
• found in Linux kernels: 3.16–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

This option creates the tracepoint "benchmark:benchmark_event". When the tracepoint is enabled, it kicks off a kernel thread that goes into an infinite loop (calling cond_resched() to let other tasks run), and calls the tracepoint. Each iteration will record the time it took to write to the tracepoint and the next iteration that data will be passed to the tracepoint itself. That is, the tracepoint will report the time it took to do the previous tracepoint. The string written to the tracepoint is a static string of 128 bytes to keep the time the same. The initial string is simply a write of "START". The second string records the cold cache time of the first write which is not added to the rest of the calculations.

As it is a tight loop, it benchmarks as hot cache. That's fine because we care most about hot paths that are probably in cache already.

An example of the output:

START first=3672 [COLD CACHED] last=632 first=3672 max=632 min=632 avg=316 std=446 std^2=199712 last=278 first=3672 max=632 min=278 avg=303 std=316 std^2=100337 last=277 first=3672 max=632 min=277 avg=296 std=258 std^2=67064 last=273 first=3672 max=632 min=273 avg=292 std=224 std^2=50411 last=273 first=3672 max=632 min=273 avg=288 std=200 std^2=40389 last=281 first=3672 max=632 min=273 avg=287 std=183 std^2=33666

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: