[lkml]   [2003]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] Re: Blender profiling-1 O16.2int
    On Sun, Aug 17, 2003 at 11:36:42PM +1000, Con Kolivas wrote:
    > Now for those that can't see what this is, blender and X are
    > interactive tasks and getting high priority (PRI < 18) which makes
    > sense. During heavy usage of blender, it is X that gets pegged for
    > cpu usage (ie it is doing the work for blender), and eventually it
    > gets expired onto the expired array for being naughty and stops doing
    > anything till all other tasks have finished working on the active
    > array. Now normally, blender should just sleep and wait till X comes
    > alive again before it does anything. However here it shows clearly that
    > it is spinning madly looking for something from X, and poor X can't do
    > anything. This is the busy on wait I've described. Meanwhile, since blender
    > was seen as an interactive task (which it is), it preempts everything lower
    > priority than it till it also gets booted.

    Ugh, priority inversion.

    -- wli
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:47    [W:0.020 / U:4.376 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site