On Thu, Jul 10, 2014 at 12:08:59PM +0200, Peter Zijlstra wrote: > > Since clock_task is the regular clock minus some local amount, the > difference between two regular clock reads is always a strict upper > bound on clock_task differences. > This is inspiring. Regarding the clock source in load avg tracking, should we simply use rq_clock_task instead of cfs_rq_clock_task.
For the bandwidth control case, just update/increase the last_update_time when unthrottled by this throttled time, so the time would look like freezed. Am I understanding right? Not sure how much bandwidth control is used, but even not used, every time we read cfs_rq_clock_task, will burn useless cycles here. Thanks, Yuyang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
