Messages in this thread | | | Subject | Re: [PATCH 06/16] sched: SCHED_DEADLINE push and pull logic | From | Steven Rostedt <> | Date | Thu, 12 Apr 2012 09:35:38 -0400 |
| |
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 > > > >
| |