Supporting Nested Transactional Memory in LogTM在LogTM支持嵌套事务内存.pptVIP

ASPLOS06 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 (inc