Home
last modified time | relevance | path

Searched refs:workloads (Results 1 – 25 of 124) sorted by relevance

12345

/linux/drivers/crypto/intel/qat/
H A DKconfig23 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.
67 for accelerating crypto and compression workloads.
79 for accelerating crypto and compression workloads.
92 Virtual Function for accelerating crypto and compression workloads.
104 Virtual Function for accelerating crypto and compression workloads.
116 Virtual Function for accelerating crypto and compression workloads.
/linux/tools/perf/tests/shell/lib/
H A Dperf_metric_validation.py13 self.workloads = [wl] # multiple workloads possible
33 .format(self.metric, self.collectedValue, self.workloads,
49 self.workloads = [x for x in workload.split(",") if x]
204 … [TestError([m], self.workloads[self.wlidx], negmetric[m], 0) for m in negmetric.keys()])
279 …self.errlist.append(TestError([m['Name'] for m in rule['Metrics']], self.workloads[self.wlidx], [],
282 …self.errlist.append(TestError([m['Name'] for m in rule['Metrics']], self.workloads[self.wlidx], [v…
334 self.errlist.extend([TestError([name], self.workloads[self.wlidx], val,
346 allres = [{"Workload": self.workloads[i], "Results": self.allresults[i]}
347 for i in range(0, len(self.workloads))]
425 workload = self.workloads[self.wlidx]
[all …]
/linux/tools/perf/Documentation/
H A Dperf-test.txt58 Run a built-in workload, to list them use '--list-workloads', current ones include:
68 The datasym and landlock workloads don't accept any.
70 --list-workloads::
71 List the available workloads to use with -w/--workload.
/linux/Documentation/gpu/
H A Ddrm-compute.rst2 Long running workloads and compute
5 Long running workloads (compute) are workloads that will not complete in 10
7 This means that other techniques need to be used to manage those workloads,
H A Ddrm-vm-bind-async.rst103 exec functions. For long-running workloads, such pipelining of a bind
109 operations for long-running workloads will not allow for pipelining
110 anyway since long-running workloads don't allow for dma-fences as
121 deeply pipelined behind other VM_BIND operations and workloads
/linux/drivers/accel/qaic/
H A DKconfig15 designed to accelerate Deep Learning inference workloads.
18 for users to submit workloads to the devices.
/linux/drivers/accel/habanalabs/
H A DKconfig18 designed to accelerate Deep Learning inference and training workloads.
21 the user to submit workloads to the devices.
/linux/Documentation/accel/qaic/
H A Daic100.rst13 inference workloads. They are AI accelerators.
16 (x8). An individual SoC on a card can have up to 16 NSPs for running workloads.
20 performance. AIC100 cards are multi-user capable and able to execute workloads
82 the processors that run the workloads on AIC100. Each NSP is a Qualcomm Hexagon
85 one workload, AIC100 is limited to 16 concurrent workloads. Workload
93 in and out of workloads. AIC100 has one of these. The DMA Bridge has 16
103 This DDR is used to store workloads, data for the workloads, and is used by the
114 for generic compute workloads.
160 ready to process workloads.
210 | | | | managing workloads. |
[all …]
/linux/Documentation/timers/
H A Dno_hz.rst26 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
228 aggressive real-time workloads, which have the option of disabling
230 some workloads will no doubt want to use adaptive ticks to
232 options for these workloads:
252 workloads, which have few such transitions. Careful benchmarking
253 will be required to determine whether or not other workloads
/linux/Documentation/admin-guide/
H A Dworkload-tracing.rst34 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/drivers/cpuidle/
H A DKconfig33 Some workloads benefit from using it and it generally should be safe
45 Some virtualized workloads benefit from using it.
/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Didpf.rst81 Driver defaults are meant to fit a wide variety of workloads, but if further
89 is tuned for general workloads. The user can customize the interrupt rate
90 control for specific workloads, via ethtool, adjusting the number of
/linux/drivers/crypto/cavium/nitrox/
H A DKconfig18 for accelerating crypto workloads.
/linux/drivers/infiniband/hw/mana/
H A DKconfig8 for workloads (e.g. DPDK, MPI etc) that uses RDMA verbs to directly
/linux/Documentation/dev-tools/
H A Dautofdo.rst16 for workloads affected by front-end stalls.
23 characteristics similar to the workloads that are intended to be
34 (1) Sample real workloads using a production environment.
/linux/security/
H A DKconfig.hardening105 sees a 1% slowdown, other systems and workloads may vary and you
149 for your workloads.
170 workloads have measured as high as 7%.
188 synthetic workloads have measured as high as 8%.
208 workloads. Image size growth depends on architecture, and should
/linux/Documentation/accounting/
H A Dpsi.rst10 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/admin-guide/pm/
H A Dintel_uncore_frequency_scaling.rst23 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
133 latency sensitive workloads further tuning can be done by SW to
/linux/tools/perf/tests/
H A Dbuiltin-test.c147 static struct test_workload *workloads[] = { variable
164 for (unsigned i = 0; i < ARRAY_SIZE(workloads) && ({ workload = workloads[i]; 1; }); i++)
/linux/Documentation/scheduler/
H A Dsched-design-CFS.rst104 "server" (i.e., good batching) workloads. It defaults to a setting suitable
105 for desktop workloads. SCHED_BATCH is handled by the CFS scheduler module too.
108 base_slice_ns will have little to no impact on the workloads.
116 than the previous vanilla scheduler: both types of workloads are isolated much
/linux/Documentation/tools/rtla/
H A Dcommon_options.txt55 …ior differs between workload types. User workloads created by rtla will inherit rtla's cgroup. Ker…
/linux/fs/squashfs/
H A DKconfig106 poor performance on parallel I/O workloads when using multiple CPU
121 poor performance on parallel I/O workloads when using multiple CPU
159 reducinng performance in workloads like fio-based benchmarks.
/linux/Documentation/filesystems/ext4/
H A Dorphan.rst18 global single linked list is a scalability bottleneck for workloads that result
/linux/drivers/cpufreq/
H A DKconfig.x86191 the CPUs' workloads are. CPU-bound workloads will be more sensitive
193 workloads will be less sensitive -- they will not necessarily perform
/linux/Documentation/accel/amdxdna/
H A Damdnpu.rst124 torn down dynamically to accommodate various workloads. A *spatial* partition
134 of 2D array among various workloads. Every workload describes the number
137 decide 2D array (re)partition strategy and mapping of workloads for spatial and

12345