Searched refs:workloads (Results 1 – 25 of 69) sorted by relevance
123
| /Linux-v5.4/drivers/crypto/qat/ |
| D | Kconfig | 22 for accelerating crypto and compression workloads.
33 for accelerating crypto and compression workloads.
44 for accelerating crypto and compression workloads.
57 Virtual Function for accelerating crypto and compression workloads.
69 Virtual Function for accelerating crypto and compression workloads.
81 Virtual Function for accelerating crypto and compression workloads.
|
| /Linux-v5.4/drivers/misc/habanalabs/ |
| D | Kconfig | 15 designed to accelerate Deep Learning inference and training workloads.
18 the user to submit workloads to the devices.
|
| /Linux-v5.4/drivers/cpuidle/ |
| D | Kconfig | 33 Some workloads benefit from using it and it generally should be safe
45 Some virtualized workloads benefit from using it.
|
| /Linux-v5.4/Documentation/timers/ |
| D | no_hz.rst | 26 workloads, you will normally -not- want this option.
39 right approach, for example, in heavy workloads with lots of tasks
42 hundreds of microseconds). For these types of workloads, scheduling
56 are running light workloads, you should therefore read the following
118 computationally intensive short-iteration workloads: If any CPU is
237 aggressive real-time workloads, which have the option of disabling
239 some workloads will no doubt want to use adaptive ticks to
241 options for these workloads:
261 workloads, which have few such transitions. Careful benchmarking
262 will be required to determine whether or not other workloads
|
| /Linux-v5.4/drivers/crypto/cavium/nitrox/ |
| D | Kconfig | 18 for accelerating crypto workloads.
|
| /Linux-v5.4/security/ |
| D | Kconfig.hardening | 130 sees a 1% slowdown, other systems and workloads may vary and you
160 your workloads.
180 workloads have measured as high as 7%.
197 synthetic workloads have measured as high as 8%.
|
| /Linux-v5.4/drivers/gpu/drm/i915/gvt/ |
| D | scheduler.c | 1178 kmem_cache_destroy(s->workloads); in intel_vgpu_clean_submission()
1279 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload", in intel_vgpu_setup_submission()
1286 if (!s->workloads) { in intel_vgpu_setup_submission()
1384 kmem_cache_free(s->workloads, workload); in intel_vgpu_destroy_workload()
1393 workload = kmem_cache_zalloc(s->workloads, GFP_KERNEL); in alloc_workload()
1566 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
1580 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
1591 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
|
| /Linux-v5.4/Documentation/accounting/ |
| D | psi.rst | 8 When CPU, memory or IO devices are contended, workloads experience
17 such resource crunches and the time impact it has on complex workloads
21 scarcity aids users in sizing workloads to hardware--or provisioning
|
| /Linux-v5.4/Documentation/vm/ |
| D | cleancache.rst | 12 many workloads in many environments at a negligible cost.
119 Cleancache provides a significant performance benefit to many workloads
142 well-publicized special-case workloads). Cleancache -- and frontswap --
218 Briefly, performance gains can be significant on most workloads,
222 overhead is negligible even in worst case workloads. Basically
|
| D | frontswap.rst | 83 Frontswap significantly increases performance in many such workloads by
104 on some workloads under high memory pressure.
120 well-publicized special-case workloads).
|
| /Linux-v5.4/drivers/cpufreq/ |
| D | Kconfig.x86 | 149 the CPUs' workloads are. CPU-bound workloads will be more sensitive
151 workloads will be less sensitive -- they will not necessarily perform
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-design-CFS.rst | 100 "server" (i.e., good batching) workloads. It defaults to a setting suitable
101 for desktop workloads. SCHED_BATCH is handled by the CFS scheduler module too.
109 than the previous vanilla scheduler: both types of workloads are isolated much
|
| /Linux-v5.4/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 58 completely avoid the overhead, so it's very helpful for some workloads. A
74 mode depending on the workloads. It's recommended to use a cache disk with at
|
| /Linux-v5.4/fs/squashfs/ |
| D | Kconfig | 78 poor performance on parallel I/O workloads when using multiple CPU
92 poor performance on parallel I/O workloads when using multiple CPU
|
| /Linux-v5.4/Documentation/RCU/ |
| D | checklist.txt | 196 to real-time workloads. Use of the expedited primitives should
199 However, real-time workloads can use rcupdate.rcu_normal kernel
209 of the system, especially to real-time workloads running on
342 for some real-time workloads, this is the whole point of using
383 real-time workloads than is synchronize_rcu_expedited().
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-stat.txt | 268 determine bottle necks in the CPU pipeline for CPU bound workloads,
280 mode like -I 1000, as the bottleneck of workloads can change often.
354 For workload sessions we also display time the workloads spent in
|
| D | perf-bench.txt | 190 Suite for evaluating NUMA workloads.
|
| /Linux-v5.4/Documentation/block/ |
| D | writeback_cache_control.rst | 11 behavior obviously speeds up various workloads, but it means the operating
|
| D | bfq-iosched.rst | 87 background workloads are being executed:
122 sequential workloads considered in our tests. With random workloads,
123 and with all the workloads on flash-based devices, BFQ achieves,
142 possibly heavy workloads are being served, BFQ guarantees:
|
| /Linux-v5.4/Documentation/x86/ |
| D | orc-unwinder.rst | 34 Gorman [1]_ have shown a slowdown of 5-10% for some workloads.
46 footprint. That can transform to even higher speedups for workloads
|
| /Linux-v5.4/tools/power/cpupower/bench/ |
| D | README-BENCH | 21 - Real world (workloads)
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 52 workloads. smq also does not have any cumbersome tuning knobs.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-block | 131 workloads where a high number of I/O operations is
143 preferred request size for workloads where sustained
|
| /Linux-v5.4/lib/ |
| D | Kconfig.kasan | 100 memory accesses. This is faster than outline (in some workloads
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | ext4.rst | 53 important to try multiple workloads; very often a subtle change in a
62 data=writeback' can be faster for some workloads. (Note however that
67 metadata-intensive workloads.
315 workloads on very fast disks, at the cost of increasing latency.
|
123
