> There is a LOT more to this. > > 1. Dual or multi-core CPUs add some complexity because all the CPUs share a > common memory. What if all four CPUs try to run the "test and set" at the > same time? Also, you can no longer assume an interrupt handler has > exclusive use of memory. > 2. what if the process uses two queues? Process A might hold access to > Queue X and process B holds Y and then each waits for the other process to > release the other queue and the system deadlocks. > 3. what if there are more than two processes? How to ensure that access to > the queue is fairly sharded between four or six users? > 4. What if the CPU you are using lacks a test and set instruction? > > There are good solutions but today NO ONE has to solve these problems > solutions were worked out 50 years ago.
I use: message queues, signaling mechanism, shared memory functions, semaphores. Then available and needed which is not always the case, if I spend some time I could add operating system on Micro controller if needed. Today I get the feeling development is going away from quality to plenty of new progamming languages not adding to much new. Usually with dynamic typing and allocation on the heap with garbage collection as the only solution while I regard these as the last solution then others do not work. Static types and local variables is my first choice as long as they work which of course is not always the case. _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
