On Tue, Nov 04, 2014 at 04:23:45PM +0800, Wanpeng Li wrote: > On Tue, Nov 04, 2014 at 09:32:25AM +0100, Peter Zijlstra wrote: > >On Tue, Nov 04, 2014 at 07:57:48AM +0800, Wanpeng Li wrote: > >> On Mon, Nov 03, 2014 at 11:41:11AM +0100, Peter Zijlstra wrote: > > > >> >On Fri, Oct 31, 2014 at 03:28:17PM +0800, Wanpeng Li wrote: > >> >So what is wrong with making dl_task_timer() deal with it? The timer > >> >will still fire on the correct time, canceling it and or otherwise > >> >messing with the CBS is wrong. Once it fires, all we need to do is > >> >migrate it to another cpu (preferably one that is still online of course > >> >:-). > > > >> Do you mean what I need to do is push the task to another cpu in > >> dl_task_timer() > >> if rq is offline? > > > >That does indeed appear to be the sensible fix to me. > > > >> In addition, what will happen if dl task can't preempt on > >> another cpu? > > > >So if we find that the rq the task was on is no longer available, we > >need to select a new rq, the 'right' rq would be the one running the > >latest deadline. > > > >If it cannot preempt the latest (running) deadline, it was not eligible > >for running in the first place so no worries, right? > > I think this will lead to this deadline task cannot running on any rqs any > more. > If my understanding is not right, when it will be picked?
So you unconditionally place it on the rq with the latest deadline. If it cannot preempt, at least its on an online cpu. It will get scheduled whenever its deadline is one of the N earliest, with N the number of online CPUs. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
