| /linux/drivers/crypto/qat/ |
| A D | Kconfig | 23 for accelerating crypto and compression workloads.
34 for accelerating crypto and compression workloads.
45 for accelerating crypto and compression workloads.
56 for accelerating crypto and compression workloads.
69 Virtual Function for accelerating crypto and compression workloads.
81 Virtual Function for accelerating crypto and compression workloads.
93 Virtual Function for accelerating crypto and compression workloads.
|
| /linux/Documentation/vm/damon/ |
| A D | index.rst | 15 of the size of target workloads).
20 In user space, meanwhile, users who have some special workloads can write
22 workloads and systems.
|
| /linux/drivers/misc/habanalabs/ |
| A D | Kconfig | 15 designed to accelerate Deep Learning inference and training workloads.
18 the user to submit workloads to the devices.
|
| /linux/Documentation/driver-api/ |
| A D | dma-buf.rst | 261 randomly hangs workloads until the timeout kicks in. Workloads, which from
274 workloads. This also means no implicit fencing for shared buffers in these
296 faults on GPUs are limited to pure compute workloads.
312 - Compute workloads can always be preempted, even when a page fault is pending
315 - DMA fence workloads and workloads which need page fault handling have
318 reservations for DMA fence workloads.
321 hardware resources for DMA fence workloads when they are in-flight. This must
326 all workloads must be flushed from the GPU when switching between jobs
330 made visible anywhere in the system, all compute workloads must be preempted
341 Note that workloads that run on independent hardware like copy engines or other
[all …]
|
| /linux/Documentation/timers/ |
| A 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
235 aggressive real-time workloads, which have the option of disabling
237 some workloads will no doubt want to use adaptive ticks to
239 options for these workloads:
259 workloads, which have few such transitions. Careful benchmarking
260 will be required to determine whether or not other workloads
|
| /linux/drivers/cpuidle/ |
| A D | Kconfig | 33 Some workloads benefit from using it and it generally should be safe
45 Some virtualized workloads benefit from using it.
|
| /linux/security/ |
| A D | Kconfig.hardening | 169 sees a 1% slowdown, other systems and workloads may vary and you
199 your workloads.
219 workloads have measured as high as 7%.
236 synthetic workloads have measured as high as 8%.
253 workloads. Image size growth depends on architecture, and should
|
| /linux/drivers/crypto/cavium/nitrox/ |
| A D | Kconfig | 18 for accelerating crypto workloads.
|
| /linux/drivers/gpu/drm/i915/gvt/ |
| A D | scheduler.c | 1328 kmem_cache_destroy(s->workloads); in intel_vgpu_clean_submission()
1420 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload", in intel_vgpu_setup_submission()
1427 if (!s->workloads) { in intel_vgpu_setup_submission()
1536 kmem_cache_free(s->workloads, workload); in intel_vgpu_destroy_workload()
1545 workload = kmem_cache_zalloc(s->workloads, GFP_KERNEL); in alloc_workload()
1719 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
1733 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
1744 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
|
| /linux/Documentation/accounting/ |
| A D | psi.rst | 10 When CPU, memory or IO devices are contended, workloads experience
19 such resource crunches and the time impact it has on complex workloads
23 scarcity aids users in sizing workloads to hardware--or provisioning
|
| /linux/Documentation/vm/ |
| A 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
|
| /linux/drivers/cpufreq/ |
| A D | Kconfig.x86 | 141 the CPUs' workloads are. CPU-bound workloads will be more sensitive
143 workloads will be less sensitive -- they will not necessarily perform
|
| /linux/kernel/rcu/ |
| A D | Kconfig | 223 real-time workloads. It can also be used to offload RCU
227 workloads will incur significant increases in context-switch
253 eliminates such IPIs for many workloads, proper setting
|
| /linux/Documentation/scheduler/ |
| A 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/Documentation/filesystems/ext4/ |
| A D | orphan.rst | 18 global single linked list is a scalability bottleneck for workloads that result
|
| /linux/Documentation/driver-api/md/ |
| A 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/Documentation/admin-guide/hw-vuln/ |
| A D | core-scheduling.rst | 9 workloads may benefit from running on the same core as they don't need the same
24 world workloads. In theory, core scheduling aims to perform at least as good as
30 total number of CPUs. Please measure the performance of your workloads always.
|
| /linux/fs/squashfs/ |
| A 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/Documentation/x86/ |
| A D | sgx.rst | 234 SGX workloads, (or just any new workloads), and migrate all valuable
235 workloads. Although a machine reboot can recover all EPC memory, the bug
|
| A 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/Documentation/RCU/ |
| A D | checklist.rst | 198 to real-time workloads. Use of the expedited primitives should
201 However, real-time workloads can use rcupdate.rcu_normal kernel
211 of the system, especially to real-time workloads running on
364 for some real-time workloads, this is the whole point of using
405 real-time workloads than is synchronize_rcu_expedited().
|
| /linux/lib/ |
| A D | Kconfig.kfence | 57 evaluated given target workloads and system architectures. Notably,
|
| /linux/tools/perf/Documentation/ |
| A D | perf-bench.txt | 204 Suite for evaluating NUMA workloads.
|
| /linux/Documentation/block/ |
| A D | writeback_cache_control.rst | 11 behavior obviously speeds up various workloads, but it means the operating
|
| A 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:
|