Messages in this thread | | | Subject | Re: 2.6.X, NPTL, SCHED_FIFO and JACK | Date | Wed, 30 Jun 2004 12:12:39 -0400 | From | Paul Davis <> |
| |
>another question: do all JACK threads run at SCHED_FIFO, and do they all >have the same rt_priority value?
They don't all run SCHED_FIFO. Just two threads in the server (one is a watchdog designed to prevent system lockups) and at least one in each client (there may be more depending on what the client does, but its not created by JACK and JACK doesn't know about it). The client threads run at 1 level lower priority than the servers main thread, and that runs 1 level lower than the watchdog.
but ...
>it seems part of the problem is that the setscheduler() calls 'succeed', >but the policy is not changed to SCHED_FIFO. The question here is, >are the correct PIDs used?
this has me thinking. one of the major changes with NPTL is that all threads share the same PID. so how in the world do we ever set the scheduling policy of a single thread (as opposed to something identified by a pid_t) to SCHED_FIFO?
--p - 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/
| |