4 ms·
Fast interprocess messaging (2010)
- justincormack 13y agoWell kdbus is arriving, but the copy to other process memory does not seem to have.
- deleted 13y ago[deleted]
- yepguy 13y agoMaybe I'm misunderstanding your comment, but I think kdbus does allow you to transfer ownership of some piece of memory to another process.
- justincormack 13y agoDoes it? I haven't seen that. It has single copy transfer, but I didnt see a memory ownership transfer/sharing.
- rcxdude 13y agoThere is a zero-copy mode, but it only makes sense for pretty large messages (>512k IIRC).
- kapilvt 13y agoThis article is painfully old... cross memory attach landed in 3.2 http://kernelnewbies.org/Linux_3.2#head-a5e26c6275e85a5c9c41873fbab96bd38d934b72 http://kernelnewbies.org/Linux_3.2#head-a5e26c6275e85a5c9c41... kdbus is coming, but its an entirely different implementation by gkh and systemd folks, its not using AF_DBUS sockets, its bypassing the net stack and using a char device. a more relevant article on the current kdbus is https://lwn.net/Articles/580194/ https://lwn.net/Articles/580194/
- rubiquity 13y agoThis article is from 2010 so it is well before kernel 3.2. This same author has since wrote about kdbus here: http://lwn.net/Articles/580194/ http://lwn.net/Articles/580194/
- joosters 13y agoThe eventual code commit has a useful description of the feature: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fcf634098c00dd9cd247447368495f0b79be12d1 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...
- checker659 13y agoAren't there any security implications of directly accessing another process's memory?
- hcarvalhoalves 13y ago> Either both processes must have the same ownership or the copying process must have the CAP_SYS_PTRACE capability; otherwise the copy will not be allowed.
- yetanotherphd 13y agoCan someone fill me in on why IPC is important? I would have thought that most parallelism was either within a process, or across machines.
- deleted 13y ago[deleted]
- angersock 13y agoSure. My Rails app is talking to Postgres--why should I have to go through the TCP stack for local communication? Why should my window manager have to use that to send clipboard events?