Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-27 Thread Raghavendra K T
On 01/26/2013 12:19 AM, Ingo Molnar wrote: * Raghavendra K T wrote: On 01/25/2013 04:17 PM, Ingo Molnar wrote: * Raghavendra K T wrote: * Ingo Molnar [2013-01-24 11:32:13]: * Raghavendra K T wrote: From: Peter Zijlstra In case of undercomitted scenarios, especially in large gues

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-25 Thread Ingo Molnar
* Raghavendra K T wrote: > On 01/25/2013 04:17 PM, Ingo Molnar wrote: > > > >* Raghavendra K T wrote: > > > >>* Ingo Molnar [2013-01-24 11:32:13]: > >> > >>> > >>>* Raghavendra K T wrote: > >>> > From: Peter Zijlstra > > In case of undercomitted scenarios, especially in large gu

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-25 Thread Raghavendra K T
On 01/25/2013 04:35 PM, Andrew Jones wrote: On Fri, Jan 25, 2013 at 04:10:25PM +0530, Raghavendra K T wrote: * Ingo Molnar [2013-01-24 11:32:13]: * Raghavendra K T wrote: From: Peter Zijlstra In case of undercomitted scenarios, especially in large guests yield_to overhead is significant

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-25 Thread Raghavendra K T
On 01/25/2013 04:17 PM, Ingo Molnar wrote: * Raghavendra K T wrote: * Ingo Molnar [2013-01-24 11:32:13]: * Raghavendra K T wrote: From: Peter Zijlstra In case of undercomitted scenarios, especially in large guests yield_to overhead is significantly high. when run queue length of sour

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-25 Thread Andrew Jones
On Fri, Jan 25, 2013 at 04:10:25PM +0530, Raghavendra K T wrote: > * Ingo Molnar [2013-01-24 11:32:13]: > > > > > * Raghavendra K T wrote: > > > > > From: Peter Zijlstra > > > > > > In case of undercomitted scenarios, especially in large guests > > > yield_to overhead is significantly high.

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-25 Thread Ingo Molnar
* Raghavendra K T wrote: > * Ingo Molnar [2013-01-24 11:32:13]: > > > > > * Raghavendra K T wrote: > > > > > From: Peter Zijlstra > > > > > > In case of undercomitted scenarios, especially in large guests > > > yield_to overhead is significantly high. when run queue length of > > > source

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-25 Thread Raghavendra K T
* Ingo Molnar [2013-01-24 11:32:13]: > > * Raghavendra K T wrote: > > > From: Peter Zijlstra > > > > In case of undercomitted scenarios, especially in large guests > > yield_to overhead is significantly high. when run queue length of > > source and target is one, take an opportunity to bail

Re: [PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-24 Thread Ingo Molnar
* Raghavendra K T wrote: > From: Peter Zijlstra > > In case of undercomitted scenarios, especially in large guests > yield_to overhead is significantly high. when run queue length of > source and target is one, take an opportunity to bail out and return > -ESRCH. This return condition can be f

[PATCH V3 RESEND RFC 1/2] sched: Bail out of yield_to when source and target runqueue has one task

2013-01-21 Thread Raghavendra K T
From: Peter Zijlstra In case of undercomitted scenarios, especially in large guests yield_to overhead is significantly high. when run queue length of source and target is one, take an opportunity to bail out and return -ESRCH. This return condition can be further exploited to quickly come out of