Lines Matching full:time
63 idle time calculations based on the timing of dequeue events and
67 Shaping is done using link idle time calculations, and actions taken if
71 be idle 90% of the time. If it isn't, it needs to be throttled so that it
72 IS idle 90% of the time.
75 derives the idle time from the number of microseconds (in fact, jiffies)
85 designed - again, how do we calculate the idle time?
97 The calculated idle time is subtracted from the EWMA measured one,
111 amount of time that was calculated to pass between packets, and then
239 for a packet for enough time for the avgidle to increase above zero.
262 To determine the idle time, CBQ must know the bandwidth of your underlying
267 The cell size determines he granularity of packet transmission time calculations. Has a sensible default.
270 A zero sized packet may still take time to transmit. This value is the lower
271 cap for packet transmission time calculations - packets smaller than this value
275 When CBQ needs to measure the average idle time, it does so using an
335 idle time, and pass 1 packet. However, Unix kernels generally have a
336 hard time scheduling events shorter than 10ms, so it is better to
340 The time to wait is called the offtime. Higher values of minburst lead
348 burst from shutting down the link for a prolonged period of time,
387 the time constant can be specified, also in microseconds. The
388 .B time constant
