News for hackers. Stuff that matters.
Re:Flow-IPC: Open-Source Toolkit for Low-Latency Inter-Proce... by jeffreygoesto on Monday April 15, 2024 @02:50AM (#40037669)
Thank you very much for this excellent explanation! I am one of the fathers of IceOryx and it's predecessor. We had to lift component based embedded development to Posix systems and are very latency and memory bandwidth sensitive (driver assistance and automated driving on what most people would call small SoCs). There it is easier to enforce the senders and receivers to use the same struct.

What you did with the shm arena and sharing std containers is outright amazing and indeed relaxes the "self contained" constraint nicely.

On QNX (up to 7) we were bitten by each syscall going through procnto, that is why we have chosen lockfree over mq btw.

Being aware of the use case and choosing the right tradeoff is crucial, as you wrote.

Re:Flow-IPC: Open-Source Toolkit for Low-Latency Inter-Proce... by elBoberido on Monday April 15, 2024 @08:26AM (#40039677)
Now I'm curious. It's seems you are not the father I'm still drinking beer with. This means there is only one person left that fits this attribute :) ... we should meet for some beer with the other father ;)
Re:Flow-IPC: Open-Source Toolkit for Low-Latency Inter-Proce... by jeffreygoesto on Tuesday April 16, 2024 @09:23AM (#40051564)
Got me. Next time I'm in Berlin we'll do... ;) Good job with IceOryx2, guys!
Re:Flow-IPC: Open-Source Toolkit for Low-Latency Inter-Proce... by elBoberido on Tuesday April 16, 2024 @06:36PM (#40058141)
We are waiting with some salt & vinegar crisps ;)
Re:Flow-IPC: Open-Source Toolkit for Low-Latency Inter-Proce... by jeffreygoesto on Sunday April 21, 2024 @10:35AM (#40106064)
Nice, but please no T-Shirts on train platforms... =;-D