Scalable Persistent Memory File System with Kernel-Userspace Collaboration
summary
Kuco is a client–server PM filesystem architecture that maps persistent memory into user space while keeping a tiny kernel KFS to enforce permissions via page-table bits and handle metadata validation. It offloads pathname resolution and concurrency control to a user library using collaborative indexing, two-level locking, and versioned reads. The implemented KucoFS moves costly indexing and locking out of the kernel, achieves up to 13.8× higher metadata throughput (roughly an order of magnitude) and saturates device bandwidth for data operations.
AI-written summary · about
chapters (9)
- 0:00Introduction to the work
- 0:36Persistent memory overview
- 1:47File system challenges
- 2:53Limitations of current designs
- 4:29The Google architecture
- 5:37Scalability problems analyzed
- 7:23Collaborative indexing design
- 8:37Correctness and safety
- 12:08Evaluation and conclusion
related talks
17mCoFS: A Filesystem for Fast Container Startup
43mpkernfs: Persisting guest memory and kernel/device state safely...
19mP2CACHE: Exploring Tiered Memory for In-Kernel File Systems Caching
22mPreserving guest memory across kexec
25mShared CXL 3 memory what will be required
43mKernel Samepage Merging (KSM) at Meta and Future Improvements to KSM
48mKFLAT - Selective Kernel Memory Serialization for Security and...
48mPersistent Memory Usage within Linux Environment