Lines Matching refs:CPU

38 worker thread per CPU and a single threaded (ST) wq had one worker
41 wq users over the years and with the number of CPU cores continuously
48 worker pool. A MT wq could provide only one execution context per CPU
66 * Use per-CPU unified worker pools shared by all wq to provide
95 for high priority ones, for each possible CPU and some extra
103 things like CPU locality, concurrency limits, priority and more. To
112 is associated to the CPU the issuer is running on.
120 Each worker-pool bound to an actual CPU implements concurrency
124 not expected to hog a CPU and consume many cycles. That means
127 workers on the CPU, the worker-pool doesn't start execution of a new
129 schedules a new worker so that the CPU doesn't sit idle while there
173 specific CPU. This makes the wq behave as a simple execution
184 * Long running CPU intensive workloads which can be better
211 Work items of a CPU intensive wq do not contribute to the
212 concurrency level. In other words, runnable CPU intensive
215 work items which are expected to hog CPU cycles so that their
218 Although CPU intensive work items don't contribute to the
221 non-CPU-intensive work items can delay execution of CPU
233 CPU which can be assigned to the work items of a wq. For example,
235 executing at the same time per CPU.
261 Work items w0, w1, w2 are queued to a bound wq q0 on the same CPU.
262 w0 burns CPU for 5ms then sleeps for 10ms then burns CPU for 5ms
263 again before finishing. w1 and w2 burn CPU for 5ms then sleep for
271 0 w0 starts and burns CPU
273 15 w0 wakes up and burns CPU
275 20 w1 starts and burns CPU
278 35 w2 starts and burns CPU
285 0 w0 starts and burns CPU
287 5 w1 starts and burns CPU
289 10 w2 starts and burns CPU
291 15 w0 wakes up and burns CPU
299 0 w0 starts and burns CPU
301 5 w1 starts and burns CPU
303 15 w0 wakes up and burns CPU
306 20 w2 starts and burns CPU
314 0 w0 starts and burns CPU
316 5 w1 and w2 start and burn CPU
319 15 w0 wakes up and burns CPU
347 * Unless work items are expected to consume a huge amount of CPU