Searched refs:benchmark (Results 1 – 25 of 28) sorted by relevance
12
/Linux-v4.19/tools/power/cpupower/bench/ |
D | Makefile | 11 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
|
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-v4.19/Documentation/devicetree/bindings/arm/ |
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-v4.19/samples/pktgen/ |
D | README.rst | 1 Sample and benchmark scripts for pktgen (packet generator) 3 This directory contains some pktgen sample and benchmark scripts, that
|
/Linux-v4.19/tools/perf/Documentation/ |
D | perf-bench.txt | 6 perf-bench - General framework for benchmark suites 15 This 'perf bench' command is a general framework for benchmark suites. 62 All benchmark subsystems.
|
/Linux-v4.19/kernel/trace/ |
D | trace_benchmark.h | 3 #define TRACE_SYSTEM benchmark
|
D | Kconfig | 661 This option creates the tracepoint "benchmark:benchmark_event". 689 tristate "Ring buffer benchmark stress tester" 692 This option creates a test to stress the ring buffer and benchmark it.
|
/Linux-v4.19/tools/testing/radix-tree/ |
D | test.h | 40 void benchmark(void);
|
D | Makefile | 10 tag_check.o multiorder.o idr-test.o iteration_check.o benchmark.o
|
D | benchmark.c | 233 void benchmark(void) in benchmark() function
|
D | main.c | 378 benchmark(); in main()
|
/Linux-v4.19/drivers/gpu/drm/radeon/ |
D | radeon_drv.c | 226 MODULE_PARM_DESC(benchmark, "Run benchmark"); 227 module_param_named(benchmark, radeon_benchmarking, int, 0444);
|
/Linux-v4.19/arch/arm/mm/ |
D | proc-arm740.S | 115 @ need some benchmark
|
/Linux-v4.19/arch/arm/probes/kprobes/ |
D | test-core.c | 506 static int benchmark(void(*fn)(void)) in benchmark() function 534 ret = benchmark(fn); in kprobe_benchmark()
|
/Linux-v4.19/drivers/gpu/drm/amd/amdgpu/ |
D | amdgpu_drv.c | 170 MODULE_PARM_DESC(benchmark, "Run benchmark"); 171 module_param_named(benchmark, amdgpu_benchmarking, int, 0444);
|
/Linux-v4.19/tools/perf/ |
D | Makefile.config | 763 …msg := $(warning No numa.h found, disables 'perf bench numa mem' benchmark, please install numactl… 767 …msg := $(warning Old numa library found, disables 'perf bench numa mem' benchmark, please install …
|
/Linux-v4.19/Documentation/networking/ |
D | af_xdp.rst | 290 Running the rxdrop benchmark in XDP_DRV mode can then be done
|
D | ixgb.txt | 214 # several network benchmark tests, your mileage may vary
|
/Linux-v4.19/arch/alpha/ |
D | Kconfig | 621 as benchmark-grade in-kernel web serving) that can make use of as
|
/Linux-v4.19/mm/ |
D | Kconfig | 604 You can check speed with zsmalloc benchmark:
|
/Linux-v4.19/Documentation/filesystems/ext4/ |
D | ext4.rst | 60 for a fair comparison. When tuning ext3 for best benchmark numbers,
|
/Linux-v4.19/Documentation/admin-guide/ |
D | bcache.rst | 351 But if you want to benchmark reads from cache, and you start out with fio
|
/Linux-v4.19/Documentation/ |
D | kprobes.txt | 656 microseconds to process. Specifically, a benchmark that hits the same
|
/Linux-v4.19/lib/ |
D | Kconfig.debug | 1747 A benchmark measuring the performance of the rbtree library. 1755 A benchmark measuring the performance of the interval tree library
|
/Linux-v4.19/Documentation/x86/ |
D | intel_rdt_ui.txt | 354 this would be dependent on number of cores the benchmark is run on.
|
12