> So we can have simply two queues ( per CPU ), one that stores I/O bound (
> counter > K for example ) and RT tasks that is walked entirely searching
> for the better tasks, the other queue will store CPU bound tasks that are
> executed in a FIFO policy.
Oh as an aside btw - there are many real world workloads where we have a lot
of non cpu hog processes running. A lot of messaging systems have high task
switch rates but very few cpu hogs. So you still need to handle the non hogs
carefully to avoid degenerating back into Linus scheduler.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:16 EST