Home
last modified time | relevance | path

Searched full:workload (Results 1 – 25 of 222) sorted by relevance

123456789

/linux/tools/testing/selftests/thermal/intel/workload_hint/
H A Dworkload_hint_test.c39 perror("Unable to open workload type feature enable file"); in workload_hint_exit()
44 perror("Can't disable workload hints"); in workload_hint_exit()
48 printf("Disabled workload type prediction\n");
61 perror("Unable to open workload notification delay"); in main()
118 perror("Unable to open workload type feature enable file"); in main()
123 perror("Can't enable workload hints"); in main()
129 printf("Enabled workload type prediction\n"); in main()
134 perror("Unable to open workload type file"); in main()
173 printf("workload type slow:%s\n", "power");
175 printf("workload typ
[all...]
/linux/tools/perf/tests/shell/lib/
H A Dperf_metric_validation.py22 \tis {1} in workload(s): {2} \n\
31 \tis {1} in workload(s): {2}\n\
39 workload='true', metrics='', cputype='cpu'): argument
49 self.workloads = [x for x in workload.split(",") if x]
51 self.allresults = dict() # metric results of all workload
55 self.results = dict() # metric results of current workload
188 # The first round collect_perf() run these metrics with simple workload
189 # "true". We give metrics a second chance with a longer workload if less
346 allres = [{"Workload": self.workloads[i], "Results": self.allresults[i]}
380 def _run_perf(self, metric, workload
[all...]
/linux/Documentation/admin-guide/mm/
H A Didle_page_tracking.rst9 accessed by a workload and which are idle. This information can be useful for
10 estimating the workload's working set size, which, in turn, can be taken into
11 account when configuring the workload parameters, setting memory cgroup limits,
12 or deciding where to place the workload within a compute cluster.
51 workload one should:
53 1. Mark all the workload's pages as idle by setting corresponding bits in
55 ``/proc/pid/pagemap`` if the workload is represented by a process, or by
56 filtering out alien pages using ``/proc/kpagecgroup`` in case the workload
59 2. Wait until the workload accesses its working set.
/linux/Documentation/filesystems/nfs/
H A Dknfsd-stats.rst54 Depending on the NFS workload patterns and various network stack
58 However this is a more accurate and less workload-dependent measure
74 pool for the NFS workload (the workload is thread-limited), in which
76 performance of the NFS workload.
93 threads configured than can be used by the NFS workload. This is
99 slow; the idle timeout is 60 minutes. Unless the NFS workload
/linux/tools/perf/tests/
H A Dperf-record.c112 * Prepare the workload in argv[] to run, it'll fork it, and then wait in test__PERF_RECORD()
119 pr_debug("Couldn't run the workload!\n"); in test__PERF_RECORD()
179 * count just on workload.pid, which will start... in test__PERF_RECORD()
H A Dtask-exit.c38 * This test will start a workload that does nothing then it checks
84 pr_debug("Couldn't run the workload!\n"); in test__task_exit()
155 TEST_CASE_EXCLUSIVE("Number of exit events of a simple workload", task_exit),
159 .desc = "Number of exit events of a simple workload",
H A Dbuiltin-test.c185 #define workloads__for_each(workload) \ in close_parent_fds()
186 for (unsigned i = 0; i < ARRAY_SIZE(workloads) && ({ workload = workloads[i]; 1; }); i++) in close_parent_fds()
1495 pr_err("Failed to open workload control FIFO '%s': %m\n", s);
1504 pr_err("Failed to open workload control ack FIFO '%s': %m\n", p);
1526 pr_err("Unsupported workload control spec '%s', expected fifo:ctl-fifo[,ack-fifo]\n",
1653 pr_info("No workload found: %s\n", work);
1730 const char *workload = NULL;
1742 OPT_STRING('w', "workload", &workload, "work", "workload t
163 workloads__for_each(workload) global() argument
788 const char *workload = NULL; cmd_test() local
[all...]
/linux/tools/perf/pmu-events/arch/x86/amdzen1/
H A Dfloating-point.json6 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
13 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
20 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
27 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
34 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
41 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
48 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
55 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
62 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
69 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
/linux/tools/perf/tests/shell/
H A Dstat_bpf_counters.sh12 workload=(taskset -c "$CPU" awk 'BEGIN { for (i=0; i<10000000; i++) sum+=i }')
49 base_instructions=$(perf stat --no-big-num -e instructions:u -- "${workload[@]}" 2>&1 | \
54 -- "${workload[@]}" 2>&1 | \
68 -- "${workload[@]}" 2>&1)
H A Dtrace_summary.sh17 workload="cat /dev/null"
20 echo "testing: perf trace ${args} -- ${workload}"
21 perf trace ${args} -- ${workload} >${OUTPUT} 2>&1
H A Dtest_intel_pt.sh221 echo "Workload PIDs are $w1 and $w2"
H A Dstat_metrics_values.sh21 workload="perf bench futex hash -r 1 -s"
29 $PYTHON $pythonvalidator -rule $rulefile -output_dir $tmpdir -wl "${workload}" \
/linux/Documentation/gpu/
H A Ddrm-compute.rst11 have their memory swapped out from them. Or they simply want their workload
19 waiting for the workload to complete. Effectively this terminates the workload
22 Since this is undesirable, there need to be mitigations to prevent a workload
H A Ddrm-vm-bind-async.rst43 * ``long-running workload``: A workload that may take more than the
106 fences gated by a long-running workload and used as in-syncobjs for the
116 workload itself, which is allowed by dma-fence rules, but rather for
140 buffers. The workload execution can then easily be pipelined behind
142 for a GPU semaphore embedded by UMD in the workload.
/linux/tools/testing/selftests/sched_ext/
H A Dpeek_dsq.c24 * Background workload thread that sleeps and wakes rapidly to exercise
95 printf("Starting %d background workload threads...\n", NUM_WORKERS); in run()
100 SCX_ERR("Failed to create workload thread %d: %s", i, strerror(err)); in run()
119 /* Stop workload threads and cleanup */ in run()
132 SCX_ERR("Failed to join workload thread %d: %s", i, strerror(err)); in run()
137 printf("Background workload threads stopped.\n"); in run()
/linux/Documentation/scheduler/
H A Dsched-capacity.rst73 With a workload that periodically does a fixed amount of work, you will get an
104 Executing the same workload as described in 1.3.1, which each CPU running at its
112 workload on CPU1
152 One issue that needs to be taken into account is that a workload's duty cycle is
154 periodic workload at a given frequency F::
163 Now, consider running the *same* workload at frequency F/2::
185 identical workload on CPUs of different capacity values will yield different
193 Executing a given periodic workload on each CPU at their maximum frequency would
384 workload on CPU0
391 workload on CPU1
[all …]
/linux/drivers/gpu/drm/i915/gvt/
H A Dscheduler.h89 /* if this workload has been dispatched to i915? */
91 bool shadow; /* if workload has done shadow of guest request */
137 void intel_vgpu_queue_workload(struct intel_vgpu_workload *workload);
164 void intel_vgpu_destroy_workload(struct intel_vgpu_workload *workload);
H A Dsched_policy.c150 * after the flag is set, workload dispatch thread will in try_to_schedule_next_vgpu()
151 * stop dispatching workload for current vgpu in try_to_schedule_next_vgpu()
155 /* still have uncompleted workload? */ in try_to_schedule_next_vgpu()
172 /* wake up workload dispatch thread */ in try_to_schedule_next_vgpu()
184 /* search a vgpu with pending workload */ in find_busy_vgpu()
465 /* stop workload dispatching */ in intel_vgpu_stop_schedule()
/linux/Documentation/timers/
H A Dno_hz.rst52 However, if you are instead running a light workload with long idle
59 In addition, if you are running either a real-time workload or an HPC
60 workload with short iterations, the scheduling-clock interrupts can
61 degrade your applications performance. If this describes your workload,
203 but do not see any change in your workload's behavior. Is this because
204 your workload isn't affected that much by OS jitter, or is it because
215 possible, then you can conclude that your workload is not all that
291 constraining the workload. For example, the only way to eliminate
/linux/tools/perf/pmu-events/arch/x86/amdzen2/
H A Dfloating-point.json6 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
13 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
20 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
27 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
34 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
/linux/rust/pin-init/examples/
H A Dstatic_init.rs90 let workload = 1_000; in main()
97 for _ in 0..workload { in main()
106 for _ in 0..workload { in main()
119 assert_eq!(*mtx.lock(), workload * thread_count * 2); in main()
93 let workload = 1_000; main() localVariable
H A Dpthread_mutex.rs157 let workload = 1_000_000; in main()
164 for _ in 0..workload { in main()
169 for _ in 0..workload { in main()
181 assert_eq!(*mtx.lock(), workload * thread_count * 2); in main()
158 let workload = 1_000_000; main() localVariable
H A Dmutex.rs191 let workload = if cfg!(miri) { 100 } else { 1_000 };
198 for _ in 0..workload { in main()
203 for _ in 0..workload { in main()
215 assert_eq!(*mtx.lock(), workload * thread_count * 2); in main()
199 let workload = if cfg!(miri) { 100 } else { 1_000 }; main() localVariable
/linux/tools/perf/pmu-events/arch/x86/amdzen3/
H A Dfloating-point.json6 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
13 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
20 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
27 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
34 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
/linux/tools/perf/bench/
H A Dfind-bit-bench.c34 static noinline void workload(int val) in workload() function
82 workload(bit); in do_for_each_set_bit()
97 workload(bit); in do_for_each_set_bit()

123456789