面向CPU故障的CXL容错性
DIKTAMO: Extending CXL for Resilience to CPU Failures
AI总结:
ReCXL通过引入副本和日志单元,实现对CPU故障的容错性,使应用程序在节点故障后能正确恢复,仅增加30%的延迟。
摘要:
计算表达链接(CXL)3.0及更高版本允许集群的计算节点以缓存行的粒度共享数据,实现硬件缓存一致性。这为分布式计算提供了共享内存语义,但引入了新的容错挑战:节点故障会导致其缓存中的脏数据丢失,破坏应用程序状态。不幸的是,CXL规范未考虑处理器故障。当组件故障时,规范试图隔离故障并继续应用程序执行;没有尝试将应用程序带回一致状态。为解决这些限制,本文扩展了CXL规范,使其具有对节点故障的容错性,并在节点故障后正确恢复应用程序。我们称之为ReCXL系统。为处理节点故障,ReCXL在写入的缓存一致性事务中增加消息,将更新传播到少量其他节点(即副本)。副本将更新保存在硬件日志单元中。这种复制确保了对节点故障的容错性。然后,定期间隔内,日志单元将更新转储到内存中。恢复涉及使用日志单元中的日志将目录和内存带回正确状态。我们的评估显示,ReCXL仅在相同平台无容错支持的情况下,导致30%的延迟,即可实现容错执行。
英文摘要:
Compute Express Link (CXL) 3.0 and beyond allows the compute nodes of a cluster to share data with hardware cache coherence and at the granularity of a cache line. This enables shared-memory semantics for distributed computing, but introduces a new resilience challenge: a node failure leads to the loss of the dirty data in its caches, corrupting application state. Sadly, the CXL specification does not consider processor failures. Moreover, when a component fails, the specification tries to isolate it and continue application execution; there is no attempt to bring the application to a consistent state -- a step required to recover a shared-memory program. To address these limitations, this paper extends CXL to be resilient to node failures, and to correctly recover the application after node failures. We call the system DIKTAMO. To survive node failures, DIKTAMO augments the coherence transaction of a write with messages that propagate the update to a small set of other nodes (i.e., Replicas). Replicas save the update in a local hardware Logging Unit. Replication ensures resilience to node failures. Then, at regular intervals, the Logging Units dump the compressed updates to memory. After a node failure, recovery involves using the logs to bring the directory and memory to a correct state. Our evaluation with 16 4-core nodes shows that DIKTAMO enables fault-tolerant execution with 30% slowdown with 3 replicas (or 27% with 2 replicas) over a platform without fault-tolerance support. DIKTAMO is 2.82x faster than ensuring fault tolerance by using a write-through protocol.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。