On Tue, 2013-02-12 at 08:06 +0100, Mike Galbraith wrote:
> On Tue, 2013-02-12 at 01:31 +0400, Kirill Tkhai wrote:
> > It's possible a situation when rq->rt is throttled or
> > it has no child entities and there are RT tasks ready
> > for execution in the rq which are the only tasks
> > of
On Tue, 2013-02-12 at 09:12 +0100, Stanislav Meduna wrote:
> On 12.02.2013 08:06, Mike Galbraith wrote:
>
> >> In this case pick_next_task takes idle tasks and idle wastes cpu
> >> time.
>
> > That's not a waste of CPU time, that's utilization enforcement the thing
> > it is designed to do.
>
On 12.02.2013 08:06, Mike Galbraith wrote:
>> In this case pick_next_task takes idle tasks and idle wastes cpu
>> time.
> That's not a waste of CPU time, that's utilization enforcement the thing
> it is designed to do.
Well this is a philosophical question and the opinions will IMHO
vary
On 12.02.2013 08:06, Mike Galbraith wrote:
In this case pick_next_task takes idle tasks and idle wastes cpu
time.
That's not a waste of CPU time, that's utilization enforcement the thing
it is designed to do.
Well this is a philosophical question and the opinions will IMHO
vary strongly. If
On Tue, 2013-02-12 at 09:12 +0100, Stanislav Meduna wrote:
On 12.02.2013 08:06, Mike Galbraith wrote:
In this case pick_next_task takes idle tasks and idle wastes cpu
time.
That's not a waste of CPU time, that's utilization enforcement the thing
it is designed to do.
Well this is
On Tue, 2013-02-12 at 08:06 +0100, Mike Galbraith wrote:
On Tue, 2013-02-12 at 01:31 +0400, Kirill Tkhai wrote:
It's possible a situation when rq-rt is throttled or
it has no child entities and there are RT tasks ready
for execution in the rq which are the only tasks
of TASK_RUNNING
On Tue, 2013-02-12 at 01:31 +0400, Kirill Tkhai wrote:
> It's possible a situation when rq->rt is throttled or
> it has no child entities and there are RT tasks ready
> for execution in the rq which are the only tasks
> of TASK_RUNNING state. In this case pick_next_task
> takes idle tasks and
It's possible a situation when rq->rt is throttled or
it has no child entities and there are RT tasks ready
for execution in the rq which are the only tasks
of TASK_RUNNING state. In this case pick_next_task
takes idle tasks and idle wastes cpu time.
The patch change logic of pre_schedule a
It's possible a situation when rq-rt is throttled or
it has no child entities and there are RT tasks ready
for execution in the rq which are the only tasks
of TASK_RUNNING state. In this case pick_next_task
takes idle tasks and idle wastes cpu time.
The patch change logic of pre_schedule a little
On Tue, 2013-02-12 at 01:31 +0400, Kirill Tkhai wrote:
It's possible a situation when rq-rt is throttled or
it has no child entities and there are RT tasks ready
for execution in the rq which are the only tasks
of TASK_RUNNING state. In this case pick_next_task
takes idle tasks and idle
10 matches
Mail list logo