9) Or is my approach of multiple processes otherwise flawed?
In Linux the communication between processes is really fast, cheap, easy and versatile.

You can e.g. use pipes/queues (e.g. named pipes in the file system or system 5 message queues).

In many cases you don't need threads to wait for data from such a queue as you can use appropriate system library calls like "select()" or (the new, more advanced way) (e)poll() (which despite of it's name does not do any actively spinning polling) to schedule your reactions on several events thrown by other processes. In Linux "everything is a file", so handling such queues (and IP-sockets, hardware ports etc) is done using the same paradigm as with handling normal files.

-Michael
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Reply via email to