The single-scheduler hot path acquired the shared mutex three times per yield: once to drain timers, once to drain IO completions, and once to pop the next runnable actor. It also called Instant::now() every loop iteration to feed timers.pop_due(), even though the pure-yield / pure-compute workloads never arm a timer. Confirmed with llmdbg before touching anything: breakpointing switch_to_scheduler and instruction-counting one scheduler-side yield cycle on the ctx_switch_probe showed ~6950 instructions / 68 calls of bookkeeping between consecutive actor resumes, dominated by lock acquisition and the per-iteration clock read — not by the naked-asm switch itself (~16 insns). The te!() trace macro compiles to () without the smarm-trace feature, so it was ruled out as a contributor. This collapses the two drain `with_shared` calls into one lock hold and reads the clock only when the timer heap is non-empty. IO completions are still drained unconditionally while the IO subsystem is live, because the IO/pool threads push completions onto their own mutex (not `shared`), so the scheduler cannot know in advance whether any arrived — it must look; that look is a single empty-VecDeque check on the hot path. No change to timer or IO semantics; the asm switch is untouched. Measured on this box (single core, nproc==1), medians over the bench harness, re-baselined locally first: yield_many smarm 1-thread 38459 -> 29943 us (-22.1%) yield_in_hot_loop smarm 1-thread 166220 -> 122629 us (-26.2%) ping_pong_oneshot smarm 1-thread 1619 -> 1367 us (-15.6%) chained_spawn smarm 1-thread 481 -> 399 us (-17.0%) Run-to-run spread on yield_many is ~3-4% (29565-30634), so the 22% move is well outside the noise. Gap to tokio current_thread closes from ~2.4x to ~1.95x. All tests green: cargo test --test context (4) plus the full suite (93 total).
smarm
SMARM — Smarm, Marks Actor Runtime Machinery. A proof-of-concept green-thread actor runtime for Rust.
Implements the core ideas in Achitecture.md: green-thread actors on a
shared heap, scheduled cooperatively, communicating only by Send messages.
Erlang's isolation model without Erlang's copying GC, Rust's zero-copy
ownership transfers without async's function colouring.
The scheduler is multi-threaded — one OS thread per available CPU, all drawing
from a shared run queue. The single-threaded run() entry point is kept as a
convenience wrapper around runtime::init(Config::exact(1)).run(f).
What's here
| Module | What it does |
|---|---|
stack |
mmap'd growable stack with guard page; SIGSEGV on overflow |
context |
#[naked] x86-64 context-switch shims, callee-saved regs only |
preempt |
Allocator-driven preemption; check!() macro for no-alloc loops |
pid |
(index, generation) PIDs; stale handles are detectable, not silent |
actor |
Trampoline + catch_unwind boundary at the actor entry point |
scheduler |
Run queue, slot table, spawn/join, parking, idle path |
channel |
Unbounded MPSC channel; recv parks the actor |
mutex |
Mutex<T> with mandatory timeout; FIFO waiters; parks the green thread |
timer |
Min-heap of (deadline, reason); Sleep and WaitTimeout reasons |
io |
block_on_io for blocking work; wait_readable/wait_writable + read/write via epoll |
supervisor |
Signal::Exit / Signal::Panic delivered to a parent actor's mailbox |
Quick taste
use smarm::{run, spawn, channel};
run(|| {
let (tx, rx) = channel::<i64>();
let h = spawn(move || {
for _ in 0..3 {
let v = rx.recv().unwrap();
println!("got {v}");
}
});
for v in 1..=3i64 {
tx.send(v).unwrap();
}
h.join().unwrap();
});
Layout
src/
stack.rs context.rs preempt.rs pid.rs actor.rs
scheduler.rs channel.rs mutex.rs timer.rs io.rs supervisor.rs
lib.rs
tests/
per-module integration tests
benches/
primes.rs fan-out/fan-in compute, vs tokio current_thread
Building and running
Standard Cargo. Requires Rust 1.95 or newer (the #[naked] attribute went stable
in 1.88; we use a few unrelated post-1.88 features). x86-64 Linux only —
ARM64 and macOS are on the deferred list because of the assembly shim and the
epoll dependency.
cargo test # all tests
cargo test --test mutex # one module
cargo bench # primes benchmark vs tokio
What's not here
See the Defer section of Architecture.md.
restart-intensity caps, join! for handle groups, stack growth via remap,
hierarchical timer wheel, fd-wait timeouts, Signal::Timeout. Each is
mechanism we know how to add; none belongs in this iteration.
Docs
| Document | What it covers |
|---|---|
Architecture.md |
Design intent, runtime model, and deferred work |
smarm - Deep Dive.html |
Generated walkthrough of the system; good starting point |
BENCHMARKS_AND_TUNING.md |
Where smarm wins and loses vs tokio, preemption knob recommendations |
benchmarks.md |
Raw benchmark results, methodology, and tuning experiment log |
Contributing
This is a personal proof-of-concept. There's no PR workflow. If you fork it and do something interesting, just send me an email. If it's nice, I'll upstream the changes.