linux ipc mechanisms

gopikrishna mogasati · 06-01-2014, 12:38 AM

why message queues are slowest of all ipc mechanisms especially when compared to pipes in linux.

message queues are slower when compared to shared memory as we need to go from user to kernel space to access the message queue.

How about message queue performance when compared to pipes?? why message queue is slower when compared to pipes mechanism? please explain the reasons with a good intitution.

dijetlo · 06-01-2014, 04:09 AM

Messages can be queued and processed based on priority,it's not that they are "slow", it's that they are prioritized. Pipes work off the assumption that all needed resources are available in the instant in which the pipe is utilized. If you create a buffer to hold the over-run of pipes being requested while you wait for resources to become available you have effectively built a message que.
Hope that helps.

rtmistler · 06-02-2014, 07:23 AM

Quote:

Originally Posted by gopikrishna mogasati

why message queues are slowest of all ipc mechanisms especially when compared to pipes in linux.

message queues are slower when compared to shared memory as we need to go from user to kernel space to access the message queue.

How about message queue performance when compared to pipes?? why message queue is slower when compared to pipes mechanism? please explain the reasons with a good intitution.

What's your basis for this question? Have you run some tests to validate one versus the other? Or is this a homework question?