vNV-Heap: An Ownership-Based Virtually Non-volatile Heap for Embedded Systems
summary
vNV-Heap implements an ownership-based virtually non-volatile heap that uses ownership and borrowing (Rust-style) to track object modifications at compile time, gives static worst-case energy bounds so persistence operations are bounded, and supports transparent swapping without an MMU. Implementation and evaluation run on ESP32-C3 + FRAM, code is open-source, and measurements show object-wise tracking reduces swapping overhead up to 93% versus module-based swapping while providing static worst-case energy bounds and nonvolatile memory safety.
AI-written summary · about
chapters (11)
- 0:00vNV-Heap introduction
- 0:22Need for non-volatile memory
- 3:35State persistence in intermittent systems
- 4:39MMU and software limits
- 7:07Rust ownership for vNV-Heap
- 9:15vNV-Heap practical example
- 12:29ESP32C3 evaluation
- 15:21Conclusion and benefits
- 16:25Q&A: predictability & compiler
- 17:28Q&A: energy & runtime
- 21:04Q&A: ownership limits
related talks
15mA Managed Memory System for micro controllers with NOR flash memory
01h 00m"Designing (New) C++ Hardware”
25mBridging the Memory Hotness Gap in Edge Systems with Hotness-Segregated Object Allocation
43mNVM Software Interfaces New Direction
55mBreaking Dependencies: Type Erasure - The Implementation Details
46mZMS a New Lightweight Storage System
16mNetVRM: Virtual Register Memory for Programmable Networks
22mOld School cache coherence-a snooping system for a multicore processor based on CVA6