4 ms·

Which executor do you use? Tokio is a bit heavy, no?

• steveklabnik 7y ago
  Not the parent, but I've been keeping my eye on https://github.com/Nemo157/embrio-rs https://github.com/Nemo157/embrio-rs
  • dbcurtis 7y ago
    Not much doc at the github. Can you provide a quick overview?
    • steveklabnik 7y ago
      Not much I can say other than “an executor designed specifically for embedded.” I don’t do embedded dev myself, so it’s more of a curiosity thing for me than something that I can give you a lengthy explanation of.
      • Matthias247 7y ago
        Embrio provides only a very limited executor. it can just drive only single Future. Which gets re-polled every time a certain system interrupt occurs. You can obviously have subtasks of that single task (e.g. via join! and friends), but you can't have other dynamic tasks. jrobsonchase has implemented a more dynamic solution which uses custom allocators for futures: https://gitlab.com/polymer-kb/firmware/embedded-executor https://gitlab.com/polymer-kb/firmware/embedded-executor I think there might also be other solutions out there. I remember the Drone OS project also doing something along that.
• rendaw 7y ago
  I'd like to hear more about this - I thought Tokio was just some tools on top of MIO which is just `select` (or similar). Is Tokio heavy?