On 4 November 2014 20:52, Steven Rostedt <[email protected]> wrote: > On Tue, 4 Nov 2014 19:13:01 +0800 > "pang.xunlei" <[email protected]> wrote: > >> When selecting the cpu for a waking RT task, if curr is a non-RT >> task which is bound only on this cpu, then we can give it a chance >> to select a different cpu(definitely an idle cpu if existing) for >> the RT task to avoid curr starving. > > Absolutely not! An RT task doesn't give a crap if a non RT task is > bound to a CPU or not. We are not going to migrate an RT task to be > nice to a bounded non-RT task. > > Migration is not cheap. It causes cache misses and TLB flushes. This is > not something that should be taken lightly. Ok, thanks! But I think the PUSH operation optimized by the former patch is reasonable, since PUSH itselft does involve the Migration. Do I miss something?
> > Nack > > -- Steve > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
