Inter-process communication for real-time

For my Arm9 board, my application will have 2 or 3 processes or maybe threads and one of ( pipe, socket, fifo, msg queue or shared memory, or?) to pass data between them. The data is about 100bytes every 50ms. Assuming I just have vanilla Linux or uCLinux without any real-time enhancements, which of the above methods will have the least processor overhead, so as to be a bit closer to meeting real-time deadlines?

My guess is that pthreads with shared memory might be best, but maybe not.
.

Relevant Pages

  • Re: Inter-process communication for real-time
    ... so as to be a bit closer to meeting real-time deadlines? ... My guess is that pthreads with shared memory might be best, ... Changing between processes hurts the ARM CPU as it needs to throw away its ... cache content for *each* change (cache works on virtual address lines ...
    (comp.os.linux.embedded)
  • Re: Inter-process communication for real-time
    ... threads and one of (pipe, socket, fifo, msg queue or shared memory, ... My guess is that pthreads with shared memory might be best, ... cache content for *each* change (cache works on virtual address lines ... In the past I have used message queues, but I suspect they use more processor time than say, a shared memory or pipe. ...
    (comp.os.linux.embedded)