| /OK3568_Linux_fs/kernel/drivers/crypto/qat/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/drivers/misc/habanalabs/ |
| H A D | Kconfig | 14 designed to accelerate Deep Learning inference and training workloads. 17 the user to submit workloads to the devices.
|
| /OK3568_Linux_fs/buildroot/package/coremark-pro/ |
| H A D | coremark-pro.sh.in | 4 workloads="@COREMARK_PRO_MARKS@" 15 for wld in $workloads; do
|
| /OK3568_Linux_fs/kernel/Documentation/timers/ |
| H 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
|
| /OK3568_Linux_fs/kernel/drivers/cpuidle/ |
| H A D | Kconfig | 33 Some workloads benefit from using it and it generally should be safe 45 Some virtualized workloads benefit from using it.
|
| /OK3568_Linux_fs/kernel/drivers/crypto/cavium/nitrox/ |
| H A D | Kconfig | 18 for accelerating crypto workloads.
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/gvt/ |
| H A D | scheduler.c | 1282 kmem_cache_destroy(s->workloads); in intel_vgpu_clean_submission() 1377 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload", in intel_vgpu_setup_submission() 1384 if (!s->workloads) { in intel_vgpu_setup_submission() 1493 kmem_cache_free(s->workloads, workload); in intel_vgpu_destroy_workload() 1502 workload = kmem_cache_zalloc(s->workloads, GFP_KERNEL); in alloc_workload() 1676 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload() 1690 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload() 1701 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
|
| /OK3568_Linux_fs/kernel/security/ |
| H A D | Kconfig.hardening | 172 sees a 1% slowdown, other systems and workloads may vary and you 202 your workloads. 222 workloads have measured as high as 7%. 239 synthetic workloads have measured as high as 8%.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/haveged/ |
| H A D | haveged_1.9.18.bb | 2 …entropy conditions in the Linux random device that can occur under some workloads, especially on h…
|
| /OK3568_Linux_fs/kernel/Documentation/accounting/ |
| H 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
|
| /OK3568_Linux_fs/kernel/Documentation/vm/ |
| H 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
|
| H A 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).
|
| /OK3568_Linux_fs/kernel/drivers/cpufreq/ |
| H A D | Kconfig.x86 | 151 the CPUs' workloads are. CPU-bound workloads will be more sensitive 153 workloads will be less sensitive -- they will not necessarily perform
|
| H A D | Kconfig | 124 'interactive' governor for latency-sensitive workloads. 232 designed for latency-sensitive workloads. 236 interactive workloads.
|
| /OK3568_Linux_fs/kernel/Documentation/scheduler/ |
| H 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/md/ |
| H 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
|
| /OK3568_Linux_fs/kernel/fs/squashfs/ |
| H 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
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | checklist.rst | 200 to real-time workloads. Use of the expedited primitives should 203 However, real-time workloads can use rcupdate.rcu_normal kernel 213 of the system, especially to real-time workloads running on 346 for some real-time workloads, this is the whole point of using 387 real-time workloads than is synchronize_rcu_expedited().
|
| /OK3568_Linux_fs/kernel/Documentation/x86/ |
| H 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A D | dma-buf.rst | 236 randomly hangs workloads until the timeout kicks in. Workloads, which from 249 workloads. This also means no implicit fencing for shared buffers in these
|
| /OK3568_Linux_fs/kernel/kernel/rcu/ |
| H A D | Kconfig | 223 real-time workloads. It can also be used to offload RCU 249 eliminates such IPIs for many workloads, proper setting
|
| /OK3568_Linux_fs/kernel/Documentation/block/ |
| H 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:
|
| H A D | writeback_cache_control.rst | 11 behavior obviously speeds up various workloads, but it means the operating
|
| /OK3568_Linux_fs/kernel/tools/perf/Documentation/ |
| H A D | perf-bench.txt | 204 Suite for evaluating NUMA workloads.
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 86 interactive or low latency workloads.
|