>How is that different from any other time a task has to yield the CPU >for a bit? While your high priority task is blocked for whatever >reason, a lower priority task gets to use the CPU.
As the submitter of the bug, let me give you my perspective. SCHED_FIFO means run my task until it blocks or a higher priority task pre-empts it. Period. mlock() doesn't block. check the man page. Any other way and you are not able to use priority based scheduling. --bud davis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
