Re: Scheduling the highest priority task

2007-08-02 Thread Martin Roehricht
On 02.08.2007 21:48, Ingo Molnar wrote: * Martin Roehricht <[EMAIL PROTECTED]> wrote: On 08/02/2007 05:19 PM, Ingo Molnar wrote: >* Martin Roehricht <[EMAIL PROTECTED]> wrote: > >>That's fine with me, that within the same priority-queue any task can >>be chosen. But assume two tasks with highl

Re: Scheduling the highest priority task

2007-08-02 Thread Ingo Molnar
* Martin Roehricht <[EMAIL PROTECTED]> wrote: > On 08/02/2007 05:19 PM, Ingo Molnar wrote: > >* Martin Roehricht <[EMAIL PROTECTED]> wrote: > > > >>That's fine with me, that within the same priority-queue any task can > >>be chosen. But assume two tasks with highly different priorities, such >

Re: Scheduling the highest priority task

2007-08-02 Thread Martin Roehricht
On 08/02/2007 05:19 PM, Ingo Molnar wrote: * Martin Roehricht <[EMAIL PROTECTED]> wrote: That's fine with me, that within the same priority-queue any task can be chosen. But assume two tasks with highly different priorities, such as 105 and 135 are scheduled on the same processor and one of th

Re: Scheduling the highest priority task

2007-08-02 Thread Ingo Molnar
* Martin Roehricht <[EMAIL PROTECTED]> wrote: > That's fine with me, that within the same priority-queue any task can > be chosen. But assume two tasks with highly different priorities, such > as 105 and 135 are scheduled on the same processor and one of them is > now to be migrated -- shouldn

Re: Scheduling the highest priority task

2007-08-02 Thread Martin Roehricht
On 08/02/2007 05:03 PM, Ingo Molnar wrote: * Martin Roehricht <[EMAIL PROTECTED]> wrote: On 08/02/2007 01:40 PM, Ingo Molnar wrote: >in the SMP migration code, the 'old scheduler' indeed picks the lowest >priority one, _except_ if that task is running on another CPU or is too >'cache hot':

Re: Scheduling the highest priority task

2007-08-02 Thread Ingo Molnar
* Martin Roehricht <[EMAIL PROTECTED]> wrote: > On 08/02/2007 01:40 PM, Ingo Molnar wrote: > >in the SMP migration code, the 'old scheduler' indeed picks the lowest > >priority one, _except_ if that task is running on another CPU or is too > >'cache hot': > > But why is it, that the scheduler

Re: Scheduling the highest priority task

2007-08-02 Thread Martin Roehricht
On 08/02/2007 01:40 PM, Ingo Molnar wrote: in the SMP migration code, the 'old scheduler' indeed picks the lowest priority one, _except_ if that task is running on another CPU or is too 'cache hot': But why is it, that the scheduler picks the lowest priority one? I thought sched_find_first_bi

Re: Scheduling the highest priority task

2007-08-02 Thread Ingo Molnar
* Martin Roehricht <[EMAIL PROTECTED]> wrote: > perhaps someone can give me a hint what I should consider to look for in > order to change the ("old" 2.6.21) scheduler such that it schedules the > highest priority task of a given runqueue. > Given a multiprocessor system I currently observe tha

Scheduling the highest priority task

2007-08-02 Thread Martin Roehricht
Hi, perhaps someone can give me a hint what I should consider to look for in order to change the ("old" 2.6.21) scheduler such that it schedules the highest priority task of a given runqueue. Given a multiprocessor system I currently observe that whenever there are two tasks on one CPU, the lo