> On May 6, 2016, at 6:21 PM, Gary E. Miller <g...@rellim.com> wrote: > > The end result is both processes have the shared memory mapped into their > data space. So things get updated at raw RAM speed. Knowing it changed > needs polls, semaphores, etc. > > shmctl() is dumber, shared memory persists until reboot or explicit kill. > > shm_open() has file system semantics, with all the good that implies. > It also gets automatically removed whenn all consumers exit or > explicitly delete. > > But both end up giving you direct access to some RAM, possibly R, W, or RW.
Thanks for the explanation. >>> Never underestiate the power of large numbers of stupid people. >> >> Look at all the Trump supporters! (sorry to mention politics on this >> list, but I couldn’t resist...) > > And look at all the Hillary supporters… Not me! Seriously! > How about we not go there? Ok with me. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
