supporting nested transactional memory in logtm.ppt

supporting nested transactional memory in logtm.ppt

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

ASPLOS'06 10/25 Wisconsin Multifacet Project 10/25/06 LogTM: Log-based Transactional Memory ? 2006 Mulitfacet Project Supporting Nested Transactional Memory in LogTM Michelle J. Moravan, Jayaram Bobba, Kevin E. Moore, Luke Yen, Mark D. Hill, Ben Liblit, Michael M. Swift, David A. Wood Motivation Composability Complex software built from existing modules Concurrency “Intel has 10 projects in the works that contain four or more computing cores per chip” -- Paul Otellini, Intel CEO, Fall ’05 Communication Operating system services Run-time system interactions Nested LogTM Closed nesting: transactions remain isolated until parent commits Open nesting: transactions commit independent of parent Escape actions: non-transactional execution for system calls and I/O Composability Composability: Closed Nested Transactions Modules expose interfaces, not implementations Must allow transactions within transactions Example Insert() calls getID() from within a transaction The getID() transaction is nested inside the insert() transaction int getID() { begin_transaction(); id = global_id++; commit_transaction(); return id; } Closed Nesting On Commit child transaction is merged with its parent Flat Nested transactions “flattened” into a single transaction Only outermost begins/commits are meaningful Any conflict aborts to outermost transaction Partial rollback Child transaction can be aborted independently Can avoid costly re-execution of parent transaction But child merges transaction state with parent on commit So most conflicts with child end up affecting the parent Conflict Detection in Nested LogTM Flat LogTM detects conflicts with directory coherence and Read (R ) and Write (W ) bits in caches Nested LogTM replicates R/W bits for each level Flash-Or circuit merges child and parent R/W bits Version Management in Nested LogTM Flat LogTM’s log is a single frame (header + undo records) Nested LogTM’s log is a stack of frames A frame contains: Header (in

您可能关注的文档

文档评论(0)

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

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

1亿VIP精品文档

相关文档