| /linux/Documentation/devicetree/bindings/cpu/ |
| H A D | cpu-capacity.txt | 25 CPU capacities are obtained by running a suitable benchmark. This binding makes 26 no guarantees on the validity or suitability of any particular benchmark, the 29 * A "single-threaded" or CPU affine benchmark 30 * Divided by the running frequency of the CPU executing the benchmark 33 For the time being we however advise usage of the Dhrystone benchmark. What 36 CPU capacities are obtained by running the Dhrystone benchmark on each CPU at 38 by the frequency (in MHz) at which the benchmark has been run, so that
|
| /linux/tools/testing/selftests/resctrl/ |
| H A D | README | 62 process pids to tasks, start benchmark. 63 - execute: let benchmark run 74 …-b benchmark_cmd [options]: run specified benchmark for MBM, MBA and CMT default benchmark is buil…
|
| /linux/tools/power/cpupower/bench/ |
| H A D | Makefile | 16 OBJS = $(OUTPUT)main.o $(OUTPUT)parse.o $(OUTPUT)system.o $(OUTPUT)benchmark.o \ 20 OBJS = $(OUTPUT)main.o $(OUTPUT)parse.o $(OUTPUT)system.o $(OUTPUT)benchmark.o
|
| H A D | README-BENCH | 6 What is this benchmark for: 17 What this benchmark does *not* cover: 123 After the benchmark, the logfile is saved in OUTPUTDIR/benchmark_TIMESTAMP.log
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-bench.txt | 6 perf-bench - General framework for benchmark suites 15 This 'perf bench' command is a general framework for benchmark suites. 74 All benchmark subsystems. 155 # Running 'sched/pipe' benchmark:
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | bpf_loop_bench.c | 26 int benchmark(void *ctx) in benchmark() function
|
| H A D | bpf_hashmap_full_update_bench.c | 31 int benchmark(void *ctx) in benchmark() function
|
| H A D | bpf_hashmap_lookup.c | 51 int benchmark(void *ctx) in benchmark() function
|
| /linux/samples/pktgen/ |
| H A D | README.rst | 1 Sample and benchmark scripts for pktgen (packet generator) 3 This directory contains some pktgen sample and benchmark scripts, that
|
| /linux/kernel/trace/ |
| H A D | trace_benchmark.h | 3 #define TRACE_SYSTEM benchmark
|
| H A D | Kconfig | 975 This option creates the tracepoint "benchmark:benchmark_event". 1003 tristate "Ring buffer benchmark stress tester" 1006 This option creates a test to stress the ring buffer and benchmark it.
|
| /linux/tools/testing/radix-tree/ |
| H A D | Makefile | 9 iteration_check.o iteration_check_2.o benchmark.o
|
| H A D | test.h | 38 void benchmark(void);
|
| H A D | benchmark.c | 137 void benchmark(void) in benchmark() function
|
| H A D | main.c | 320 benchmark(); in main()
|
| /linux/tools/testing/selftests/bpf/benchs/ |
| H A D | bench_bpf_loop.c | 82 link = bpf_program__attach(ctx.skel->progs.benchmark); in setup()
|
| H A D | bench_bpf_hashmap_full_update.c | 52 link = bpf_program__attach(ctx.skel->progs.benchmark); in setup()
|
| H A D | bench_bpf_hashmap_lookup.c | 193 link = bpf_program__attach(ctx.skel->progs.benchmark); in setup()
|
| /linux/Documentation/gpu/ |
| H A D | panfrost.rst | 43 because of power saving concerns. `fdinfo` users and benchmark applications which
|
| /linux/arch/arm/mm/ |
| H A D | proc-arm740.S | 123 @ need some benchmark
|
| /linux/lib/crypto/tests/ |
| H A D | Kconfig | 112 The benchmark results are printed to the kernel log when the
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel-speed-select.rst | 592 # Running 'sched/pipe' benchmark: 692 # Running 'sched/pipe' benchmark: 698 This way, by enabling Intel(R) SST-BF, the performance of this benchmark is 812 # Running 'sched/pipe' benchmark: 925 # Running 'sched/pipe' benchmark:
|
| H A D | amd-pstate.rst | 607 Test and monitor the cpu changes when running tbench benchmark under the specified governor. 614 … Test and monitor the cpu changes when running gitsource benchmark under the specified governor.
|
| /linux/arch/arm/probes/kprobes/ |
| H A D | test-core.c | 503 static int benchmark(void(*fn)(void)) in benchmark() function 531 ret = benchmark(fn); in kprobe_benchmark()
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-regressions.rst | 239 micro-benchmark thus is unlikely to qualify as regression, unless it also 240 influences the results of a broad benchmark by more than one percent. If in
|