![]() | ||||||||||
Messages in this thread |
On Wed, Jun 18, 2003 at 06:44:42PM -0700, Perez-Gonzalez, Inaky wrote: > > Now that we are at that, it might be wise to add a higher-than-anything > priority that the kernel code can use (what would be 100 for user space, > but off-limits), so even FIFO 99 code in user space cannot block out > the migration thread, keventd and friends. I would prefer users have the ability to put one or two truly critical RT tasks above keventd & family. Such tasks would have to follow certain rules .. run & sleep quick .. limited or no device IO .. most communication to other tasks through shared memory .. possibly others. There are those willing to follow whatever rules necessary & split up their application into tasks any which way in order to get high responsiveness to a critical but small part of their application. If you follow the rules, you should be allowed to put a carefully crafted task above the system daemons (with the possible exception of the migration daemon). Joe - 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:36 [from the cache] ©2003-2008 | ||||||||||