[lkml]   [2011]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch 4/4] sched: Distangle worker accounting from rq->lock
    Hello, Thomas.

    The hooking place doesn't have anything to do with rq->lock. The
    problem with Peter's patch was preemption, not the lock.

    > There is also no harm from updating nr_running when the task returns
    > from scheduling instead of accounting it in the wakeup code.

    Well, not exactly. If CPU is being thrashed, we don't want to try to
    fire up new workers or calling in rescuers. If nr_running is bumped
    up from ttwu(), a woken up but not yet running worker already counts
    as running. With the suggested change, when we hit such heavy CPU
    thrashing, workqueue code will add things on top of it.



     \ /
      Last update: 2011-06-23 10:47    [W:0.023 / U:9.348 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site