80972f1e0e
This is a `core` patch to make wakers 1 word (the task pointer) instead of 2 (task pointer + vtable). It allows having the "waker optimization" we had a while back on `WakerRegistration/AtomicWaker`, but EVERYWHERE, without patching all crates. Advantages: - Less memory usage. - Faster. - `AtomicWaker` can actually use atomics to load/store the waker, No critical section needed. - No `dyn` call, which means `cargo-call-stack` can now see through wakes. Disadvantages: - You have to patch `core`... - Breaks all executors and other things that create wakers, unless they opt in to using the new `from_ptr` API. How to use: - Run this shell script to patch `core`. https://gist.github.com/Dirbaio/c67da7cf318515181539122c9d32b395 - Enable `build-std` - Enable `build-std-features = core/turbowakers` - Enable feature `turbowakers` in `embassy-executor`, `embassy-sync`. - Make sure you have no other crate creating wakers other than `embassy-executor`. These will panic at runtime. Note that the patched `core` is equivalent to the unpached one when the `turbowakers` feature is not enabled, so it should be fine to leave it there.
31 lines
796 B
Rust
31 lines
796 B
Rust
use core::ptr;
|
|
use core::ptr::NonNull;
|
|
use core::sync::atomic::{AtomicPtr, Ordering};
|
|
use core::task::Waker;
|
|
|
|
/// Utility struct to register and wake a waker.
|
|
pub struct AtomicWaker {
|
|
waker: AtomicPtr<()>,
|
|
}
|
|
|
|
impl AtomicWaker {
|
|
/// Create a new `AtomicWaker`.
|
|
pub const fn new() -> Self {
|
|
Self {
|
|
waker: AtomicPtr::new(ptr::null_mut()),
|
|
}
|
|
}
|
|
|
|
/// Register a waker. Overwrites the previous waker, if any.
|
|
pub fn register(&self, w: &Waker) {
|
|
self.waker.store(w.as_turbo_ptr().as_ptr() as _, Ordering::Release);
|
|
}
|
|
|
|
/// Wake the registered waker, if any.
|
|
pub fn wake(&self) {
|
|
if let Some(ptr) = NonNull::new(self.waker.load(Ordering::Acquire)) {
|
|
unsafe { Waker::from_turbo_ptr(ptr) }.wake();
|
|
}
|
|
}
|
|
}
|