Home
last modified time | relevance | path

Searched refs:benchmarks (Results 1 – 18 of 18) sorted by relevance

/linux/tools/perf/
H A Dbuiltin-bench.c121 struct bench *benchmarks; member
148 for (bench = coll->benchmarks; bench && bench->name; bench++)
/linux/lib/crypto/tests/
H A DKconfig108 bool "Include benchmarks in KUnit tests for cryptographic functions"
111 Include benchmarks in the KUnit tests for cryptographic functions.
/linux/tools/perf/Documentation/
H A Dperf-bench.txt59 NUMA scheduling and MM benchmarks.
62 Futex stressing benchmarks.
65 Eventpoll (epoll) stressing benchmarks.
/linux/tools/testing/selftests/powerpc/
H A DMakefile11 benchmarks \
/linux/arch/arm/probes/kprobes/
H A Dtest-core.c537 struct benchmarks { struct
546 struct benchmarks list[] = { in run_benchmarks() argument
568 struct benchmarks *b; in run_benchmarks()
/linux/lib/crc/
H A DKconfig119 Include benchmarks in the KUnit test suite for the CRC functions.
/linux/arch/arm/boot/dts/broadcom/
H A Dbcm2837.dtsi47 * https://magpi.raspberrypi.com/articles/raspberry-pi-3-specs-benchmarks
/linux/Documentation/arch/arm/nwfpe/
H A Dtodo.rst47 This has made porting some benchmarks difficult. It is possible to
/linux/Documentation/admin-guide/
H A Dworkload-tracing.rst110 benchmarks for executing different subsystems in the Linux kernel and
240 benchmarks for executing different subsystems in the Linux kernel and
246 "perf bench all" command runs the following benchmarks:
H A Dkernel-parameters.txt2249 benchmarks. It also makes some profiling using
/linux/Documentation/virt/kvm/
H A Dppc-pv.rst17 This cuts down virtualization costs by about 50% on some of my benchmarks.
/linux/fs/squashfs/
H A DKconfig159 reducinng performance in workloads like fio-based benchmarks.
/linux/Documentation/timers/
H A Dtimekeeping.rst136 and will likely show up in system benchmarks.
/linux/kernel/trace/
H A DKconfig247 small and not measurable even in micro-benchmarks (at least on
973 bool "Add tracepoint that benchmarks tracepoints"
987 As it is a tight loop, it benchmarks as hot cache. That's fine because
/linux/Documentation/admin-guide/pm/
H A Dcpufreq.rst687 4. Reproducible results are important when running benchmarks. Since
691 frequency boost mechanism before running benchmarks sensitive to that
/linux/mm/
H A DKconfig68 a particular compression algorithm please refer to the benchmarks
/linux/Documentation/virt/uml/
H A Duser_mode_linux_howto_v2.rst1051 of 5 times or higher on some benchmarks.
/linux/lib/
H A DKconfig.debug2829 In addition to correctness checks, simple performance benchmarks