Home
last modified time | relevance | path

Searched full:workloads (Results 1 – 25 of 139) sorted by relevance

123456

/linux/tools/perf/tests/shell/lib/
H A Dperf_metric_validation.py13 self.workloads = [wl] # multiple workloads possible
24 \tRelationship rule description: \'{5}\'".format(self.metric, self.collectedValue, self.workloads,
28 \tworkload(s): {1}".format(self.metric, self.workloads)
33 .format(self.metric, self.collectedValue, self.workloads,
49 self.workloads = [x for x in workload.split(",") if x]
50 self.wlidx = 0 # idx of current workloads
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[sel
[all...]
/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/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/core-api/real-time/
H A Dkernel-configuration.rst48 Real-Time workloads expect a fixed CPU frequency during execution. Using the
117 GPU-accelerated workloads can share system resources with the CPU, including
127 If graphics workloads must run alongside real-time tasks, users must conduct
175 - For periodic workloads; e.g., control loops executing every 100 µs, avoid
178 - For computation-intensive workloads; e.g. extended userspace execution,
228 real-time workloads and peripherals with lockdep (:ref:`lockdep`) and other
230 workloads might trigger kernel code paths that were not triggered during the
H A Dhardware.rst13 can affect the deterministic handling of workloads in other applications.
51 different workloads on a neighboring CPU. Even more powerful, the perf
220 affects real-time workloads depends on whether secure interrupts are enabled
/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/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/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/drivers/crypto/cavium/nitrox/
H A DKconfig18 for accelerating crypto workloads.
/linux/tools/perf/tests/
H A Dbuiltin-test.c159 static struct test_workload *workloads[] = {
186 for (unsigned i = 0; i < ARRAY_SIZE(workloads) && ({ workload = workloads[i]; 1; }); i++) in close_parent_fds()
1742 OPT_STRING('w', "workload", &workload, "work", "workload to run for testing, use '--list-workloads' to list the available ones."),
1745 OPT_BOOLEAN(0, "list-workloads", &list_workloads, "List the available builtin workloads to use with -w/--workload"),
147 static struct test_workload *workloads[] = { global() variable
H A Dtests.h219 * Define test workloads to be used in test suites.
237 /* The list of test workloads */
/linux/drivers/infiniband/hw/mana/
H A DKconfig8 for workloads (e.g. DPDK, MPI etc) that uses RDMA verbs to directly
/linux/Documentation/driver-api/md/
H A Draid5-cache.rst58 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/
H A Dcore-scheduling.rst9 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/Documentation/arch/x86/
H A Dsgx.rst249 SGX workloads, (or just any new workloads), and migrate all valuable
250 workloads. Although a machine reboot can recover all EPC memory, the bug
H A Dorc-unwinder.rst34 Gorman [1]_ have shown a slowdown of 5-10% for some workloads.
46 footprint. That can transform to even higher speedups for workloads
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A Duncore-cache.json1310 …eads. This count only tracks the regular credits Common high banwidth workloads should be able t…
1320 …eads. This count only tracks the regular credits Common high banwidth workloads should be able t…
1330 …eads. This count only tracks the regular credits Common high banwidth workloads should be able t…
1340 …eads. This count only tracks the regular credits Common high banwidth workloads should be able t…
1350 …l' credits. This statistic is generally not interesting for general IA workloads, but may be of i…
1360 …l' credits. This statistic is generally not interesting for general IA workloads, but may be of i…
1370 …l' credits. This statistic is generally not interesting for general IA workloads, but may be of i…
1380 …l' credits. This statistic is generally not interesting for general IA workloads, but may be of i…
1903 …ites. This count only tracks the regular credits Common high banwidth workloads should be able t…
1913 …ites. This count only tracks the regular credits Common high banwidth workloads should be able t…
[all …]
/linux/samples/coresight/
H A Dcoresight-cfg-sample.c23 * experimentation with mark / space ratios for various workloads
/linux/Documentation/block/
H A Dbfq-iosched.rst87 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/Documentation/RCU/
H A Dchecklist.rst222 IPI-sensitive real-time workloads can use the rcupdate.rcu_normal
232 of the system, especially to real-time workloads running on the
398 real-time workloads, this is the whole point of using the
453 real-time workloads than is synchronize_rcu_expedited().
/linux/tools/perf/tests/shell/
H A Dsched.sh32 # Start two noploop workloads on CPU0 to trigger scheduling.
/linux/Documentation/filesystems/ext4/
H A Dorphan.rst18 global single linked list is a scalability bottleneck for workloads that result
/linux/lib/
H A DKconfig.kfence69 evaluated given target workloads and system architectures. Notably,
/linux/kernel/rcu/
H A DKconfig280 real-time workloads. It can also be used to offload RCU
284 workloads will incur significant increases in context-switch

123456