Plumbing challenges in Dynamic capacity device
summary
CXL 3.0 allows asynchronous release of extents but kernel code in review keeps the response lightweight and defers real reclamation, with an RFC v3 patch set coming to upstream. The kernel models DAX as a new sparse DAX region container that composes interleaved extents into HPAs, and currently rejects complex sub-extent semantics until a concrete use case appears. Hardware forced release can poison memory and crash the host so current handling is best-effort, tooling leans on userspace orchestrators and tags for allocation policies.
AI-written summary · about
chapters (6)
- 0:00Introduction and overview
- 2:52Asynchronous memory release
- 8:56Interleaving challenges
- 11:46Force release and errors
- 17:23SparkDax region concept
- 27:22Patch set updates and next steps
related talks
30mCXL Dynamic Capacity MM
29mCXL HDM-DB support for Linux
39mCompute Express Link(CXL), the Next Generation Interconnect - Overview and the Status of Linux
43mExpanding the Memory Limits with CXL Software Stack
28mCXL Type-3 device discovery, configuration in firmware and prepare ACPI tables...
22mKernel CXL Cache (safe) support
31mLinux plumbing of CXL error reporting
23mCXL hotplug: spec to reality