elBoberido

6 ms·

1. 1.▲
   by elBoberido 20d ago

   iceoryx2 maintainer here. Of course everybody has different requirements when it comes to IPC and if a rich set of supported languages is the highest priority, then protocols like JSONRPC are a good option. But using such protocols for loca
2. 2.▲
   by elBoberido 6mo ago

   I'm one of the iceoryx maintainer :) Yes, there is some overlap but iceoryx and threadprocs could complement each other. Currently, we achieve true zero copy only with data types that are shared memory compatible, i.e. no heap, no self
3. 3.▲
   by elBoberido 1y ago

   Btw, with the next release iceoryx2 will have Python bindings. They are already on main and we will make it available via PIP. This should make it easier to use with Pytorch.
4. 4.▲
   by elBoberido 2y ago

   I'm not sure I fully understand what you mean? Do you assume we implemented the same approach for shared memory communication like described in the blog post? If that’s the case, I want to reassure you that we don’t use locks. Quite th
5. 5.▲
   by elBoberido 2y ago

   Thanks, really appreciate it.
6. 6.▲
   by elBoberido 2y ago

   Request-response is on our todo list and will be introduced in an upcoming release :) What are you needing request-response for?
7. 7.▲
   by elBoberido 2y ago

   Indeed. That's our goal :)
8. 8.▲
   by elBoberido 2y ago

   Sweet. Can we link to your benchmark from the main iceoryx2 readme?
9. 9.▲
   by elBoberido 2y ago

   > In my experience shared memory is really hard to implement well and manage: I second that. It took us quite some time to get the correct architecture. After all, iceoryx2 is the third incarnation of this piece of software, with elfepif
10. 10.▲
    by elBoberido 2y ago

    Thanks for the tips. We have a comparison with message queues and unix domain sockets [1] on the repo on github [2]. ~~It's nice to see that independent benchmarks are in the same ballpark than the one we perform.~~ Edit: sorry, I conf
11. 11.▲
    by elBoberido 2y ago

    Besides being written in Rust, the big difference is the decentralized approach. With iceoryx1 a central daemon is required but with iceoryx2 this in not the case anymore. Furthermore, more fine grained control over the resources like memor
12. 12.▲
    by elBoberido 2y ago

    Don't worry. It's great to have other projects in this field, exploring different routes and you created a great piece of software. The best thing, it's all open source after all :) Reading your response is almost as you&#x27
13. 13.▲
    by elBoberido 2y ago

    We are waiting with some salt & vinegar crisps ;)
14. 14.▲
    by elBoberido 2y ago

    Hehe, we are also using fancy-pointer in some places :) We started with mapping to the shm to the same address but soon noticed that it was not a good idea. It works until some application already mapped something to the same address. It&#x
15. 15.▲
    by elBoberido 2y ago

    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 ;)
16. 16.▲
    by elBoberido 2y ago

    I'm one of the iceoryx mantainers. Great to see some new players in this field. Competition leads to innovation and maybe we can even collaborate in some areas :) I did not yet look at the code but you made me curious with the raw poin