|
I am far from an expert on the emc stuff, but basically the shared
memory is a method of passing data from userspace to realtime. The memory is allocated to the size of a specific structure, (say emcmot_struct_t) then pointers are allocated to elements within the structure. These pointers are then used to pass and access the values. As for the specific connection, motion.c creates the structure for realtime functions. usmotintf.cc, does not create a different structure, it you look it gets the emcmot SHMEM_KEY (line 64) of the realtime structure and uses that to create its local version (line 690) This is cutting edge MIT 1980s coding, only the sheer complexity of replacing it has prevented simpler and more efficient code. That and the fact that it works, so don't fix it :) Search the pointers created, for instance emcmotCommand, and you will find it accessed by taskintf.cc and command.c On 09/01/18 03:46,
[email protected] wrote:
-- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. |
- [Machinekit] share memory created usrmotintf.cc ... steve . better01
- Re: [Machinekit] share memory created usrmo... [email protected]
- Re: [Machinekit] share memory created u... steve . better01
