Lines Matching +full:20 +full:system

33 thread system-wide.  A single MT wq needed to keep around the same
43 while an ST wq one for the whole system.  Work items had to compete for
120 Minimal to save resources and sufficient in that the system is used at
201     managed by the system scheduler.
204   A freezable wq participates in the freeze phase of the system
228   execution is regulated by the system scheduler.
285  20		w0 finishes
286  20		w1 starts and burns CPU
303  20		w0 finishes
304  20		w1 wakes up and finishes
315  20		w0 finishes
316  20		w1 wakes up and finishes
317  20		w2 starts and burns CPU
331  20		w0 finishes
332  20		w1 wakes up and finishes
356   special attribute, can use one of the system wq.  There is no
358   and a system wq.
399 ``system``
422   anywhere in the system as it sees fit. This enables benefiting from scope
443 cause lower overall system utilization if the work items are not spread
470    :widths: 16 20 20
477    * - system
489 With enough issuers spread across the system, there is no downside to
506 system.
509    :widths: 16 20 20
516    * - system
528 This is more than enough work to saturate the system. Both "system" and
531 "system".
548 reduced to four, there now isn't enough work to saturate the whole system
552    :widths: 16 20 20
559    * - system
572 2% bandwidth loss compared to "system" and "cache (struct)" whopping 20%.
579 scope over "system" is, while consistent and noticeable, small. However, the
642   SYSTEM
651   pool[01] ref= 1 nice=-20 idle/workers=  2/  2 cpu=  0
653   pool[03] ref= 1 nice=-20 idle/workers=  2/  2 cpu=  1
655   pool[05] ref= 1 nice=-20 idle/workers=  2/  2 cpu=  2
657   pool[07] ref= 1 nice=-20 idle/workers=  2/  2 cpu=  3
661   pool[11] ref= 1 nice=-20 idle/workers=  1/  1 cpus=0000000f
662   pool[12] ref= 2 nice=-20 idle/workers=  1/  1 cpus=00000003
663   pool[13] ref= 2 nice=-20 idle/workers=  1/  1 cpus=0000000c
766 executed by at most one worker system-wide at any given time.