| /linux-6.3-rc2/drivers/crypto/qat/ |
| A D | Kconfig | 24 for accelerating crypto and compression workloads.
35 for accelerating crypto and compression workloads.
46 for accelerating crypto and compression workloads.
57 for accelerating crypto and compression workloads.
70 Virtual Function for accelerating crypto and compression workloads.
82 Virtual Function for accelerating crypto and compression workloads.
94 Virtual Function for accelerating crypto and compression workloads.
|
| /linux-6.3-rc2/Documentation/mm/damon/ |
| A D | index.rst | 16 of the size of target workloads).
20 users who have special information about their workloads can write personalized
21 applications for better understanding and optimizations of their workloads and
|
| /linux-6.3-rc2/drivers/accel/habanalabs/ |
| A D | Kconfig | 18 designed to accelerate Deep Learning inference and training workloads.
21 the user to submit workloads to the devices.
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | dma-buf.rst | 264 randomly hangs workloads until the timeout kicks in. Workloads, which from
277 workloads. This also means no implicit fencing for shared buffers in these
299 faults on GPUs are limited to pure compute workloads.
315 - Compute workloads can always be preempted, even when a page fault is pending
318 - DMA fence workloads and workloads which need page fault handling have
321 reservations for DMA fence workloads.
324 hardware resources for DMA fence workloads when they are in-flight. This must
329 all workloads must be flushed from the GPU when switching between jobs
333 made visible anywhere in the system, all compute workloads must be preempted
344 Note that workloads that run on independent hardware like copy engines or other
[all …]
|
| /linux-6.3-rc2/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
231 aggressive real-time workloads, which have the option of disabling
233 some workloads will no doubt want to use adaptive ticks to
235 options for these workloads:
255 workloads, which have few such transitions. Careful benchmarking
256 will be required to determine whether or not other workloads
|
| /linux-6.3-rc2/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-6.3-rc2/Documentation/admin-guide/pm/ |
| A D | intel_uncore_frequency_scaling.rst | 23 Users may have some latency sensitive workloads where they do not want any
24 change to uncore frequency. Also, users may have workloads which require
|
| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | workload-tracing.rst | 34 to evaluate safety considerations. We use strace tool to trace workloads.
67 We used strace to trace the perf, stress-ng, paxtest workloads to illustrate
69 be applied to trace other workloads.
101 paxtest workloads to show how to analyze a workload and identify Linux
102 subsystems used by these workloads. Let's start with an overview of these
103 three workloads to get a better understanding of what they do and how to
173 by three workloads we have chose for this analysis.
312 Tracing workloads
315 Now that we understand the workloads, let's start tracing them.
595 information on the resources in use by workloads using strace.
|
| /linux-6.3-rc2/drivers/crypto/cavium/nitrox/ |
| A D | Kconfig | 18 for accelerating crypto workloads.
|
| /linux-6.3-rc2/drivers/infiniband/hw/mana/ |
| A D | Kconfig | 8 for workloads (e.g. DPDK, MPI etc) that uses RDMA verbs to directly
|
| /linux-6.3-rc2/tools/perf/tests/ |
| A D | builtin-test.c | 130 static struct test_workload *workloads[] = { variable
501 for (i = 0; i < ARRAY_SIZE(workloads); i++) { in run_workload()
502 twl = workloads[i]; in run_workload()
|
| A D | Build | 109 perf-y += workloads/
|
| /linux-6.3-rc2/drivers/gpu/drm/i915/gvt/ |
| A D | scheduler.c | 1330 kmem_cache_destroy(s->workloads); in intel_vgpu_clean_submission()
1422 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload", in intel_vgpu_setup_submission()
1429 if (!s->workloads) { in intel_vgpu_setup_submission()
1538 kmem_cache_free(s->workloads, workload); in intel_vgpu_destroy_workload()
1547 workload = kmem_cache_zalloc(s->workloads, GFP_KERNEL); in alloc_workload()
1721 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
1735 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
1746 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
|
| /linux-6.3-rc2/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-6.3-rc2/security/ |
| A D | Kconfig.hardening | 177 sees a 1% slowdown, other systems and workloads may vary and you
217 your workloads.
238 workloads have measured as high as 7%.
256 synthetic workloads have measured as high as 8%.
276 workloads. Image size growth depends on architecture, and should
|
| /linux-6.3-rc2/Documentation/filesystems/ext4/ |
| A D | orphan.rst | 18 global single linked list is a scalability bottleneck for workloads that result
|
| /linux-6.3-rc2/drivers/cpufreq/ |
| A D | Kconfig.x86 | 173 the CPUs' workloads are. CPU-bound workloads will be more sensitive
175 workloads will be less sensitive -- they will not necessarily perform
|
| /linux-6.3-rc2/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-6.3-rc2/kernel/rcu/ |
| A D | Kconfig | 244 real-time workloads. It can also be used to offload RCU
248 workloads will incur significant increases in context-switch
303 eliminates such IPIs for many workloads, proper setting
|
| /linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/fs/squashfs/ |
| A D | Kconfig | 106 poor performance on parallel I/O workloads when using multiple CPU
121 poor performance on parallel I/O workloads when using multiple CPU
|
| /linux-6.3-rc2/Documentation/x86/ |
| A D | sgx.rst | 249 SGX workloads, (or just any new workloads), and migrate all valuable
250 workloads. Although a machine reboot can recover all EPC memory, the bug
|
| /linux-6.3-rc2/lib/ |
| A D | Kconfig.kfence | 69 evaluated given target workloads and system architectures. Notably,
|
| /linux-6.3-rc2/tools/perf/Documentation/ |
| A D | perf-bench.txt | 204 Suite for evaluating NUMA workloads.
|