embassy/embassy-executor
Ulf Lilleengen 045ae2c29f Ensure interrupt::take works without embassy-executor
Add "rtos-trace-interrupt" feature flag on embassy-macros and enable it
for embassy-executor, to ensure that the interrupt::take! macro can be
used without depending on embassy-executor.
2022-08-25 12:46:24 +02:00
..
src Remove warnings 2022-08-22 16:33:39 +02:00
build.rs Split embassy crate into embassy-executor, embassy-util. 2022-07-29 23:40:36 +02:00
Cargo.toml Ensure interrupt::take works without embassy-executor 2022-08-25 12:46:24 +02:00
README.md Split embassy-time from embassy-executor. 2022-08-18 01:22:30 +02:00

embassy-executor

An async/await executor designed for embedded usage.

  • No alloc, no heap needed. Task futures are statically allocated.
  • No "fixed capacity" data structures, executor works with 1 or 1000 tasks without needing config/tuning.
  • Integrated timer queue: sleeping is easy, just do Timer::after(Duration::from_secs(1)).await;.
  • No busy-loop polling: CPU sleeps when there's no work to do, using interrupts or WFE/SEV.
  • Efficient polling: a wake will only poll the woken task, not all of them.
  • Fair: a task can't monopolize CPU time even if it's constantly being woken. All other tasks get a chance to run before a given task gets polled for the second time.
  • Creating multiple executor instances is supported, to run tasks with multiple priority levels. This allows higher-priority tasks to preempt lower-priority tasks.