[lkml]   [2010]   [Apr]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [REGRESSION 2.6.30][PATCH 1/1] sched: defer idle accounting till after load update period
    On Thu, Apr 1, 2010 at 4:18 PM, Thomas Gleixner <> wrote:
    > Also we need to think about a more clever way than just accounting the
    > number of running and uninterruptible tasks. What we really want is to
    > use the numbers which the scheduler has handy, i.e how many tasks did
    > we run since we did the last loadavg calculation. It was always
    > possible (even before the big loadavg changes) to create a task which
    > consumes 50% of a CPU and never shows up in the loadavg calculations
    > at all.

    I'm not sure I follow how knowing how many tasks have been run since
    the last LOAD_FREQ expiration will help, or is that just an example of
    the kind of data the scheduler has available that may be useful?

    -- Chase

     \ /
      Last update: 2010-04-01 22:35    [W:0.018 / U:1.268 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site