TENET: Memory Safe and Fault Tolerant Persistent Transactional Memory
summary
TENET is a PTM framework built on TimeStone that prevents software and media corruption by making NVM read‑only to applications via Memory Protection Keys (MPK), validating updates through DRAM copies with 8‑bit canary bits, and preventing use‑after‑free with pointer tags (upper 16 bits). It asynchronously replicates durable state to local SSD with a small operation log for consistent, lossless recovery. Evaluation shows ~4% overhead for memory safety only and ~12% with fault tolerance on TimeStone, while prior SafePM slows PMDK ~55%.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:28Boon and bane of Non-volatile Memory (NVM)
- 1:14Hardware (Media) errors are a threat too!
- 2:19Background on types of memory safety violations
- 3:15Background on types of Media Errors
- 3:57Summary of prior Persistent Transactional Memory (PTM) works
- 4:32TENET overview: Goals and Assumptions
- 5:13TENET overview: Programming Model
- 5:52Spatial safety design in TENET
- 6:12Direct NVM writes in the application code is dangerous
- 7:45Prevent direct NVM writes using Memory Protection Keys (MPK)
- 8:07Protecting DRAM objects using canary bits
- 8:55Read-only NVM access can cause temporal safety violations
- 9:29Enforcing temporal safety for NVM objects using pointer tags
- 10:57Replicating NVM data for fault tolerance against UME
- 12:44Evaluation of TENET
- 13:37Comparison of TENET with the other PTMs
- 14:55Performance of TENET and SafePM for a concurrent hash table
- 19:09Conclusion
related talks
46mTPM in TEE
14mScalable Memory Protection in the PENGLAI Enclave
41mPanel: A New Root Of Trust: Changing Computing With TEE
14mNimble: Rollback Protection for Confidential Cloud Services
21mOP-TEE: Shared memory between TAs
15mTimelock Drive: Isolated Time-Based Defense for Storage Systems
19mSupporting Trusted Virtual Machines with Hardware-based Secure Remote Memory
22mSupporting TEE on x86 Client Platforms with pKVM
