David Leimbach wrote:
Why can't I mmap a remote process's memory? Some embedded systems [used to?] let me do this and pass messages with memcpy :).
http://mbgokhale.org/rminnich, look at the zounds stuff, user-mode library that let you do the moral equivalent. You could, as a server, attach a chunk of your memory to a socket endpoint, and you could, as a client, do same. Voila, your memory is my memory. Then I added multicast sockets. For the server side, you could optionally fork off a child that served the memory segment out.
OK, ok, I am sure it is ugly to even mention such a thing on this list, but I claim the excuse of utility. Once I added multicast, this library let me move a 16 MByte voxel cube to every node in a 128-node cluster in about the time it took to move it to 1. It greatly shortened the startup time for a || rendering app.
There's actually a few people out there still using this library, I hear from them from time to time. I have not worked on it in 10 years.
FreeBSD and Linux were supported. ron
