Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: new IPC mechanism ideas | Date | 10 Jul 2001 20:25:40 -0700 |
| |
Followup to: <20010711014918.76554.qmail@web14404.mail.yahoo.com> By author: Rajeev Bector <rajeev_bector@yahoo.com> In newsgroup: linux.dev.kernel > > 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 ? >
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 -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |