lkml.org 
[lkml]   [2014]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 2/2] sched: Rewrite per entity runnable load average tracking
    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


    \
     
     \ /
      Last update: 2014-07-11 10:21    [W:4.709 / U:0.048 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site