Evaluating the Effect of Last-Level Cache Sharing on Integrated GPU-CPU Systems with Heterogeneous Applications
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Parallel Computer Architecture
Parallel Computer Architecture Introduction to Parallel Computing CIS 410/510 Department of Computer and Information Science Lecture 2 – Parallel Architecture Outline q Parallel architecture types q Instruction-level parallelism q Vector processing q SIMD q Shared memory ❍ Memory organization: UMA, NUMA ❍ Coherency: CC-UMA, CC-NUMA q Interconnection networks q Distributed memory q Clusters q Clusters of SMPs q Heterogeneous clusters of SMPs Introduction to Parallel Computing, University of Oregon, IPCC Lecture 2 – Parallel Architecture 2 Parallel Architecture Types • Uniprocessor • Shared Memory – Scalar processor Multiprocessor (SMP) processor – Shared memory address space – Bus-based memory system memory processor … processor – Vector processor bus processor vector memory memory – Interconnection network – Single Instruction Multiple processor … processor Data (SIMD) network processor … … memory memory Introduction to Parallel Computing, University of Oregon, IPCC Lecture 2 – Parallel Architecture 3 Parallel Architecture Types (2) • Distributed Memory • Cluster of SMPs Multiprocessor – Shared memory addressing – Message passing within SMP node between nodes – Message passing between SMP memory memory nodes … M M processor processor … … P … P P P interconnec2on network network interface interconnec2on network processor processor … P … P P … P memory memory … M M – Massively Parallel Processor (MPP) – Can also be regarded as MPP if • Many, many processors processor number is large Introduction to Parallel Computing, University of Oregon, -
Reducing Cache Coherence Traffic with a NUMA-Aware Runtime Approach
This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TPDS.2017.2787123, IEEE Transactions on Parallel and Distributed Systems IEEE TRANSACTIONS ON PARALLEL AND DISTRIBUTED SYSTEMS, VOL. XX, NO. X, MONTH YEAR 1 Reducing Cache Coherence Traffic with a NUMA-Aware Runtime Approach Paul Caheny, Lluc Alvarez, Said Derradji, Mateo Valero, Fellow, IEEE, Miquel Moreto,´ Marc Casas Abstract—Cache Coherent NUMA (ccNUMA) architectures are a widespread paradigm due to the benefits they provide for scaling core count and memory capacity. Also, the flat memory address space they offer considerably improves programmability. However, ccNUMA architectures require sophisticated and expensive cache coherence protocols to enforce correctness during parallel executions, which trigger a significant amount of on- and off-chip traffic in the system. This paper analyses how coherence traffic may be best constrained in a large, real ccNUMA platform comprising 288 cores through the use of a joint hardware/software approach. For several benchmarks, we study coherence traffic in detail under the influence of an added hierarchical cache layer in the directory protocol combined with runtime managed NUMA-aware scheduling and data allocation techniques to make most efficient use of the added hardware. The effectiveness of this joint approach is demonstrated by speedups of 3.14x to 9.97x and coherence traffic reductions of up to 99% in comparison to NUMA-oblivious scheduling and data allocation. Index Terms—Cache Coherence, NUMA, Task-based programming models F 1 INTRODUCTION HE ccNUMA approach to memory system architecture the data is allocated within the NUMA regions of the system T has become a ubiquitous choice in the design-space [10], [28]. -
Thread-Level Parallelism – Part 1
Chapter 5: Thread-Level Parallelism – Part 1 Introduction What is a parallel or multiprocessor system? Why parallel architecture? Performance potential Flynn classification Communication models Architectures Centralized shared-memory Distributed shared-memory Parallel programming Synchronization Memory consistency models What is a parallel or multiprocessor system? Multiple processor units working together to solve the same problem Key architectural issue: Communication model Why parallel architectures? Absolute performance Technology and architecture trends Dennard scaling, ILP wall, Moore’s law Multicore chips Connect multicore together for even more parallelism Performance Potential Amdahl's Law is pessimistic Let s be the serial part Let p be the part that can be parallelized n ways Serial: SSPPPPPP 6 processors: SSP P P P P P Speedup = 8/3 = 2.67 1 T(n) = s+p/n As n → , T(n) → 1 s Pessimistic Performance Potential (Cont.) Gustafson's Corollary Amdahl's law holds if run same problem size on larger machines But in practice, we run larger problems and ''wait'' the same time Performance Potential (Cont.) Gustafson's Corollary (Cont.) Assume for larger problem sizes Serial time fixed (at s) Parallel time proportional to problem size (truth more complicated) Old Serial: SSPPPPPP 6 processors: SSPPPPPP PPPPPP PPPPPP PPPPPP PPPPPP PPPPPP Hypothetical Serial: SSPPPPPP PPPPPP PPPPPP PPPPPP PPPPPP PPPPPP Speedup = (8+5*6)/8 = 4.75 T'(n) = s + n*p; T'() → !!!! How does your algorithm ''scale up''? Flynn classification Single-Instruction Single-Data -
Efficient Synchronization Mechanisms for Scalable GPU Architectures
Efficient Synchronization Mechanisms for Scalable GPU Architectures by Xiaowei Ren M.Sc., Xi’an Jiaotong University, 2015 B.Sc., Xi’an Jiaotong University, 2012 a thesis submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the faculty of graduate and postdoctoral studies (Electrical and Computer Engineering) The University of British Columbia (Vancouver) October 2020 © Xiaowei Ren, 2020 The following individuals certify that they have read, and recommend to the Faculty of Graduate and Postdoctoral Studies for acceptance, the dissertation entitled: Efficient Synchronization Mechanisms for Scalable GPU Architectures submitted by Xiaowei Ren in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Electrical and Computer Engineering. Examining Committee: Mieszko Lis, Electrical and Computer Engineering Supervisor Steve Wilton, Electrical and Computer Engineering Supervisory Committee Member Konrad Walus, Electrical and Computer Engineering University Examiner Ivan Beschastnikh, Computer Science University Examiner Vijay Nagarajan, School of Informatics, University of Edinburgh External Examiner Additional Supervisory Committee Members: Tor Aamodt, Electrical and Computer Engineering Supervisory Committee Member ii Abstract The Graphics Processing Unit (GPU) has become a mainstream computing platform for a wide range of applications. Unlike latency-critical Central Processing Units (CPUs), throughput-oriented GPUs provide high performance by exploiting massive application parallelism. -
How to Manually Switch Graphics Cards Macbook Pro
How To Manually Switch Graphics Cards Macbook Pro How to manually switch between dedicated and integrated graphics Is there a "hack" to switch between graphics processors on the Retina Display MacBook Pro makes it possible to easily switch between graphics cards manually on these. gpu-switch is an application that allows to switch between the graphic cards of dual-GPU Macbook Pro models. On these computers, the "automatic graphics switching" option is turned on by how to determine which graphics card is in use on a 15" or 17" MacBook Pro. MacBook Pro models that were affected by this problem would often have visual the picture above for a half a second while switching between graphics cards). capsule backup in this mode so have to keep manually backing up my data. When using a Mac that supports automatic graphics switching, the system will Two entries should appear under Video Card: "Intel HD Graphics 4000". Installing Arch Linux on a MacBook (Air/Pro) or an iMac is quite similar to installing it on any other computer. Boot installation medium and switch to a free tty. and work through until you get to Prepare Hard Drive and use the "Manually configure block devices. Different MacBook models have different graphic cards. How To Manually Switch Graphics Cards Macbook Pro Read/Download Several support threads discussing issue related to GPU switching. Some early Retina-equipped MacBook Pro users are seeing graphical issues in Safari. Earlier "Late 2008" and "Mid-2009" MacBook Pro models equipped with dual graphics A tool called gfxCardStatus allows to switch it manually: gfx.io/. -
Op E N So U R C E Yea R B O O K 2 0
OPEN SOURCE YEARBOOK 2016 ..... ........ .... ... .. .... .. .. ... .. OPENSOURCE.COM Opensource.com publishes stories about creating, adopting, and sharing open source solutions. Visit Opensource.com to learn more about how the open source way is improving technologies, education, business, government, health, law, entertainment, humanitarian efforts, and more. Submit a story idea: https://opensource.com/story Email us: [email protected] Chat with us in Freenode IRC: #opensource.com . OPEN SOURCE YEARBOOK 2016 . OPENSOURCE.COM 3 ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ OPENSOURCE.COM...... ........ .. .. .. ... .... ........ WRITE FOR US ..... .. .. .. ... .... 7 big reasons to contribute to Opensource.com: Career benefits: “I probably would not have gotten my most recent job if it had not been for my articles on 1 Opensource.com.” Raise awareness: “The platform and publicity that is available through Opensource.com is extremely 2 valuable.” Grow your network: “I met a lot of interesting people after that, boosted my blog stats immediately, and 3 even got some business offers!” Contribute back to open source communities: “Writing for Opensource.com has allowed me to give 4 back to a community of users and developers from whom I have truly benefited for many years.” Receive free, professional editing services: “The team helps me, through feedback, on improving my 5 writing skills.” We’re loveable: “I love the Opensource.com team. I have known some of them for years and they are 6 good people.” 7 Writing for us is easy: “I couldn't have been more pleased with my writing experience.” Email us to learn more or to share your feedback about writing for us: https://opensource.com/story Visit our Participate page to more about joining in the Opensource.com community: https://opensource.com/participate Find our editorial team, moderators, authors, and readers on Freenode IRC at #opensource.com: https://opensource.com/irc . -
Versapipe: a Versatile Programming Framework for Pipelined Computing on GPU
VersaPipe: A Versatile Programming Framework for Pipelined Computing on GPU Zhen Zheng Chanyoung Oh Jidong Zhai Tsinghua University University of Seoul Tsinghua University [email protected] [email protected] [email protected] Xipeng Shen Youngmin Yi Wenguang Chen North Carolina State University University of Seoul Tsinghua University [email protected] [email protected] [email protected] ABSTRACT 1 INTRODUCTION Pipeline is an important programming pattern, while GPU, designed Pipeline parallel programming is commonly used to exert the full mostly for data-level parallel executions, lacks an ecient mecha- parallelism of some important applications, ranging from face detec- nism to support pipeline programming and executions. This paper tion to network packet processing, graph rendering, video encoding provides a systematic examination of various existing pipeline exe- and decoding [11, 31, 34, 42, 46]. A pipeline program consists of a cution models on GPU, and analyzes their strengths and weaknesses. chain of processing stages, which have a producer-consumer rela- To address their shortcomings, this paper then proposes three new tionship. The output of a stage is the input of the next stage. Figure 1 execution models equipped with much improved controllability, shows Reyes rendering pipeline [12], a popular image rendering al- including a hybrid model that is capable of getting the strengths gorithm in computer graphics. It uses one recursive stage and three of all. These insights ultimately lead to the development of a soft- other stages to render an image. In general, any programs that have ware programming framework named VersaPipe. With VersaPipe, multiple stages with the input data going through these stages in users only need to write the operations for each pipeline stage. -
CIS 501 Computer Architecture This Unit: Shared Memory
This Unit: Shared Memory Multiprocessors App App App • Thread-level parallelism (TLP) System software • Shared memory model • Multiplexed uniprocessor CIS 501 Mem CPUCPU I/O CPUCPU • Hardware multihreading CPUCPU Computer Architecture • Multiprocessing • Synchronization • Lock implementation Unit 9: Multicore • Locking gotchas (Shared Memory Multiprocessors) • Cache coherence Slides originally developed by Amir Roth with contributions by Milo Martin • Bus-based protocols at University of Pennsylvania with sources that included University of • Directory protocols Wisconsin slides by Mark Hill, Guri Sohi, Jim Smith, and David Wood. • Memory consistency models CIS 501 (Martin): Multicore 1 CIS 501 (Martin): Multicore 2 Readings Beyond Implicit Parallelism • Textbook (MA:FSPTCM) • Consider “daxpy”: • Sections 7.0, 7.1.3, 7.2-7.4 daxpy(double *x, double *y, double *z, double a): for (i = 0; i < SIZE; i++) • Section 8.2 Z[i] = a*x[i] + y[i]; • Lots of instruction-level parallelism (ILP) • Great! • But how much can we really exploit? 4 wide? 8 wide? • Limits to (efficient) super-scalar execution • But, if SIZE is 10,000, the loop has 10,000-way parallelism! • How do we exploit it? CIS 501 (Martin): Multicore 3 CIS 501 (Martin): Multicore 4 Explicit Parallelism Multiplying Performance • Consider “daxpy”: • A single processor can only be so fast daxpy(double *x, double *y, double *z, double a): • Limited clock frequency for (i = 0; i < SIZE; i++) • Limited instruction-level parallelism Z[i] = a*x[i] + y[i]; • Limited cache hierarchy • Break it -
Shared-Memory Multiprocessors Gates & Transistors
This Unit: Shared Memory Multiprocessors Application • Three issues OS • Cache coherence Compiler Firmware CIS 501 • Synchronization • Memory consistency Introduction To Computer Architecture CPU I/O Memory • Two cache coherence approaches • “Snooping” (SMPs): < 16 processors Digital Circuits • “Directory”/Scalable: lots of processors Unit 11: Shared-Memory Multiprocessors Gates & Transistors CIS 501 (Martin/Roth): Shared Memory Multiprocessors 1 CIS 501 (Martin/Roth): Shared Memory Multiprocessors 2 Readings Thread-Level Parallelism struct acct_t { int bal; }; • H+P shared struct acct_t accts[MAX_ACCT]; • Chapter 6 int id,amt; 0: addi r1,accts,r3 if (accts[id].bal >= amt) 1: ld 0(r3),r4 { 2: blt r4,r2,6 accts[id].bal -= amt; 3: sub r4,r2,r4 spew_cash(); 4: st r4,0(r3) } 5: call spew_cash • Thread-level parallelism (TLP) • Collection of asynchronous tasks: not started and stopped together • Data shared loosely, dynamically • Example: database/web server (each query is a thread) • accts is shared, can’t register allocate even if it were scalar • id and amt are private variables, register allocated to r1, r2 • Focus on this CIS 501 (Martin/Roth): Shared Memory Multiprocessors 3 CIS 501 (Martin/Roth): Shared Memory Multiprocessors 4 Shared Memory Shared-Memory Multiprocessors • Shared memory • Provide a shared-memory abstraction • Multiple execution contexts sharing a single address space • Familiar and efficient for programmers • Multiple programs (MIMD) • Or more frequently: multiple copies of one program (SPMD) P1 P2 P3 P4 • Implicit (automatic) communication via loads and stores + Simple software • No need for messages, communication happens naturally – Maybe too naturally • Supports irregular, dynamic communication patterns Memory System • Both DLP and TLP – Complex hardware • Must create a uniform view of memory • Several aspects to this as we will see CIS 501 (Martin/Roth): Shared Memory Multiprocessors 5 CIS 501 (Martin/Roth): Shared Memory Multiprocessors 6 Shared-Memory Multiprocessors Paired vs. -
Hard Disk Drive
V10.1.00 Preface Notice The company reserves the right to revise this publication or to change its contents without notice. Information contained herein is for reference only and does not constitute a commitment on the part of the manufacturer or any subsequent vendor. They assume no responsibility or liability for any errors or inaccuracies that may appear in this publication nor are they in anyway responsible for any loss or damage resulting from the use (or misuse) of this publication. This publication and any accompanying software may not, in whole or in part, be reproduced, translated, trans- mitted or reduced to any machine readable form without prior consent from the vendor, manufacturer or creators of this publication, except for copies kept by the user for backup purposes. Brand and product names mentioned in this publication may or may not be copyrights and/or registered trade- marks of their respective companies. They are mentioned for identification purposes only and are not intended as an endorsement of that product or its manufacturer. ©May 2010 Trademarks Intel and Intel Core are trademarks/registered trademarks of Intel Corporation. I Preface R&TTE Directive This device is in compliance with the essential requirements and other relevant provisions of the R&TTE Direc- tive 1999/5/EC. This device will be sold in the following EEA countries: Austria, Italy, Belgium, Liechtenstein, Denmark, Lux- embourg, Finland, Netherlands, France, Norway, Germany, Portugal, Greece, Spain, Iceland, Sweden, Ireland, United Kingdom, Cyprus, Czech Republic, Estonia, Hungary, Latvia, Lithuania, Malta, Slovakia, Poland, Slov- enia. II Preface FCC Statement (Federal Communications Commission) You are cautioned that changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. -
Tardis: Time Traveling Coherence Algorithm for Distributed Shared Memory
Tardis: Time Traveling Coherence Algorithm for Distributed Shared Memory Xiangyao Yu Srinivas Devadas CSAIL, MIT CSAIL, MIT Cambridge, MA, USA Cambridge, MA, USA [email protected] [email protected] Abstract—A new memory coherence protocol, Tardis, is pro- requiring a globally synchronized clock unlike prior timestamp posed. Tardis uses timestamp counters representing logical time coherence schemes (e.g., [9], [10]), and without requiring as well as physical time to order memory operations and enforce multicast/broadcast support unlike prior directory coherence sequential consistency in any type of shared memory system. Tardis is unique in that as compared to the widely-adopted schemes (e.g., [11], [12]). In Tardis, only the timestamps directory coherence protocol, and its variants, it completely and the owner ID need to be stored for each address for a avoids multicasting and only requires O(log N) storage per O(log N) cost where N is the number of processors or cores; cache block for an N-core system rather than O(N) sharer the O(N) sharer information of common directory protocols information. Tardis is simpler and easier to reason about, yet is not required. The requirement of storing sharers is avoided achieves similar performance to directory protocols on a wide range of benchmarks run on 16, 64 and 256 cores. partly through the novel insight that a writer can instantly jump 1 Index Terms—coherence; timestamp; scalability; sequential ahead to a time when the sharer copies have expired and consistency; immediately perform the write without violating sequential consistency. A formal proof that Tardis satisfies sequential I. -
Gpgpu & Accelerators
Bimalee Salpitikorala Thilina Gunarathne GPGPU & ACCELERATORS CPU . Optimized for sequential performance . Extracting Instruction level parallelism is difficult Control hardware to check for dependencies, out-of-order execution, prediction logic etc . Control hardware dominates CPU Complex, difficult to build and verify . Does not do actual computation but consumes power . Pollack’s Rule Performance ~ sqrt(area) To increase sequential performance 2 times, area 4 times Increase performance using 2 cores, area only 2 times GPU . High-performance many-core processors . Data Parallelized Machine -SIMD Architecture . Less control hardware . High computational performance GPU vs CPU GFLOPS graph http://courses.ece.illinois.edu/ece498/al/textbook/Chapter1-Introduction.pdf GPU - Accelerator? No, not this .... Accelerator? . Speed up some aspect of the computing workload . Implemented as a coprocessor to the host- Its own instruction set Its own memory (usually but not always). To the hardware - another IO unit . To the software – another computer . Today's accelerators Sony/Toshiba/IBM Cell Broadband Engine GPUs How the GPU Fits into the Overall Computer System Graphics pipeline GPU Architecture http://http.download.nvidia.com/developer/GPU_Gems_2/GPU_Gems2_ch30.pdf GPU Pipeline . CPU to GPU data transfer . Vertex processing . Cull / Clip /Set up . Rasterization . Texture & Fragment processing . Compare & blend CPU to GPU data transfer . Through a graphics connector PCI Express AGP slot on the motherboard . Graphics connector transfers properties at the end points (vertices) or control points of the geometric primitives ( lines and triangles). The type of properties provided per vertex x-y-z coordinates RGB values Texture Reflectivity etc.. Vertex processing Vertex processor/vertex shaders http://http.download.nvidia.com/developer/GPU_Gems_2/GPU_Gems2_ch30.pdf Cull/ Clip/ Set up .