Messages in this thread | | | Date | Wed, 30 Jun 2004 11:26:52 -0400 | From | Jakub Jelinek <> | Subject | Re: 2.6.X, NPTL, SCHED_FIFO and JACK |
| |
On Wed, Jun 30, 2004 at 05:04:30PM +0200, Ingo Molnar wrote: > > Are there known issues with the implementation of NPTL that might give > > rise to this behaviour? What can we do to help understand and debug > > it? > > there's nothing special about NPTL, scheduling-wise. But if SCHED_FIFO > is not properly set for all JACK threads that could explain the > symptoms. You talked about kludges that are necessary to make all > threads SCHED_FIFO - are you 100% sure that all JACK threads are indeed > SCHED_FIFO after these kludges are applied? If yes and you are running a > later kernel then it's something new and probably NPTL-unrelated.
One thing to note is that NPTL defaults to PTHREAD_INHERIT_SCHED while LinuxThreads defaults to PTHREAD_EXPLICIT_SCHED. So, if you care about what scheduling created threads will have and want it to work with both NPTL and LinuxThreads, you want pthread_attr_setinheritsched (&attr, PTHREAD_*_SCHED); explicitely.
Jakub - 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/
| |