Messages in this thread | | | Date | Fri, 19 Jan 2001 12:32:30 -0800 | From | Mike Kravetz <> | Subject | Re: [Lse-tech] Re: multi-queue scheduler update |
| |
On Fri, Jan 19, 2001 at 03:12:11PM -0500, Mark Hahn wrote: > > incurred in the current implementation. To maintain existing > > scheduler behavior, we look at all CPU specific runqueues to find > > the highest priority (goodness) task in the system. Therefore, > > do you have cpu-affinity? the mainstream scheduler at one time > actually tuned the decision to move a task based on its expected > timeslice and the worstcase cache-flush time.
We use the same same cpu-affinity mechanism as the current scheduler. This simply gives a 'priority boost' to tasks that last ran on the current CPU. In our multi-queue scheduler, tasks on a remote queue must have high enough priority (to overcome this boost) before being moved to the local queue.
-- Mike Kravetz mkravetz@sequent.com IBM Linux Technology Center 15450 SW Koll Parkway Beaverton, OR 97006-6063 (503)578-3494 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |