lkml.org 
[lkml]   [2012]   [Apr]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 06/16] sched: SCHED_DEADLINE push and pull logic
From
Date
On Thu, 2012-04-12 at 20:56 +0800, Hillf Danton wrote:

> >> if (2 == dl_nr_migratory + dl_nr_total)
> >> rq was not overloaded;
> >>
> >> after enqueuing a deadline task that is not migratory,
> >
> > Now rq would be overloaded because:
> >
> > dl_nr_migratory + dl_nr_total == 3
> >
>
> Which is the current task, and where?

More riddles?

The current task is the one executing on the CPU.

-- Steve

>
> >
> >>
> >> if (current task is not preempted)
> >> rq remains not overloaded;
> >
> > s/not//
> >
> >>
> >> else if (current task is not pushed out) {
> >> if (rq is not overloaded)
> >> maintenance of overloaded is __corrupted__;
> >> }
> >>
> >> btw, same behavior in RTS?
> >
> > I still don't understand what you are saying.
> >
> > I can see your scenario happening with the change you are suggesting
> > though.
> >
> > -- Steve
> >
> >




\
 
 \ /
  Last update: 2012-04-12 15:37    [W:0.183 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site