new IPC mechanism ideas
We are planning to develop a new IPC mechanism based on shared memory. The memory is allocated by a device driver in the kernel and mapped to various processes read only. Processes talk to the driver to write to the memory but they can directly read the memory (so its a 1-copy IPC mechanism).
We also want to make this IPC mechanism persistent across application restarts. So that if an application crashes, when it comes back up, it can remap to its old queues and get its messages.
Does anyone have experiences building such a mechanism ? Any pointers to reading material would be really appreciated ?
Please cc replies to [email protected]
Thanks !
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
Followup to: <[email protected]> By author: Rajeev Bector <[email protected]> In newsgroup: linux.dev.kernel
Quoted 7 lines
We are planning to develop a new IPC mechanism based on shared memory. The memory is allocated by a device driver in the kernel and mapped to various processes read only. Processes talk to the driver to write to the memory but they can directly read the memory (so its a 1-copy IPC mechanism).
Quoted 7 lines
We also want to make this IPC mechanism persistent across application restarts. So that if an application crashes, when it comes back up, it can remap to its old queues and get its messages.
Does anyone have experiences building such a mechanism ? Any pointers to reading material would be really appreciated ?
Why not just use mmap() on a file? That way you can even make it zero-copy. Otherwise, mmap() readonly in all but one process ("the driver").
Nothing needed in the kernel that isn't already there...
-hpa
Signature · 3 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt