40 likes | 186 Views
Why build transactional memory workloads?. Tim Harris. The transactional elephant. How do all these issues fit into the bigger picture (just the trunk, as it were, of the concurrency elephant).
E N D
Why build transactional memory workloads? Tim Harris
The transactional elephant How do all these issues fit into the bigger picture (just the trunk, as it were, of the concurrency elephant) Semantics of atomic blocks, progress guarantees, forms of nesting, interaction outside the transaction Other applications of transactional memory – e.g. speculation Software transactional memory algorithms and APIs Compiling and optimizing atomic blocks to STM APIs Hardware transactional memory Hardware acceleration of software transactional memory
Why build transactional workloads? • Several different motivations • Provide an improved basis for quantitative decision making • Larger applications rather than concurrent data structures with synthetic workloads • Gather evidence to help us make design choices further up the stack • Do we need to make many forms of IO transactions, do we need condition synchronization, do we really just need updates to shared memory? • What other abstractions do we need when designing future languages for multi-core processors? Does the experience using transactions help identify new research directions?
Current ideas for concrete steps Identify application areas relevant for desktop multi-core computing Make these “challenges” widely available. How can we agree on these and make them available quickly? Develop parallel implementations using a range of abstractions and APIs Try to share these too for comparative assessment of techniques Compare perf impact of different API implementations