首页> 外文期刊>Computer architecture news >Wait-N-GoTM: Improving Htm Performance By Serializing Cyclic Dependencies
【24h】

Wait-N-GoTM: Improving Htm Performance By Serializing Cyclic Dependencies

机译:Wait-N-GoTM:通过序列化循环依赖性来提高Htm性能

获取原文
获取原文并翻译 | 示例
           

摘要

Transactional memory (TM) has been proposed to alleviate some key programmability problems in chip multiprocessors. Most TMs optimistically allow concurrent transactions, detecting read-write or write-write conflicts. Upon conflicts, existing hardware TMs (HTMs) use one of three conflict-resolution policies: (1) always-abort, (2) always-wait for some conflicting transactions to complete, or (3) always-go past conflicts and resolve acyclic conflicts at commit or abort upon cyclic dependencies. While each policy has advantages, the policies degrade performance under contention by limiting concurrency (always-abort, always-wait) or incurring late aborts due to cyclic dependencies (always-go). Thus, while always-go avoids acyclic aborts, no policy avoids cyclic aborts. We propose Wait-n-GoTM (WnGTM) to increase concurrency while avoiding cyclic aborts. We observe that most cyclic dependencies are caused by threads interleaving multiple accesses to a few heavily-read-write-shared delinquent data cache blocks. These accesses occur in code sections called cycle inducer sections (CISTs). Accordingly, we propose Wait-n-Go (WnG) conflict-resolution to avoid many cyclic aborts by predicting and serializing the CISTs. To support the WnG policy, we extend previous HTMs to (1) allow multiple readers and writers, (2) scalably identify dependencies, and (3) detect cyclic dependencies via new mechanisms, namely, conflict transactional state, order-capture, and hardware timestamps, respectively. In 16-core simulations of STAMP, WnGTM achieves average speedups of 46% for higher-contention benchmarks and 28% for all benchmarks over always-abort (TokenTM) with low-contention benchmarks remaining unchanged, compared to always-go (DATM) and always-wait (LogTM-SE), which perform worse than and 6% better than TokenTM, respectively.
机译:已提出事务性存储器(TM)以减轻芯片多处理器中的一些关键可编程性问题。大多数TM乐观地允许并发事务,以检测读写冲突。发生冲突时,现有的硬件TM(HTM)使用以下三种冲突解决策略之一:(1)始终中止;(2)始终等待某些冲突的事务完成;或者(3)永远过去的冲突并解决非周期性问题在提交时发生冲突,或者在循环依赖项时中止冲突。尽管每种策略都有其优势,但这些策略会通过限制并发性(始终中止,始终等待)或由于循环依赖性而导致延迟中止(始终执行)来降低争用下的性能。因此,尽管始终执行可避免非循环中止,但没有策略可避免循环中止。我们建议使用Wait-n-GoTM(WnGTM)来提高并发性,同时避免循环中止。我们观察到,大多数循环依赖关系是由线程交错访问对几个严重读写共享的拖延数据缓存块的多次访问引起的。这些访问发生在称为循环诱导器节(CIST)的代码节中。因此,我们提出了Wait-n-Go(WnG)冲突解决方案,通过预测和序列化CIST来避免许多循环中止。为了支持WnG策略,我们将以前的HTM扩展为(1)允许多个读取器和写入器,(2)可缩放地标识依赖性,以及(3)通过新机制(即冲突事务状态,订单捕获和硬件)检测循环依赖性。时间戳。在16核模拟的STAMP中,与始终运行(DATM)相比,WnGTM在始终中断(TokenTM)上的争用较高的基准平均速度提高了46%,所有基准的平均速度提高了28%,而低争用基准保持不变始终等待(LogTM-SE),其性能分别比TokenTM差和6%。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号