Home
last modified time | relevance | path

Searched refs:benchmark (Results 1 – 25 of 37) sorted by relevance

12

/linux-6.3-rc2/tools/testing/selftests/resctrl/
A DREADME62 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-6.3-rc2/Documentation/devicetree/bindings/cpu/
A Dcpu-capacity.txt25 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-6.3-rc2/tools/power/cpupower/bench/
A DMakefile11 OBJS = $(OUTPUT)main.o $(OUTPUT)parse.o $(OUTPUT)system.o $(OUTPUT)benchmark.o \
15 OBJS = $(OUTPUT)main.o $(OUTPUT)parse.o $(OUTPUT)system.o $(OUTPUT)benchmark.o
A DREADME-BENCH6 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-6.3-rc2/tools/testing/selftests/bpf/progs/
A Dbpf_loop_bench.c19 int benchmark(void *ctx) in benchmark() function
A Dbpf_hashmap_full_update_bench.c31 int benchmark(void *ctx) in benchmark() function
A Dbpf_hashmap_lookup.c51 int benchmark(void *ctx) in benchmark() function
/linux-6.3-rc2/tools/perf/Documentation/
A Dperf-bench.txt6 perf-bench - General framework for benchmark suites
15 This 'perf bench' command is a general framework for benchmark suites.
71 All benchmark subsystems.
/linux-6.3-rc2/kernel/trace/
A Dtrace_benchmark.h3 #define TRACE_SYSTEM benchmark
A DKconfig840 This option creates the tracepoint "benchmark:benchmark_event".
868 tristate "Ring buffer benchmark stress tester"
871 This option creates a test to stress the ring buffer and benchmark it.
/linux-6.3-rc2/samples/pktgen/
A DREADME.rst1 Sample and benchmark scripts for pktgen (packet generator)
3 This directory contains some pktgen sample and benchmark scripts, that
/linux-6.3-rc2/tools/testing/selftests/bpf/benchs/
A Dbench_bpf_loop.c87 link = bpf_program__attach(ctx.skel->progs.benchmark); in setup()
A Dbench_bpf_hashmap_full_update.c57 link = bpf_program__attach(ctx.skel->progs.benchmark); in setup()
A Dbench_bpf_hashmap_lookup.c198 link = bpf_program__attach(ctx.skel->progs.benchmark); in setup()
/linux-6.3-rc2/tools/testing/radix-tree/
A Dtest.h38 void benchmark(void);
A DMakefile12 iteration_check_2.o benchmark.o
A Dbenchmark.c137 void benchmark(void) in benchmark() function
A Dmain.c320 benchmark(); in main()
/linux-6.3-rc2/drivers/gpu/drm/radeon/
A Dradeon_drv.c197 MODULE_PARM_DESC(benchmark, "Run benchmark");
198 module_param_named(benchmark, radeon_benchmarking, int, 0444);
/linux-6.3-rc2/arch/arm/mm/
A Dproc-arm740.S111 @ need some benchmark
/linux-6.3-rc2/Documentation/admin-guide/pm/
A Dintel-speed-select.rst592 # 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:
A Damd-pstate.rst508 Test and monitor the cpu changes when running tbench benchmark under the specified governor.
515 … Test and monitor the cpu changes when running gitsource benchmark under the specified governor.
/linux-6.3-rc2/arch/arm/probes/kprobes/
A Dtest-core.c503 static int benchmark(void(*fn)(void)) in benchmark() function
531 ret = benchmark(fn); in kprobe_benchmark()
/linux-6.3-rc2/Documentation/admin-guide/
A Dreporting-regressions.rst239 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
/linux-6.3-rc2/Documentation/networking/device_drivers/ethernet/intel/
A Dixgb.rst255 # several network benchmark tests, your mileage may vary

Completed in 40 milliseconds

12