![]() | |||||||||||||
Messages in this thread |
On Sun, May 25, 2003 at 11:27:20AM +1000, Con Kolivas wrote: > Even though you're not Marc I do agree with you. The problem is well > described as either poor interactivity (the window wiggle test) or > starvation in the presence of certain scheduler hogs (for whatever > reason) since the interactivity patch from mingo. Dropping the max > timeslice is a bandaid but destroys priority based timeslice > scheduling. Dropping the min timeslice will bring this back, but at > some point the timeslice will be so low that low priority cpu > intensive tasks will spend most of their time cache trashing. The fact that it's a "bandaid" and that it "destroys priority-based timeslice scheduling" makes it a shenanigan. If you're having problems solved by capping timeslices, you have someone's timeslice and/or priority growing too large for some reason. It'd be far better to help figure out what went wrong. -- wli - 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/ | ||||||||||||
| Last update: 2005-03-22 12:35 [from the cache] ©2003-2008 | |||||||||||||