3. break (sry, my translation is not so good)
"the developer have no greater demur against Realtime-Tree (RT). the code for threaded interrupts will probably settle in to the next versionen to the main developmentally. the code will be customized before."
What I do understand is that some kernel masters discussed things about real time kernels and especially about "Threaded Interrupts". A way to handle hardware interruptions which is used by rt kernels. It seems that they agree about the fact that this way of handling "Threaded Interrupts" could be used in the design of new versions of kernels which is good news for realtime usage on linux....
Changes in the handling of the kernel thread were also debated. That gave rise to a discussion about thread interrupts – these are used in the realtime tree (RT) to allow hardware interrupts to be run in their own threads in order to avoid disrupting other work in the system. Until now, a number of developers have viewed this concept, which has a profound influence on how interrupts are handled, with a critical eye, but following a few debates about details there are no longer any significant objections to the idea. This paves the way for the code for threaded interrupts to be incorporated into the main development branch, but first the code has to be adapted so that threaded interrupts are not used by default, but only for hardware devices where it makes sense and is unlikely to cause any problems.
The kernel hackers responsible for the real-time tree have recently started a Git tree designed, to prepare the improvements developed in the RT tree for integration into the main development branch of Linux.
Interesting info. It would be nice if us music geeks could use a standard kernel. That would be one less thing to deal with when upgrading, modifying, etc.
