Jon
I'm not sure where they are at with replacing NML, but that is not what I was talking of. They have split the cnc stack from the HAL stack HAL is what I am talking of, which would include the realtime code I suppose. (Talking above my pay grade but to summarize) Because of their needs for ARM support they wanted to utilize multiple cores for realtime. Our HAL system works very well with single core or isolating realtime to a single core. Apparently it breaks in subtle, hard to find ways on multicore. They rewrote it with multicore in mind. It also still supports legacy (linuxcnc) components. I do believe it means 32bit is not supported anymore though.. Chris M ________________________________ From: Jon Elson <el...@pico-systems.com> Sent: September 8, 2018 11:44 PM To: EMC developers Subject: Re: [Emc-developers] Breakout of HAL/ machinekits's HAL On 09/08/2018 02:05 PM, Chris Morley wrote: >> > > There are very smart and hard working people on both > projects, it would be nice to benefit both > > projects. > > > I _THINK_ that the biggest thing they have done is to replace NML with 0mq. While I don't know the details at all, NML ships the entire real-time context with every message, incurring a LOT of overhead. With 0mq, all requesters tell it what structure they need, and then ONLY the requested structure is sent. This has some impact within one node, but has HUGE impact when the system has some HAL components on different nodes, over the network. This replacement of NML was VERY complicated, as almost everything in LinuxCNC is interfaced through it. Jon _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
