High Performance Computing : Parallel Processing Models and Architectures / Marco Vanneschi

Total Page:16

File Type:pdf, Size:1020Kb

High Performance Computing : Parallel Processing Models and Architectures / Marco Vanneschi Marco Vanneschi High Performance Computing Parallel Processing Models and Architectures Vanneschi, Marco High performance computing : parallel processing models and architectures / Marco Vanneschi. - Pisa : Pisa university press, 2014. – (Manuali) 004.35 (22.) 1. Elaborazione parallela dei dati CIP a cura del Sistema bibliotecario dell’Università di Pisa © Copyright 2014 by Pisa University Press srl Società con socio unico Università di Pisa Capitale Sociale € 20.000,00 i.v. - Partita IVA 02047370503 Sede legale: Lungarno Pacinotti 43/44 - 56126 Pisa Tel. + 39 050 2212056 - Fax + 39 050 2212945 [email protected] www.pisauniversitypress.it ISBN 978-88-6741-372-0 Le fotocopie per uso personale del lettore possono essere effettuate nei limiti del 15% di ciascun volume/ fascicolo di periodico dietro pagamento alla SIAE del compenso previsto dall’art. 68, commi 4 e 5, della legge 22 aprile 1941 n. 633. Le riproduzioni effettuate per fi nalità di carattere professionale, economico o commerciale o comunque per uso diverso da quello personale possono essere effettuate a seguito di specifi ca autorizzazione rilasciata da AIDRO, Corso di Porta Romana, 108 – 20122 Milano, [email protected] – www.aidro.org A Giovanna Preface This book is the result of my integrated research and teaching experience in High Performance Computing at the Computer Science Department, University of Pisa. During several years, a continuous and collaborative effort has been done for properly exploiting the research experience in teaching Master Degree courses on advanced architectures, programming models and systems. At the same time, the teaching experience has often stimulated new research activities on subject matters needing a more scientific and methodological treatment, as well as a better integration of methodology and technology. This positive feedback has been enabled by the joint work with my collaborators and by a large number of Master and PhD dissertations. The book is currently used in the High Performance Computing course of the international Master Degree Program in Computer Science and Networking, a joint initiative of University of Pisa and Scuola Superiore Sant’Anna. Subject matters and goals High Performance Computing (HPC) is the ICT area that studies hardware-software architectures and applications characterized by requirements for high processing bandwidth, low response time, high efficiency and scalability, as well as availability and energy efficiency. Many scientific, commercial and technological disciplines benefit from HPC systems and tools: physics, chemistry, earth sciences, biology, medicine, engineering, environmental control, emergency management, telecommunications, software defined networking, information retrieval, big data, intelligent sensors, image and signal processing, multimedia, finance and economy, and so on. HPC is not limited to scientific supercomputing, though this is a very challenging arena. Industrial, commercial and embedded applications are perceived as quite strategic areas, which, in addition to raw performance, require modularity, portability and programmability. HPC is synonymous with parallel and distributed processing. Any HPC product is manly based on parallelism exploitation: at the process/thread level (shared memory SMP/NUMA multiprocessors, distributed memory multicomputers and heterogeenous clusters), at the instruction level (pipeline scalar and superscalar CPUs, vectorization facilities, stream processing and SIMT-GPUs). Typical HPC system configurations range from few processing elements to hundreds and thousands of processors/computers. Currently, an important technological evolution/revolution is under way: multi-/many- core components, or chip multiprocessors, will replace (are replacing) uniprocessor-based CPUs for both the scientific and the commercial market. This fact has enormous implications on technologies and applications: in some measure, all hardware-software products will be based on parallel processing. In this evolution/revolution, a fundamental role is played by high-level and portable programming tools and application development frameworks: they are becoming first- II class citizens in HPC field too, although currently a wide gap still exists between parallel architecture and parallel programming maturity. For too many years, parallel program design has been the realm of unstructured approaches based on low-level tools and specialized libraries. By now, the need for a user-friendly and solid application- architecture bridge has been widely recognized: achieving a proper trade-off in the complex interrelationships of performance, programmability and portability issues is a must. The aim of this book is: 1. to provide fundamental models and methodologies for parallel programming and parallel applications development, 2. to study parallel architectures thoroughly, at the state-of-the-art and according to the research trends, 3. to establish a strong relationship between parallel application methodologies and parallel architectures. Approach and organization of the book In this book parallel programming and parallel architectures are studied as two strongly interrelated areas in high-performance computing. Programming models and tools are characterized by a properly abstract view of the parallel architecture. At the same time, parallel architectures support such models and tools in the most effective and seamless way. Concepts and techniques, both in programming methodologies and in parallel architectures, are studied according to a uniform and structured approach. Design and implementation models and cost models (i.e. performance models) are defined for parallel programming methodologies, for parallel architectures, and for their integration. The book is organized into three Parts: 1. Parallel Processing Models and Methodology, 2. Single Instruction Stream Architectures, 3. Multiple Instruction Stream Architectures. Part 1 studies fundamental concepts and techniques in parallel computation structuring and design, including parallelization methodologies and paradigms, parallel programming models, their implementation, and related cost models. Models and methodologies of Part 1 are fundamental, not only for parallel programming and application development, but also for designing, understanding and evaluating parallel architectures and machine structures. In other words, Part1 defines also the conceptual and technical framework for the “hardware-software” integration of parallel applications and parallel architectures. Parts 2 and 3 study architectures of high-performance computing systems, including instruction level parallelism, SIMD/SIMT technologies, shared memory multiprocessors, distributed memory multicomputers, high performance interconnect structures. At the light of the strategic role played by chip multiprocessors (CMP), a large space is dedicated to CMP-based architectures: implementation and cost models for shared memory organization, processor synchronization, cache coherence, memory ordering, and communication run-time support,. All issues in parallel programming and parallel architecture are dealt with in terms of structural models, static and dynamic support to computation and programming models, III performance evaluation, capability for building complex and heterogeneous applications and/or enabling platforms. Models and methodologies precede the description of technologies and products (multi-/many-core technology, high-performance networks and interconnect technologies, parallel programming tools). Through this approach the reader will be able to understand and to critically analyze current/future products and/or to properly adapt/combine them, as well as to conceive new solutions. The book contains a large number of examples, exercises and case studies. Part 1: Parallel Processing Models and Methodology This Part deals with systematic methods and techniques for the design of high- performance parallel and distributed computations. The goal is to achieve a good trade- off between two contrasting requirements: programmability and portability, on one side, and performance and efficiency, on the other side. The methodology is based on two interrelated issues: structured parallelism paradigms and cost models. Structured parallelism paradigms aim to provide standard and effective rules for composing parallel computations in a machine-independent manner. Cost models are defined for performance evaluation and prediction, and are fundamental for reducing parallel software design complexity. Cost models will take into account application- and architecture-dependent parameters related to calculation, storage and communication. Contents: 1. HPC and structured parallel computations 2. Metrics for performance evaluation 3. Interprocess communication 4. Basic cost model for acyclic graph computations 5. Pipeline paradigm 6. Farm paradigm 7. Data parallel paradigms 8. Examples of parallel program design 9. Client-server computations Methodology of Part 1 has much wider applicability. In Parts 2 and 3 it is used for studying properties and performances of parallel architectures. Part 2: Single Instruction Stream Architectures This Part applies the general methodology of Part 1 to the firmware architecture level, i.e. structured parallel computations are implemented as collections of communicating processing units. After high-performance communication techniques, we study parallel structures for efficient cache hierarchies and for Instruction Level Parallelism (ILP) basic
Recommended publications
  • Automatic Temperature Controls
    230900S03 INSTRUMENTATION AND CONTROL FOR HVAC UK Controls Standard SECTION 230900S03 - AUTOMATIC TEMPERATURE CONTROLS PART 1 - GENERAL RELATED DOCUMENTS: Drawings and general provisions of the Contract, including General and Supplementary Conditions, General Mechanical Provisions and General Requirements, Division 1 Specification Sections apply to the work specified in this section. DESCRIPTION OF WORK: Furnish a BACnet system compatible with existing University systems. All building controllers, application controllers, and all input/output devices shall communicate using the protocols and network standards as defined by ANSI/ASHRAE Standard 135-2001, BACnet. This system shall communicate with the University of Kentucky Facility Management’s existing BACnet head-end software using BACnet/IP at the tier 1 level and BACnet/MSTP at the tier 2 level. No gateways shall be used for communication to controllers installed under section. BACnet/MSTP or BACnet/IP shall be used for all other tiers of communication. No servers shall be used for communication to controllers installed under this section. If servers are required, all hardware and operating systems must be approved by the Facilities Management Controls Engineering Manager and/or the Facilities Management Information Technology Manager. All Building Automation Devices should be located behind the University firewall, but outside of the Medical Center Firewall and on the environmental VLAN. Provide all necessary hardware and software to meet the system’s functional specifications. Provide Protocol Implementation Conformance Statement (PICS) for Windows-based control software and every controller in system, including unitary controllers. These must be in compliance with Front End systems PICS and BIBBS and attached Tridium PICS and BIBBS.
    [Show full text]
  • High Performance Platforms
    High Performance Platforms Salvatore Orlando High Perfoamnce Computing - S. Orlando 1 Scope of Parallelism: the roadmap towards HPC • Conventional architectures are coarsely comprised of – processor, memory system, I/O • Each of these components presents significant performance bottlenecks. – It is important to understand each of these performance bottlenecks to reduce their effects • Parallelism addresses each of these components in significant ways to improve performance and reduce the bottlenecks • Applications utilize different aspects of parallelism, e.g., – data intensive applications utilize high aggregate memory bandwidth – server applications utilize high aggregate network bandwidth – scientific applications typically utilize high processing and memory system performance High Perfoamnce Computing - S. Orlando 2 Implicit Parallelism: Trends in Microprocessor Architectures • Microprocessor clock speeds have posted impressive gains over the past two decades (two to three orders of magnitude) – there are limits to this increase, also due to power consumption and heat dissipation • Higher levels of device integration have made available a large number of transistors – the issue is how best to transform these large amount of transistors into computational power • Single-core processors use these resources in multiple functional units and execute multiple instructions in the same cycle. • The precise manner in which these instructions are selected and executed provides impressive diversity in architectures. High Perfoamnce Computing - S. Orlando 3 ILP High Perfoamnce Computing - S. Orlando 4 Instruction Level Parallelism • Pipelining overlaps various stages of instruction execution to achieve performance • At a high level of abstraction, an instruction can be executed while the next one is being decoded and the next one is being fetched. • This is akin to an assembly line for manufacture of cars.
    [Show full text]
  • Multiprocessing Contents
    Multiprocessing Contents 1 Multiprocessing 1 1.1 Pre-history .............................................. 1 1.2 Key topics ............................................... 1 1.2.1 Processor symmetry ...................................... 1 1.2.2 Instruction and data streams ................................. 1 1.2.3 Processor coupling ...................................... 2 1.2.4 Multiprocessor Communication Architecture ......................... 2 1.3 Flynn’s taxonomy ........................................... 2 1.3.1 SISD multiprocessing ..................................... 2 1.3.2 SIMD multiprocessing .................................... 2 1.3.3 MISD multiprocessing .................................... 3 1.3.4 MIMD multiprocessing .................................... 3 1.4 See also ................................................ 3 1.5 References ............................................... 3 2 Computer multitasking 5 2.1 Multiprogramming .......................................... 5 2.2 Cooperative multitasking ....................................... 6 2.3 Preemptive multitasking ....................................... 6 2.4 Real time ............................................... 7 2.5 Multithreading ............................................ 7 2.6 Memory protection .......................................... 7 2.7 Memory swapping .......................................... 7 2.8 Programming ............................................. 7 2.9 See also ................................................ 8 2.10 References .............................................
    [Show full text]
  • K1DM3 Control System Software User's Guide
    K1DM3 Control System Software User's Guide William Deich University of California Observatories 07 Jan 2020 ver 3.7b Contents 1 Overview 6 1.1 Active Components of K1DM3..........................6 1.1.1 Drum....................................6 1.1.2 Swingarm..................................9 1.2 Position Summary................................. 13 1.3 Motion Controllers................................. 13 1.4 Software....................................... 14 1.4.1 Back-end Services............................. 14 1.4.2 End-User Applications........................... 15 1.5 K1DM3 Private Network.............................. 15 2 Starting, Stopping, Suspending Services 17 2.1 Starting/Stopping................................. 17 2.2 Suspending Dispatchers.............................. 19 2.3 Special No-Dock Engineering Version....................... 19 2.4 Periodic Restarts.................................. 20 3 Components, Assemblies, and Sequencers 21 3.1 Elementary Components.............................. 21 3.2 Compound Keywords............................... 22 3.3 Assemblies...................................... 22 3.4 Sequencers..................................... 23 3.5 The ACTIVATE Sequencer............................ 24 3.6 The M3AGENT Sequencer............................ 27 3.7 Monitoring Sequencer Execution......................... 27 4 Dispatcher Interfaces for Routine Operations 29 4.1 TCS Operations.................................. 31 4.2 M3AGENT..................................... 32 4.3 Hand Paddle...................................
    [Show full text]
  • Computer Structures for Distributed Systems Liam
    COMPUTER STRUCTURES FOR DISTRIBUTED SYSTEMS LIAM MAURICE CASEY C DOCTOR OF PHILOSOPHY UNIVERSITY OF EDINBURGH 1977. - ABSTRPCI: A building block approach to configuring large corruter. iEerns is attractive because the blocks, either primitive processors or small computers, are daily becoming cheaper and because this approach alloiis a close match of the pcwer required to the pciler supplied. This thesis addresses the design goal of an expandable system where there is no premium paid for a minimal configuration and the cost of extra units of capacity is constant. It is shoiin that a distributed system, a system of homogeneous canputers loosely coupled by a cartmunication subsystem, is likely to be the best approach to this design goal. Some consideration is given to the form of the canmunication subsystem but the rain research is directed to.ards the software organisation required to achieve efficient co-operation between the canputers constituting the distributed system. An organisation based on the domain structures of protection schenEs is found to have advantages. Hitherto dcirtain management using capabilities has been centred around systems with shared. primary memory. This is because central tables have been required to implement the capability rrechanism. A model is developed which, by restricting. the sharing of some items and providing a 'global object' managerrent scheme to cover essential sharing, enables central tables to be dispensed with and dcmain managenent to be distributed. The main goal in achieving this extension is to facilitate dynamic and efficient load sharing but the model could equally well be used to provide, in distributed systems, the protection normally associated with danains.
    [Show full text]
  • Stuart Elliot Madnick V37
    STUART ELLIOT MADNICK V37 John Norris Maguire Professor of Information Technology Sloan School of Management and Professor of Engineering Systems Sloan School of Engineering Massachusetts Institute of Technology TABLE OF CONTENTS EDUCATION ............................................................................................. 1 PRINCIPAL FIELD OF INTEREST ........................................................ 1 NAME AND RANK OF OTHER FACULTY IN SAME FIELD ......... 1 1. SUMMARY OF NON-MIT EXPERIENCE ....................................... 2 2. SUMMARY OF MIT APPOINTMENTS ........................................... 4 3. COMMITTEES ...................................................................................... 5 4. CONSULTING ACTIVITIES .............................................................. 8 5. PROFESSIONAL ACTIVITIES ............................................................ 11 6. PROFESSIONAL SOCIETIES ............................................................. 14 7. SUBJECTS TAUGHT ............................................................................ 15 8. THESIS SUPERVISION ....................................................................... 19 9. RESEARCH PROJECT SUPERVISION (Principal Investigator or co-PI) .... 28 10. PUBLICATIONS ................................................................................ 32 10.1 BOOKS AND MONOGRAPHS ........................................................................................................ 32 10.2 BOOK CHAPTERS ...........................................................................................................................
    [Show full text]
  • Hb Lee Hvac Upgrades Specifications
    SECTION 00 01 10 TABLE OF CONTENTS DESCRIPTION OF CONTENTS The complete Contract Documents contain the following: VOLUME 1 PROJECT MANUAL Division 0 Contracting Requirements Division 1 General Requirements Divisions 2-14 Building Technical Specification Divisions 21-23 Mechanical Technical Specification Divisions 26-28 Electrical Technical Specification Divisions 31-33 Site Technical Specification VOLUME 2 PROJECT DRAWINGS Division G General Drawings Division C Civil Drawings Division L Landscape Drawings Division A Architectural Drawings Division E Electrical Drawings Division M Mechanical Drawings Division P Plumbing Drawings VOLUME 1 PROJECT MANUAL Unit Number Description DIVISION 0 BIDDING AND CONTRACTING REQUIREMENTS Section 00 01 01 Introduction 00 01 10 Table of Contents 00 11 16 Invitation to Bidders 00 21 13 Instructions to the Bidders Substitution Request Form 00 41 00 Bid Form First-Tier Subcontractor Disclosure Form 00 50 00 Agreement Forms State of Oregon Public Improvement Agreement 00 61 00 Bond Forms Bid Bond Form Performance and Payment Bond Forms 00 72 00 General Conditions State of Oregon General Conditions for Public Improvement Contracts 00 73 43 Prevailing Wage Rates 00 91 13 Addendum DIVISION 1 GENERAL REQUIREMENTS Section 01 11 00 Summary of Work 01 21 13 Unit Cost Work Items 01 23 00 Alternative Bid Items 00 29 00 Payment Procedures June 9, 2016 Reynolds School District 7 00 01 10-1 HB Lee Middle School HVAC Upgrades SECTION 00 01 10 TABLE OF CONTENTS 01 31 00 Coordination 01 33 00 Submittals 01 40 00 Quality
    [Show full text]
  • DOWNLOAD the Labmart 2013 Catalog
    Alconox Detergents 24 Bags 10 Balances 11-17, 70 Welcome To Baths 35 Beakers 3, 60 About Us Benchtop Covers 23 For more than 160 years, The LabMart® has offered NEW and INNOVATIVE Biotechnology 68 products at affordable prices! We look forward to suppling you with all Bottles 3, 9, 53-57 your lab needs in the future & thank you for your past patronage. Brushes 22 Buffers, pH 51 Burners 38 Contact Us Carts 22 Call: 800-684-1234 Fax: 908-561-3002 Calculators 39 Online: www.labmart.com E-mail: [email protected] Centrifuges & Accessories 18-21 Mail: J&H Berge/The LabMart® Cleaning 22-24, 33 4111 South Clinton Avenue PO Box 310 Corning Glassware Sale 3-7 South Plainfield, NJ 07080 Cryoware 25-26 Cylinders 4, 55 This Edition Desiccator 27 This edition offers our best products at the best prices. WE WENT GREEN and cut Dishes, Glass / Petri 7, 69 back on resources to reduce our carbon footprint. We still have a full line catalog, Dispensers 44, 54 just contact us and will will be happy to send it to you. And of course, our online Disposal, Safety 8 catalog (www.labmart.com) lists every product and chemical we offer. If you don’t Electrophoresis 27 see it or can’t find it, call us. We can cross-reference any competitors’ product number Electrodes, pH 52 Filtration / Paper 28-30 or description and beat their price. Flasks 5-7, 69 Food Prep / Handling 59, 70-71 New and Free Stuff Funnels 60 We have packed this catalog with the latest and best products Gloves 31-34 produced by leading manufacturers.
    [Show full text]
  • Some Computer Organizations and Their Effectiveness Michael J Flynn
    Some Computer Organizations and Their Effectiveness Michael J Flynn IEEE Transactions on Computers. Vol. c-21, No.9, September 1972 Introduction Attempts to codify a computer have been from three points of view ! Automata Theoritic or microscopic ! Individual Problem Oriented ! Global or Statistical Microscopic View: ! Relationships are described exhaustively ! All parameters are considered irrespective of their importance in the problem Individual Poblem Oriented: ! Compare Computer Organizations based on their relative performances in a peculiar environment ! Such comparisons are limited because of their ad hoc nature Global or Statistical Comparisons: ! Made on basis of statistical tabulations of relative performances on various jobs or mixture of jobs Drawback: The analysis is of little consequence in the system as the base premise on which they were based has been changed Objective of this paper: To reexamine the principal interactions within a processor system so as to generate a more “macroscopic” view, yet without reference to a particular environment Limitations: 1. I/O problems are not treated as a limiting resource 2. No assessment of particular instruction set 3. In spite of the fact that either (1) or (2) will dominate the assessment we will use the notion of efficiency Classification: Forms of Computing Systems Stream : sequence of items (instructions or data) Based on the magnitude of interactions of the instructions and data streams, machines are classified as 1. SISD - Single Instruction, Single Data Stream 2. SIMD - Single Instruction, Multiple Data Stream 3. MISD - Multiple Instruction, Single Data Stream 4. MIMD - Multiple Instruction, Multiple Data Stream Let us formalize the stream view of Computing in order to obtain a better insight.
    [Show full text]
  • Intel Thread Building Blocks, Part III
    Intel Thread Building Blocks, Part III SPD course 2014-15 Massimo Coppola 12/05/2015 MCSN – M. Coppola – Strumenti di programmazione per sistemi paralleli e distribuiti 1 Parallel_do template< typename InputIterator, typename Body> void parallel_do( InputIterator first, InputIterator last, Body body [, task_group_context& group] ); • Parallel_do has two forms, both using the object- oriented syntax • Applies a function object body to a specified interval – The body can add additional tasks dynamically – Iterator is a standard C++ one, however • a purely serial input iterator is a bottleneck • It is better to use iterators over random-access data structures • Replaces the deprecated parallel_while MCSN – M. Coppola – Strumenti di programmazione per sistemi paralleli e distribuiti 2 Parallel_do Template< typename Container, typename Body> void parallel_do( Container c, Body body [, task_group_context& group] ); • Shorter equivalent for processing a whole container – iterators are provided by the Container type – equivalent to passing std::begin() and std:: end() with the other syntax MCSN – M. Coppola – Strumenti di programmazione per sistemi paralleli e distribuiti 3 Computing and adding items in a do • The body class need to compute on the template T type e.g. operator() – Body also needs a copy constructor and a destroyer B::operator()( T& item, parallel_do_feeder<T>& feeder ) const B::operator()( T& item ) const • Adding items depends on the signature of the Body operator() -- two possible signatures – First signature, with extra parameter, allows each item to call a feeder callback to add more items dinamically à e.g. allows dynamically bound parallel do, feedback, divide & conquer – Second signature means the do task set is static – You can’t define both! MCSN – M.
    [Show full text]
  • Grid Computing
    Grid computing This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (July 2010) This article needs attention from an expert on the subject. See the talk page for details. Consider associating this request with a WikiProject. (July 2010) Grid computing is a term referring to the combination of computer resources from multiple administrative domains to reach a common goal. The grid can be thought of as a distributed system with non-interactive workloads that involve a large number of files. What distinguishes grid computing from conventional high performance computing systems such as cluster computing is that grids tend to be more loosely coupled, heterogeneous, and geographically dispersed. Although a grid can be dedicated to a specialized application, it is more common that a single grid will be used for a variety of different purposes. Grids are often constructed with the aid of general-purpose grid software libraries known as middleware. Grid size can vary by a considerable amount. Grids are a form of distributed computing whereby a ―super virtual computer‖ is composed of many networked loosely coupled computers acting together to perform very large tasks. Furthermore, ―distributed‖ or ―grid‖ computing, in general, is a special type of parallel computing that relies on complete computers (with onboard CPUs, storage, power supplies, network interfaces, etc.) connected to a network (private, public or the Internet) by a conventional network interface, such as Ethernet. This is in contrast to the traditional notion of a supercomputer, which has many processors connected by a local high- speed computer bus.
    [Show full text]
  • Multithreading Contents
    Master Program (Laurea Magistrale) in Computer Science and Networking High Performance Computing Systems and Enabling Platforms Marco Vanneschi Multithreading Contents • Main features of explicit multithreading architectures • Relationships with ILP • Relationships with multiprocessors and multicores • Relationships with network processors • GPUs MCSN - M. Vanneschi: High Performance Computing Systems and Enabling Platforms 2 Basic principle • Concurrently execute instructions of different threads of control within a single pipelined processor • Notion of thread in this context: – NOT “software thread” as in a multithreaded OS, – Hardware-firmware supported thread: an independent execution sequence of a (general- purpose or specialized) processor: • A process • A compiler generated thread • A microinstruction execution sequence • A task scheduled to a processor core in a GPU architecture • Even an OS thread (e.g. POSIX) • In a multithreaded architecture, a thread is the unit of instruction scheduling for ILP – Neverthless, multithreading might be a powerful mechanism for multiprocessing too (i.e., parallelism at process level in multiprocessors architectures) • (Unfortunately, there is a lot of confusion around the word “thread”, which is used in several contexts often with very different meanings) MCSN - M. Vanneschi: High Performance Computing Systems and Enabling Platforms 3 Basic architecture • More independent program counters • Tagging mechanism (unique identifiers) to distinguish instructions of different threads within the pipeline • Efficient mechanisms for thread switching: very efficient context switching, from zero to very few clock cycles • Multiple register sets Request DM – (not always statically allocated) IM Queue Interleave the execution of instructions of different threads in the same pipeline. IU Pipelined EU Request FIXED RG ICIC Queue FIXED RG Try “to fill” the ICIC FIXED RG latencies as much as FLOAT RG FLOAT RG possible.
    [Show full text]