Searched refs:benchmarks (Results 1 – 17 of 17) sorted by relevance
59 NUMA scheduling and MM benchmarks.62 Futex stressing benchmarks.65 Eventpoll (epoll) stressing benchmarks.
107 struct bench *benchmarks; member133 for (bench = coll->benchmarks; bench && bench->name; bench++)
17 benchmarks \
537 struct benchmarks { struct546 struct benchmarks list[] = { in run_benchmarks() argument568 struct benchmarks *b; in run_benchmarks()
47 * https://magpi.raspberrypi.com/articles/raspberry-pi-3-specs-benchmarks
44 latest benchmarks.:-) Use of this option allows our team to go all
47 This has made porting some benchmarks difficult. It is possible to
110 benchmarks for executing different subsystems in the Linux kernel and240 benchmarks for executing different subsystems in the Linux kernel and246 "perf bench all" command runs the following benchmarks:
269 and caching devices and then install bcache on top. [benchmarks?]
17 This cuts down virtualization costs by about 50% on some of my benchmarks.
136 and will likely show up in system benchmarks.
113 to get slightly better performance in multiprocessor benchmarks. It also
213 small and not measurable even in micro-benchmarks (at least on838 bool "Add tracepoint that benchmarks tracepoints"852 As it is a tight loop, it benchmarks as hot cache. That's fine because
670 4. Reproducible results are important when running benchmarks. Since674 frequency boost mechanism before running benchmarks sensitive to that
49 benchmarks showing what the impact (or benefit) of your change is; a
58 a particular compression algorithm please refer to the benchmarks
1049 of 5 times or higher on some benchmarks.
Completed in 22 milliseconds