On Tue, 2010-12-14 at 15:54 +0530, Srivatsa Vaddagiri wrote:
quoted text
> On Tue, Dec 14, 2010 at 07:08:16AM +0100, Mike Galbraith wrote:

quoted text
> > That part looks ok, except for the yield cross cpu bit.  Trying to yield
> > a resource you don't have doesn't make much sense to me.
> 
> So another (crazy) idea is to move the "yieldee" task on another cpu over to 
> yielding task's cpu, let it run till the end of yielding tasks slice and then
> let it go back to the original cpu at the same vruntime position!

Yeah, pulling the intended recipient makes fine sense.  If he doesn't
preempt you, you can try to swap vruntimes or whatever makes arithmetic
sense and will help.  Dunno how you tell him how long he can keep the
cpu though, and him somehow going back home needs to be a plain old
migration, no fancy restoration of ancient history vruntime.

	-Mike

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/