Lines Matching full:given

95 tasks assigned to it, the CPU will load the given task's context and run its
102 assigned to the given CPU and the CPU is then regarded as idle.  In other words,
136 spend in the given state, including the time needed to enter it (which may be
143 the time needed to enter the given state in case the wakeup occurs when the
150 when they will trigger, and it is the maximum time the hardware that the given
194 allow them to make reasonable progress in a given time frame is to make them
196 given a slice of the CPU time to run its code, subject to the scheduling class,
217 tick goes away if the given CPU is idle.  Consequently, it is possible to stop
256 which the tick cannot be stopped.  If the given system is tickless, it will use
279 One of them is used when tasks previously running on the given CPU are waiting
285 The correction factor for the given sleep length range (determined before
317 previously ran on the given CPU and now they are waiting for I/O operations to
348 given conditions.  However, it applies a different approach to that problem.
354 that were running on the given CPU in the past and are waiting on some I/O
368 The ``hits`` and ``misses`` metrics measure the likelihood that a given idle
375 former condition is satisfied and the target residency of the given idle state
378 (that is, it is increased when the given idle state "matches" both the sleep
380 increased when the given idle state "matches" the sleep length only and the
383 The ``early_hits`` metric measures the likelihood that a given idle state will
389 deeper than the given one).
478 statistics of the given idle state.  That information is exposed by the kernel
482 directory in ``sysfs``, where the number ``<N>`` is assigned to the given
485 objects defined for the given CPU minus one.  Each of these directories
524 	Total time spent in this idle state by the given CPU (as measured by the
528 	Total number of times the hardware has been asked by the given CPU to
532 	Total number of times a request to enter this idle state on the given
541 given idle state is disabled for this particular CPU, which means that the
550 If the :file:`disable` attribute contains 0, the given idle state is enabled for
554 take it into consideration for the given CPU and the driver to ask for it,
566 really spent by the given CPU in the given idle state, because it is measured by
582 and :file:`rejected` files report the number of times the given idle state
657 the given CPU as the upper limit for the exit latency of the idle states that
723 where ``<n>`` is an idle state index also used in the name of the given