3 ms·
If you are counting on lock-free operations to guarantee you will meet your real-time scheduling requirements, you have chosen to fail, right out of the gate. G
by ncmncm 5y ago
If you are counting on lock-free operations to guarantee you will meet your real-time scheduling requirements, you have chosen to fail, right out of the gate. Guaranteeing met deadlines takes engineering. Using lock-free operations is not a substitute for engineering. There is no such substitute.
Also: All this has nothing to do with parallelism. Parallelism is about things happening at the same time. Locking or not locking, and contention, are about concurrency, which is about synchronization and serialization, a different topic.
- Kranar 5y agoIf you are using a mutex to guarantee real-time scheduling requirements, you have failed. Furthermore if you think a discussion about benchmarking an algorithm on a 24-core SMP system involving atomic reads, writes and shared caches has nothing to do with parallelism then let's just agree to disagree with one another and I wish you all the best in your programming endeavors. People can decide for themselves what credibility they wish to lend to your argument given your perspective on this matter.
- ncmncm 5y ago. . . I don't even need to say anything here.
- SAI_Peregrinus 5y agoRTOS programming tends to make extensive use of semaphores, often to build queues.