Abstract

As one of the most potential solution to parallel programming on the future many-core platforms, Transactional Memory (TM) systems have attracted a great deal of attention from both the industry and academic since the first TM was proposed in 1993. Various design and implementation proposals have been proposed to improve the performance while reducing the overheads. Recent investigations of the high-contention and coarse-grained transactional workloads on TMs reveal various pathologies that will offset the performance benefits. In this paper, we analysis the advantages and disadvantages of the existing conflict management and version management schemes, make a case study in the interplay between conflict management and version management in hardware transactional memory systems, to learn its impact on performance and find some interesting appearance that can guide the future design. In particular, apply software runtime environment to support recognize application's dynamic behaviors and resolve transactional conflicts can obtain an average speedup of 11.7% across the 8 applications selected from the STAMP benchmark suite on DynTM, which is regarded as one of the most latest progress in hardware transactional memory systems.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.