网站大量收购独家精品文档,联系QQ:2885784924

SlackenedMemoryDependenceEnforcementCombining放松记忆依赖执法相结合.ppt

SlackenedMemoryDependenceEnforcementCombining放松记忆依赖执法相结合.ppt

  1. 1、本文档共27页,可阅读全部内容。
  2. 2、有哪些信誉好的足球投注网站(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
SlackenedMemoryDependenceEnforcementCombining放松记忆依赖执法相结合

6/20/2006 Slackened Memory Dependence Enforcement, Alok Garg, ISCA 2006 Slackened Memory Dependence Enforcement: Combining Opportunistic Forwarding with Decoupled Verification Alok Garg, M. W. Rashid, and Michael Huang Department of Electrical Computer Engineering University of Rochester Motivation Out-of-order execution needs efficient memory dependence enforcement logic Conventional approach – complex, hard to scale Tightly coupled forwarding and enforcement We use two decoupled components to simplify the task Opportunistic forwarding using L0 cache Verification against in-order re-execution Slackened memory dependence enforcement (SMDE) LSQ: complex hard to scale Needs priority CAMs Forwarding from LSQ on timing critical path Serialized with address translation Design further complicated by Coherence and consistency considerations Corner cases: e.g., partial overlap of operands Highlights of prior work Two-level load store queue [sethumadhavan03], [akkary03], [baugh04], [roth04], [torres05], [gandhi05] Reducing search frequency using clever filtering and prediction mechanism [park03], [sethumadhavan03] Memory dependence prediction [moshovos.isca97], [moshovos.micro97], [sha05], [stone05] Value based re-execution [cain04], [roth04], [sha05] (more detailed contrast in paper) Outline Overview of SMDE Optional performance optimizations Evaluation Conclusion Overview of SMDE Decoupled execution LSQ: competing requirements Front-end execution: little mem dependence enforcement Back-end execution: detect violations (mem access only) Memory B/W: naturally handled Why it works – two perspectives Back-end execution is the only one required Totally in-order, preserving dependence Any front-end execution is OK L0 effectively a slow but accurate value predictor Front-end execution correct most of the time Common case: 99% of loads happen at right time Speculation is on timing of load store pairs Two-level LSQ speculate on the scope of stores Relatively expensive repl

文档评论(0)

qiwqpu54 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档