Async Executors
Ariel OS embraces async Rust and favors async interfaces over blocking ones.
System Executor Flavors
Ariel OS provides a system executor which is automatically started at startup. It comes in three different flavors, identified by their laze module names:
| laze module | Embassy executor | Description |
|---|---|---|
executor-interrupt | InterruptExecutor | Runs in handler mode. A software interrupt (SWI) handler is used when the MCU provides one, otherwise the board configuration must specify which peripheral interrupt to dedicate to this executor. |
executor-single-thread | Executor | Runs in thread mode in place of threads. Therefore not compatible with multithreading. |
executor-thread | Custom, based on raw::Executor | Runs inside a dedicated thread automatically started at startup. |
A default flavor compatible with the MCU is automatically selected by default in the order of preference in which they are listed above. Another flavor can be manually selected, replacing the default one, by selecting its laze module. Not all flavors are available on all MCUs however, and the laze configuration will only allow selecting one the compatible ones.
The
executor-interruptmight offer a slight performance advantage.
Using Multiple Executors
Using multiple executors is possible but currently undocumented.
Running multiple executors allows running them with different priorities.