Hello Morten, On 10/5/07, Morten Mossige <morten.mossige@xxxxxxxxx> wrote: > Hi > I'm porting an application from another realtime-os to Linux. This > application makes use of intLock() from time to time. I still need the the > application to be compilable on both Linux and my old os, so I need a > portabel intLock() > I have tried the following approach: > When a thread needs to do intLock, I boost the thread-pri to max, and when > the thread does intUnLock() I set the thread-pri back. This woorks quite ok, I think your approach is good if it is working. > but by using this approach, I will also lock other threads in other > applications running on Linux. Someone has to pay. If you are boosting someone on the same time you are also suppressing others, this is how real-time works. > What I really need is a way of blocking all other threads in my application, > without affecting other applications. If you block other applications they will be affected. No solution for this. Jaswinder Singh. > I know I can use mutex'es and semaphores, but that will require a major > rewriting of the application, and that is somthing I dont want to do. > Can someone come up with an idea how this is done best? > Morten > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > - To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
