Searched refs:benchmarks (Results 1 – 18 of 18) sorted by relevance
120 struct bench *benchmarks; member147 for (bench = coll->benchmarks; bench && bench->name; bench++)
59 NUMA scheduling and MM benchmarks.62 Futex stressing benchmarks.65 Eventpoll (epoll) stressing benchmarks.
11 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
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?]
2052 benchmarks. It also makes some profiling using
17 This cuts down virtualization costs by about 50% on some of my benchmarks.
136 and will likely show up in system benchmarks.
227 small and not measurable even in micro-benchmarks (at least on910 bool "Add tracepoint that benchmarks tracepoints"924 As it is a tight loop, it benchmarks as hot cache. That's fine because
689 4. Reproducible results are important when running benchmarks. Since693 frequency boost mechanism before running benchmarks sensitive to that
49 benchmarks showing what the impact (or benefit) of your change is; a
217 benchmarks have indicated that increasing the size of the pool does not
71 a particular compression algorithm please refer to the benchmarks
1084 of 5 times or higher on some benchmarks.
2924 Include benchmarks in the KUnit test suite for the CRC functions.