Server - CMS - DC - Memory Fabric Orchestration - 87523137632 & 83213620697 - Workstream - (2025-11-
Why It Matters
Dynamic CXL memory orchestration promises scalable, disaggregated resources for cloud providers, reducing costs and boosting performance, while open‑source tooling accelerates industry adoption.
Key Takeaways
- •OCP white paper stuck in review; public access issues persist.
- •Team pursuing dynamic CXL memory binding via XCON switch prototypes.
- •Redfish profiles being mapped to generic vs CXL‑specific functions.
- •Open‑source libCXLMI positioned as foundation for fabric manager API.
- •Collaboration needed among hardware vendors, BIOS teams, and hyperscalers.
Summary
The meeting centered on progress and roadblocks in the Server‑CMS‑DC memory‑fabric orchestration workstream, including the pending OCP white paper and its limited public accessibility. Participants highlighted two parallel technical tracks: a system‑level solution for dynamic CXL memory provisioning and a detailed mapping of Redfish DMTF profiles to distinguish generic versus CXL‑specific capabilities.
Key technical updates included ongoing debugging of XCON switch modes—pool and hierarchical switch configurations—to enable dynamic binding of CXL memory to hosts. Efforts are underway to expose DAX devices to containers, integrate them with NEMAs, and align these flows with QMU and BIOS firmware changes. Simultaneously, the group is cataloguing Redfish profiles to ensure comprehensive API coverage.
Notable contributions referenced the open‑source libCXLMI library as a building block for an open fabric manager, with plans to translate Redfish commands into CXL‑aware actions. Participants discussed firmware requirements on both the XCON switch and Intel platforms, BIOS modifications, and the need for coordinated hardware‑software partnerships involving vendors such as Samsung, CMach, and hyperscalers.
The discussion underscored that a unified, open‑source fabric manager could accelerate CXL memory disaggregation across data‑center deployments, but success hinges on cross‑vendor collaboration, standardized APIs, and broader accessibility of documentation and tooling.
Comments
Want to join the conversation?
Loading comments...