On Fri, 2015-01-09 at 11:24 -0800, Yogesh Ahire wrote:
> Thank you Mike. I didn't get what you mean by saying "its gona try to
> yield for one hell of a long time before it succeeds".
Look at vruntimes. Equalizing same is what the scheduler does for a
living, it does so by giving the CPU to the
Thank you Mike. I didn't get what you mean by saying "its gona try to
yield for one hell of a long time before it succeeds".
On Thu, Jan 8, 2015 at 7:14 PM, Mike Galbraith wrote:
> On Thu, 2015-01-08 at 10:00 -0500, Yogesh Ahire wrote:
>> Thank you Mike. But I can see there are tasks with same
On Fri, 2015-01-09 at 11:24 -0800, Yogesh Ahire wrote:
Thank you Mike. I didn't get what you mean by saying its gona try to
yield for one hell of a long time before it succeeds.
Look at vruntimes. Equalizing same is what the scheduler does for a
living, it does so by giving the CPU to the
Thank you Mike. I didn't get what you mean by saying its gona try to
yield for one hell of a long time before it succeeds.
On Thu, Jan 8, 2015 at 7:14 PM, Mike Galbraith umgwanakikb...@gmail.com wrote:
On Thu, 2015-01-08 at 10:00 -0500, Yogesh Ahire wrote:
Thank you Mike. But I can see there
On Thu, 2015-01-08 at 10:00 -0500, Yogesh Ahire wrote:
> Thank you Mike. But I can see there are tasks with same priority and
> are runnable waiting for CPU, following is the output of
> /proc/sched_debug where you can see that the task "symphonyapp"
> continuously calls sched_yield() but there
Thank you Mike. But I can see there are tasks with same priority and
are runnable waiting for CPU, following is the output of
/proc/sched_debug where you can see that the task "symphonyapp"
continuously calls sched_yield() but there are other tasks which are
ready to run are not getting CPU and
On Thu, 2015-01-08 at 10:00 -0500, Yogesh Ahire wrote:
Thank you Mike. But I can see there are tasks with same priority and
are runnable waiting for CPU, following is the output of
/proc/sched_debug where you can see that the task symphonyapp
continuously calls sched_yield() but there are
Thank you Mike. But I can see there are tasks with same priority and
are runnable waiting for CPU, following is the output of
/proc/sched_debug where you can see that the task symphonyapp
continuously calls sched_yield() but there are other tasks which are
ready to run are not getting CPU and are
On Wed, 2015-01-07 at 16:30 -0500, Yogesh Ahire wrote:
> Hi All,
>
> I have a system with multiple CPU cores. I have multiple threads
> assigned to particular CPU. Among these threads the main thread calls
> sched_yield() if it has nothing to do, I am hoping that doing so will
> give chance to
Hi All,
I have a system with multiple CPU cores. I have multiple threads
assigned to particular CPU. Among these threads the main thread calls
sched_yield() if it has nothing to do, I am hoping that doing so will
give chance to other threads to run. But the strange behavior of
sched_yield() is ,
On Wed, 2015-01-07 at 16:30 -0500, Yogesh Ahire wrote:
Hi All,
I have a system with multiple CPU cores. I have multiple threads
assigned to particular CPU. Among these threads the main thread calls
sched_yield() if it has nothing to do, I am hoping that doing so will
give chance to other
Hi All,
I have a system with multiple CPU cores. I have multiple threads
assigned to particular CPU. Among these threads the main thread calls
sched_yield() if it has nothing to do, I am hoping that doing so will
give chance to other threads to run. But the strange behavior of
sched_yield() is ,
12 matches
Mail list logo
