lkml.org 
[lkml]   [2010]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH 3/4] tracing/sched: Add sched_rt_push and sched_rt_pull tracepoints
    From
    Date
    On Tue, 2010-09-21 at 10:46 +0200, Peter Zijlstra wrote:
    > On Mon, 2010-09-20 at 22:40 -0400, Steven Rostedt wrote:
    > > From: Steven Rostedt <srostedt@redhat.com>
    > >
    > > Seeing how tasks are affected by the push/pull algorithm of the RT
    > > scheduler helps in understanding the migration of RT tasks.
    > >
    > > Adding these two tracepoints to show when an RT task is pushed from
    > > one CPU to another, or pulled helps with analyzing the way the
    > > scheduler works.
    >
    > Why doesn't the migration tracepoint cover this? It shows you the task,
    > the prio, the old and new cpu. If the migration is logged from the old
    > cpu, its a push, if its logged from the new its a pull, no?

    For some reason it did not help me enough in my analysis. I'll go back
    and see why.

    I originally had these tracepoints at the front of the series, and
    realized they may be a little controversial, thus I moved them to the
    end.

    -- Steve




    \
     
     \ /
      Last update: 2010-09-21 14:35    [W:0.028 / U:0.104 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site