<p dir="ltr">absolutke not to json over shm.</p>
<p dir="ltr">once you have done that, with the needed mutexes and ring pointers, you have just literally reimplemented unix domain socket in user space, less safely</p>
<br><div class="gmail_quote"><div dir="ltr">On Fri, May 6, 2016, 2:10 PM Gary E. Miller <<a href="mailto:gem@rellim.com">gem@rellim.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yo Hal!<br>
<br>
On Fri, 06 May 2016 13:56:43 -0700<br>
Hal Murray <<a href="mailto:hmurray@megapathdsl.net" target="_blank">hmurray@megapathdsl.net</a>> wrote:<br>
<br>
> > Are we presently using the old one? Where is documentation for the<br>
> > new one?<br>
><br>
> Do the old and new SHM schemes share the same name space? If gpsd<br>
> uses old, can a ntpd using new talk to it?<br>
<br>
No, fundamentally incompatible at the ABI level. So it would have<br>
to be a totally new refclock. Unless we find another QNX type issue<br>
that needs fixing, a half step not worth making. Better to work on<br>
refclockd and fixing current refclocks.<br>
<br>
But, just to totally muddy the water...<br>
<br>
Some people worry about the latency issues in the JSON. I doubt they exist,<br>
but if they did, then the solution would be to run JSON through shm_open()<br>
style shared memory. We get file system style security and shared memory<br>
style speed!<br>
<br>
So just keep shm_open() in the back of your mind, someday it might be a<br>
solution to a hard problem.<br>
<br>
RGDS<br>
GARY<br>
---------------------------------------------------------------------------<br>
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703<br>
<a href="mailto:gem@rellim.com" target="_blank">gem@rellim.com</a> Tel:+1 541 382 8588<br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@ntpsec.org" target="_blank">devel@ntpsec.org</a><br>
<a href="http://lists.ntpsec.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ntpsec.org/mailman/listinfo/devel</a></blockquote></div>