![]() | |||||||||||
Messages in this thread |
* Con Kolivas <kernel@kolivas.org> wrote: > However the non-interactive mode addresses a number of different needs > that seem to have come up. Specifically: > I have had users report great success with such a mode on my own > scheduler in multiple X session setups where very choppy behaviour > occurs in mainline. since SCHED_CPUBOUND would be inherited across fork(), it should be rather easy to start an X session with all tasks as SCHED_CPUBOUND. but i think the above rather points in the direction of some genuine weakness in the interactivity code (i know, for which the fix is staircase ;) which would be nice to debug. > Many high performance computing people do not wish interactivity code > modifying their choice of latency/distribution - admittedly this is a > soft one. well, SCHED_CPUBOUND would solve their needs too, right? Ingo - 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 14:07 [from the cache] ©2003-2008 | |||||||||||