Hey Folks, I wanted to point you all to question from Luke posted as a github issue on Sig-Embedded on what the hardware minimum requirement should be for memory management and control on embedded devices.
Luke's also got some cool ideas about how a MPU could mimic a limited MMU - anyway, please do head over read and chip in with your view : https://github.com/bytecodealliance/sig-embedded/issues/7
Hi, I finally completed my prototype for memory attached publisher subscriber with wasmtime (it requires a host extension and WASI 0.3 streams) and would love feed-back.
This extends my initial mmap prototype, the example where it attaches a large buffer to multiple components to change numbers in an array still works, but the publisher subscriber functionality I am most excited about.
Most likely this part is of interest to this SIG:
The buffer API could be implemented with copying without the guests noticing, also several efficient zero-copy mappings to MPU only embedded are possible. The host can optimize the implementation to avoid attachment during run-time without affecting the ownership logic, this of course assumes a well-behaved publisher; subscribers remain untrusted. Adding a subscriber only requires creating another stream<memory-block> on the sender side (and writing four bytes to it per published data). So the overhead per subscriber is minimal.
The direct link for convenience is https://github.com/cpetig/wasm-shm-test/tree/main?tab=readme-ov-file#publisher-subscriber
Last updated: Dec 06 2025 at 06:05 UTC