Searched +refs:is +refs:scheduled +refs:pipeline (Results 1 – 3 of 3) sorted by relevance
| /Linux-v6.6/Documentation/scheduler/ |
| D | sched-capacity.rst | 16 CPU capacity is a measure of the performance a CPU can reach, normalized against
28 performance-oriented than the LITTLE ones (more pipeline stages, bigger caches,
32 CPU performance is usually expressed in Millions of Instructions Per Second
42 ``capacity_orig`` is its maximum attainable capacity, i.e. its maximum
43 attainable performance level. A CPU's ``capacity`` is its ``capacity_orig`` to
44 which some loss of available performance (e.g. time spent handling IRQs) is
47 Note that a CPU's ``capacity`` is solely intended to be used by the CFS class,
48 while ``capacity_orig`` is class-agnostic. The rest of this document will use
121 performance is somewhat of a contentious point. The relative performance
134 while task utilization is specific to CFS, it is convenient to describe it here
[all …]
|
| /Linux-v6.6/tools/perf/Documentation/ |
| D | perf-stat.txt | 39 - a raw PMU event in the form of rN where N is a hexadecimal value
52 'percore' is a event qualifier that sums up the event counts for both
66 'uncore_' is also ignored when performing this match.
109 The default path is /sys/fs/bpf/perf_attr_map.
124 system-wide collection from all CPUs (default if no target is specified)
151 In per-thread mode, this option is ignored. The -a option is still necessary
152 to activate system-wide monitoring. Default is to count on all CPUs.
192 monitor only in the container (cgroup) called "name". This option is available only
195 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
196 to first event, second cgroup to second event and so on. It is possible to provide
[all …]
|
| /Linux-v6.6/Documentation/RCU/ |
| D | torture.rst | 11 The CONFIG_RCU_TORTURE_TEST config option is available for all RCU
15 command (perhaps grepping for "torture"). The test is started
16 when the module is loaded, and stops when the module is unloaded.
24 The statistics output is as follows::
52 containing structures to be placed into the "rtc" area is empty.
53 This condition is important, since it can fool you into thinking
54 that RCU is working when it is not. :-/
59 failed due to the list being empty. It is not unusual for this
60 to be non-zero, but it is bad for it to be a large fraction of
70 family of functions is not working correctly.
[all …]
|
