lkml.org 
[lkml]   [2009]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] Re: scheduler oddity [bug?]

* Mike Galbraith <efault@gmx.de> wrote:

> On Sun, 2009-03-08 at 18:52 +0100, Ingo Molnar wrote:
> > * Mike Galbraith <efault@gmx.de> wrote:
> >
> > > On Sun, 2009-03-08 at 16:39 +0100, Ingo Molnar wrote:
> > > > * Mike Galbraith <efault@gmx.de> wrote:
> > > >
> > > > > The problem with your particular testcase is that while one
> > > > > half has an avg_overlap (what we use as affinity hint for
> > > > > synchronous wakeups) which triggers the affinity hint, the
> > > > > other half has avg_overlap of zero, what it was born with, so
> > > > > despite significant execution overlap, the scheduler treats
> > > > > them as if they were truly synchronous tasks.
> > > >
> > > > hm, why does it stay on zero?
> > >
> > > Wakeup preemption. Presuming here: heavy task wakes light
> > > task, is preempted, light task stuffs data into pipe, heavy
> > > task doesn't block, so no avg_overlap is ever computed. The
> > > heavy task uses 100% CPU.
> > >
> > > Running as SCHED_BATCH (virgin source), it becomes sane.
> >
> > ah.
> >
> > I'd argue then that time spent on the rq preempted _should_
> > count in avg_overlap statistics. I.e. couldnt we do something
> > like ... your patch? :)
> >
> > > > if (sleep && p->se.last_wakeup) {
> > > > update_avg(&p->se.avg_overlap,
> > > > p->se.sum_exec_runtime - p->se.last_wakeup);
> > > > p->se.last_wakeup = 0;
> > > > - }
> > > > + } else if (p->se.avg_overlap < limit && runtime >= limit)
> > > > + update_avg(&p->se.avg_overlap, runtime);
> >
> > Just done unconditionally, i.e. something like:
> >
> > if (sleep) {
> > runtime = p->se.sum_exec_runtime - p->se.last_wakeup;
> > p->se.last_wakeup = 0;
> > } else {
> > runtime = p->se.sum_exec_runtime - p->se.prev_sum_exec_runtime;
> > }
> >
> > update_avg(&p->se.avg_overlap, runtime);
> >
> > ?
>
> OK, I've not seen any problem indications yet, so find patchlet below.
>
> However! Balazs has stated that this problem is _not_ present in .git,
> and that..
>
> commit 38736f475071b80b66be28af7b44c854073699cc
> Author: Gautham R Shenoy <ego@in.ibm.com>
> Date: Sat Sep 6 14:50:23 2008 +0530
>
> ..is what fixed it. Willy Tarreau verified this as being the case on
> his HW as well. It is present in .git with my HW.
>
> I see it as a problem, but it's your call. Dunno if I'd apply it or
> hold back, given these conflicting reports.

I think we still want it - as the purpose of the overlap metric
is to measure reality. If preemption causes overlap in execution
we should not ignore that.

The fact that your hw triggers it currently is enough of a
justification. Gautham's change to load-balancing might have
shifted the preemption and migration characteristics on his box
just enough to not trigger this - but it does not 'fix' the
problem per se.

Peter, what do you think?

Ingo


\
 
 \ /
  Last update: 2009-03-09 09:09    [W:0.094 / U:6.408 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site