DOCSLIB.ORG

CS 698L: Intel Threading Building Blocks Swarnendu Biswas

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CS 698L: Intel Threading Building Blocks Swarnendu Biswas CS 698L: Intel Threading Building Blocks Swarnendu Biswas Semester 2019-2020-I CSE, IIT Kanpur Content influenced by many excellent references, see References slide for acknowledgements. Approaches to Parallelism • New languages • For example, Cilk, X10, Chapel • New concepts, but difficult to get widespread acceptance • Language extensions/pragmas • For example, OpenMP • Easy to extend, but requires special compiler or preprocessor support • Library • For example, C++ STL, Intel TBB, and MPI • Works with existing environments, usually no new compiler is needed CS 698L Swarnendu Biswas What is Intel TBB? • A library to help leverage multicore performance using standard C++ • Does not require programmers to be an expert • Writing a correct and scalable parallel loop is not straightforward • Does not require support for new languages and compilers • Does not directly support vectorization • TBB was first available in 2006 • Current release is 2019 Update 8 • Open source and licensed versions available CS 698L Swarnendu Biswas What is Intel TBB? • TBB works at the abstraction of tasks instead of low-level threads • Specify tasks that can run concurrently instead of threads • Specify work (i.e., tasks), instead of focusing on workers (i.e., threads) • Raw threads are like assembly language of parallel programming • Maps tasks onto physical threads, efficiently using cache and balancing load • Full support for nested parallelism CS 698L Swarnendu Biswas Advantages with Intel TBB • Promotes scalable data-parallel programming • Data parallelism is more scalable than functional parallelism • Functional blocks are usually limited while data parallelism scales with more processors • Not tailored for I/O-bound or real-time processing • Compatible with other threading packages and is portable • Can be used in concert with native threads and OpenMP • Relies on generic programming (e.g., C++ STL) CS 698L Swarnendu Biswas Key Features of Intel TBB Generic Parallel algorithms parallel_for, parallel_for_each, Concurrent containers parallel_reduce, parallel_scan, concurrent_hash_map parallel_do, pipeline, parallel_pipeline, concurrent_unordered_map parallel_sort, parallel_invoke concurrent_queue concurrent_bounded_queue Task scheduler concurrent_vector task_group, structured_task_group, task, task_scheduler_init Synchronization primitives Utilities atomic operations, condition_variable tick_count various flavors of mutexes tbb_thread Memory allocators tbb_allocator, cache_aligned_allocator, scalable_allocator, zero_allocator CS 698L Swarnendu Biswas Task-Based Programming • Challenges with threads: oversubscription or undersubscription, scheduling policy, load imbalance, portability • For example, mapping of logical to physical threads is crucial • Mapping also depends on whether computation waits on external devices • Non-trivial impact of time slicing with context switches, cache cooling effects, and lock preemption • Time slicing allows more logical threads than physical threads CS 698L Swarnendu Biswas Task-Based Programming with Intel TBB • Intel TBB parallel algorithms map tasks onto threads automatically • Task scheduler manages the thread pool • Oversubscription and undersubscription of core resources is prevented by task-stealing technique of TBB scheduler • Tasks are lighter-weight than threads CS 698L Swarnendu Biswas An Example: Hello World #include <iostream> int main() { #include <tbb/tbb.h> task_group tg; using namespace std; tg.run(HelloWorld("1")); using namespace tbb; tg.run(HelloWorld("2")); class HelloWorld { const char* id; tg.wait(); public: return EXIT_SUCCESS; HelloWorld(const char* s) : id(s) {} } void operator()() const { cout << "Hello from task " << id << "\n"; } }; CS 698L Swarnendu Biswas An Example: Hello World #include <iostream> int main() { #include <tbb/tbb.h> task_group tg; using namespace std; tg.run(HelloWorld("1")); using namespace tbb; tg.run(HelloWorld("2")); class HelloWorld { const char* id; tg.wait(); public: return EXIT_SUCCESS; HelloWorld(const char* s) : id(s) {} } void operator()() const { cout << "Hello from task " << id << "\n"; } }; CS 698L Swarnendu Biswas Another Example: Parallel loop #include <chrono> void parallel_incr(float* a) { #include <iostream> tbb::parallel_for(static_cast<size_t>(0), #include <tbb/parallel_for.h> static_cast<size_t>(N), #include <tbb/tbb.h> [&](size_t i) { a[i] += 10; using namespace std; }); using namespace std::chrono; using HRTimer = high_resolution_clock::time_point; } #define N (1 << 26) void seq_incr(float* a) { for (int i = 0; i < N; i++) { a[i] += 10; } } CS 698L Swarnendu Biswas Another Example: Parallel loop int main() { start = high_resolution_clock::now(); float* a = new float[N]; parallel_incr(a); for (int i = 0; i < N; i++) { end = high_resolution_clock::now(); a[i] = static_cast<float>(i); duration = duration_cast<microseconds> (end - start).count(); } cout << "Intel TBB Parallel increment in " << duration << " us\n"; HRTimer start = high_resolution_clock: :now(); return EXIT_SUCCESS; seq_incr(a); } HRTimer end = high_resolution_clock::n ow(); auto duration = duration_cast<microsec onds>(end - start).count(); cout << "Sequential increment in " << duration << " us\n"; CS 698L Swarnendu Biswas Another Example: Parallel loop int main() { start = high_resolution_clock::now(); float* a = new float[N]; parallel_incr(a); for (int i = 0; i < N; i++) { end = high_resolution_clock::now(); a[i] = static_cast<float>(i); duration = duration_cast<microseconds> (end - start).count(); } cout << "Intel TBB Parallel increment in " << duration << " us\n"; HRTimer start = high_resolution_clock: :now(); return EXIT_SUCCESS; seq_incr(a); } HRTimer end = high_resolution_clock::n ow(); auto duration = duration_cast<microsec onds>(end - start).count(); cout << "Sequential increment in " << duration << " us\n"; CS 698L Swarnendu Biswas Initializing the TBB Library #include <tbb/task_scheduler_init.h> • Control when the task scheduler is constructed using namespace tbb; and destroyed. • Specify the number of int main( ) { threads used by the task task_scheduler_init init; scheduler. ... • Specify the stack size for return 0; worker threads } Not required in recent versions, >= TBB 2.2 CS 698L Swarnendu Biswas Thinking Parallel • Decomposition • Decompose the problem into concurrent tasks • Scaling • Identify concurrent tasks to keep processors busy • Threads • Map tasks to threads • Correctness • Ensure correct synchronization to shared resources CS 698L Swarnendu Biswas How to Decompose? Data parallelism Task parallelism CS 698L Swarnendu Biswas How to Decompose? • Distinguishing just between data and task parallelism may not be perfect • Imagine TAs grading questions of varied difficulty • Might need hybrid parallelism or pipelining or work stealing CS 698L Swarnendu Biswas OpenMP vs Intel TBB OpenMP Intel TBB • Language extension consisting of • Library for task-based pragmas, routines, and programming environment variables • Supports C, C++, and Fortran • Supports C++ with generics • User can control scheduling • Automated divide-and-conquer policies approach to scheduling, with work stealing • OpenMP limited to specified • Generic programming is flexible types (for e.g., reduction) with types CS 698L Swarnendu Biswas Generic Parallel Algorithms CS 698L Swarnendu Biswas Generic Programming • Best known example is C++ Standard Template Library (STL) • Enables distribution of useful high-quality algorithms and data structures • Write best possible algorithm with fewest constraints (for e.g., std::sort) • Instantiate algorithm to specific situation • C++ template instantiation, partial specialization, and inlining make resulting code efficient • STL is not generally thread-safe CS 698L Swarnendu Biswas Generic Programming Example • The compiler creates the needed versions T must define a copy constructor and a destructor template <typename T> T max (T x, T y) { if (x < y) return y; return x; } T must define operator < int main() { int i = max(20,5); double f = max(2.5, 5.2); MyClass m = max(MyClass(“foo”), MyClass(“bar”)); return 0; } CS 698L Swarnendu Biswas Intel Threading Building Blocks Patterns • High-level parallel and scalable patterns • parallel_for: load-balanced parallel execution of independent loop iterations • parallel_reduce: load-balanced parallel execution of independent loop iterations that perform reduction • parallel_scan: template function that computes parallel prefix • parallel_while: load-balanced parallel execution of independent loop iterations with unknown or dynamically changing bounds • pipeline: data-flow pipeline pattern • parallel_sort: parallel sort CS 698L Swarnendu Biswas Loop Parallelization • parallel_for and parallel_reduce • Load-balanced, parallel execution of a fixed number of independent loop iterations • parallel_scan • A template function that computes a prefix computation (also known as a scan) in parallel • y[i] = y[i-1] op x[i] CS 698L Swarnendu Biswas TBB parallel_for void SerialApplyFoo(float a[], size_t n) { for (size_t i=0; i<n; ++i) foo(a[i]); } CS 698L Swarnendu Biswas Class Definition for TBB parallel_for #include “tbb/blocked_range.h” class ApplyFoo { float *const m_a; Task public: void operator()(const blocked_range<size_t>& r) const { Body object float *a = m_a; for (size_t i=r.begin(); i!=r.end( ); ++i) foo(a[i]); } ApplyFoo(float a[]) : m_a(a) {} }; CS 698L Swarnendu Biswas TBB parallel_for #include “tbb/parallel_for.h” void ParallelApplyFoo(float a[], size_t n) { parallel_for(blocked_range<size_t>(0,n,grainSize),
Load more

Recommended publications
  • Heterogeneous Task Scheduling for Accelerated Openmp
    Heterogeneous Task Scheduling for Accelerated OpenMP ? ? Thomas R. W. Scogland Barry Rountree† Wu-chun Feng Bronis R. de Supinski† ? Department of Computer Science, Virginia Tech, Blacksburg, VA 24060 USA † Center for Applied Scientific Computing, Lawrence Livermore National Laboratory, Livermore, CA 94551 USA [email protected] [email protected] [email protected] [email protected] Abstract—Heterogeneous systems with CPUs and computa- currently requires a programmer either to program in at tional accelerators such as GPUs, FPGAs or the upcoming least two different parallel programming models, or to use Intel MIC are becoming mainstream. In these systems, peak one of the two that support both GPUs and CPUs. Multiple performance includes the performance of not just the CPUs but also all available accelerators. In spite of this fact, the models however require code replication, and maintaining majority of programming models for heterogeneous computing two completely distinct implementations of a computational focus on only one of these. With the development of Accelerated kernel is a difficult and error-prone proposition. That leaves OpenMP for GPUs, both from PGI and Cray, we have a clear us with using either OpenCL or accelerated OpenMP to path to extend traditional OpenMP applications incrementally complete the task. to use GPUs. The extensions are geared toward switching from CPU parallelism to GPU parallelism. However they OpenCL’s greatest strength lies in its broad hardware do not preserve the former while adding the latter. Thus support. In a way, though, that is also its greatest weak- computational potential is wasted since either the CPU cores ness. To enable one to program this disparate hardware or the GPU cores are left idle.
    [Show full text]
  • Parallel Programming
    Parallel Programming Libraries and implementations Outline • MPI – distributed memory de-facto standard • Using MPI • OpenMP – shared memory de-facto standard • Using OpenMP • CUDA – GPGPU de-facto standard • Using CUDA • Others • Hybrid programming • Xeon Phi Programming • SHMEM • PGAS MPI Library Distributed, message-passing programming Message-passing concepts Explicit Parallelism • In message-passing all the parallelism is explicit • The program includes specific instructions for each communication • What to send or receive • When to send or receive • Synchronisation • It is up to the developer to design the parallel decomposition and implement it • How will you divide up the problem? • When will you need to communicate between processes? Message Passing Interface (MPI) • MPI is a portable library used for writing parallel programs using the message passing model • You can expect MPI to be available on any HPC platform you use • Based on a number of processes running independently in parallel • HPC resource provides a command to launch multiple processes simultaneously (e.g. mpiexec, aprun) • There are a number of different implementations but all should support the MPI 2 standard • As with different compilers, there will be variations between implementations but all the features specified in the standard should work. • Examples: MPICH2, OpenMPI Point-to-point communications • A message sent by one process and received by another • Both processes are actively involved in the communication – not necessarily at the same time • Wide variety of semantics provided: • Blocking vs. non-blocking • Ready vs. synchronous vs. buffered • Tags, communicators, wild-cards • Built-in and custom data-types • Can be used to implement any communication pattern • Collective operations, if applicable, can be more efficient Collective communications • A communication that involves all processes • “all” within a communicator, i.e.
    [Show full text]
  • Openmp API 5.1 Specification
    OpenMP Application Programming Interface Version 5.1 November 2020 Copyright c 1997-2020 OpenMP Architecture Review Board. Permission to copy without fee all or part of this material is granted, provided the OpenMP Architecture Review Board copyright notice and the title of this document appear. Notice is given that copying is by permission of the OpenMP Architecture Review Board. This page intentionally left blank in published version. Contents 1 Overview of the OpenMP API1 1.1 Scope . .1 1.2 Glossary . .2 1.2.1 Threading Concepts . .2 1.2.2 OpenMP Language Terminology . .2 1.2.3 Loop Terminology . .9 1.2.4 Synchronization Terminology . 10 1.2.5 Tasking Terminology . 12 1.2.6 Data Terminology . 14 1.2.7 Implementation Terminology . 18 1.2.8 Tool Terminology . 19 1.3 Execution Model . 22 1.4 Memory Model . 25 1.4.1 Structure of the OpenMP Memory Model . 25 1.4.2 Device Data Environments . 26 1.4.3 Memory Management . 27 1.4.4 The Flush Operation . 27 1.4.5 Flush Synchronization and Happens Before .................. 29 1.4.6 OpenMP Memory Consistency . 30 1.5 Tool Interfaces . 31 1.5.1 OMPT . 32 1.5.2 OMPD . 32 1.6 OpenMP Compliance . 33 1.7 Normative References . 33 1.8 Organization of this Document . 35 i 2 Directives 37 2.1 Directive Format . 38 2.1.1 Fixed Source Form Directives . 43 2.1.2 Free Source Form Directives . 44 2.1.3 Stand-Alone Directives . 45 2.1.4 Array Shaping . 45 2.1.5 Array Sections .
    [Show full text]
  • Openmp Made Easy with INTEL® ADVISOR
    OpenMP made easy with INTEL® ADVISOR Zakhar Matveev, PhD, Intel CVCG, November 2018, SC’18 OpenMP booth Why do we care? Ai Bi Ai Bi Ai Bi Ai Bi Vector + Processing Ci Ci Ci Ci VL Motivation (instead of Agenda) • Starting from 4.x, OpenMP introduces support for both levels of parallelism: • Multi-Core (think of “pragma/directive omp parallel for”) • SIMD (think of “pragma/directive omp simd”) • 2 pillars of OpenMP SIMD programming model • Hardware with Intel ® AVX-512 support gives you theoretically 8x speed- up over SSE baseline (less or even more in practice) • Intel® Advisor is here to assist you in: • Enabling SIMD parallelism with OpenMP (if not yet) • Improving performance of already vectorized OpenMP SIMD code • And will also help to optimize for Memory Sub-system (Advisor Roofline) 3 Don’t use a single Vector lane! Un-vectorized and un-threaded software will under perform 4 Permission to Design for All Lanes Threading and Vectorization needed to fully utilize modern hardware 5 A Vector parallelism in x86 AVX-512VL AVX-512BW B AVX-512DQ AVX-512CD AVX-512F C AVX2 AVX2 AVX AVX AVX SSE SSE SSE SSE Intel® microarchitecture code name … NHM SNB HSW SKL 6 (theoretically) 8x more SIMD FLOP/S compared to your (–O2) optimized baseline x - Significant leap to 512-bit SIMD support for processors - Intel® Compilers and Intel® Math Kernel Library include AVX-512 support x - Strong compatibility with AVX - Added EVEX prefix enables additional x functionality Don’t leave it on the table! 7 Two level parallelism decomposition with OpenMP: image processing example B #pragma omp parallel for for (int y = 0; y < ImageHeight; ++y){ #pragma omp simd C for (int x = 0; x < ImageWidth; ++x){ count[y][x] = mandel(in_vals[y][x]); } } 8 Two level parallelism decomposition with OpenMP: fluid dynamics processing example B #pragma omp parallel for for (int i = 0; i < X_Dim; ++i){ #pragma omp simd C for (int m = 0; x < n_velocities; ++m){ next_i = f(i, velocities(m)); X[i] = next_i; } } 9 Key components of Intel® Advisor What’s new in “2019” release Step 1.
    [Show full text]
  • Introduction to Openmp Paul Edmon ITC Research Computing Associate
    Introduction to OpenMP Paul Edmon ITC Research Computing Associate FAS Research Computing Overview • Threaded Parallelism • OpenMP Basics • OpenMP Programming • Benchmarking FAS Research Computing Threaded Parallelism • Shared Memory • Single Node • Non-uniform Memory Access (NUMA) • One thread per core FAS Research Computing Threaded Languages • PThreads • Python • Perl • OpenCL/CUDA • OpenACC • OpenMP FAS Research Computing OpenMP Basics FAS Research Computing What is OpenMP? • OpenMP (Open Multi-Processing) – Application Program Interface (API) – Governed by OpenMP Architecture Review Board • OpenMP provides a portable, scalable model for developers of shared memory parallel applications • The API supports C/C++ and Fortran on a wide variety of architectures FAS Research Computing Goals of OpenMP • Standardization – Provide a standard among a variety shared memory architectures / platforms – Jointly defined and endorsed by a group of major computer hardware and software vendors • Lean and Mean – Establish a simple and limited set of directives for programming shared memory machines – Significant parallelism can be implemented by just a few directives • Ease of Use – Provide the capability to incrementally parallelize a serial program • Portability – Specified for C/C++ and Fortran – Most majors platforms have been implemented including Unix/Linux and Windows – Implemented for all major compilers FAS Research Computing OpenMP Programming Model Shared Memory Model: OpenMP is designed for multi-processor/core, shared memory machines Thread Based Parallelism: OpenMP programs accomplish parallelism exclusively through the use of threads Explicit Parallelism: OpenMP provides explicit (not automatic) parallelism, offering the programmer full control over parallelization Compiler Directive Based: Parallelism is specified through the use of compiler directives embedded in the C/C++ or Fortran code I/O: OpenMP specifies nothing about parallel I/O.
    [Show full text]
  • Parallel Programming with Openmp
    Parallel Programming with OpenMP OpenMP Parallel Programming Introduction: OpenMP Programming Model Thread-based parallelism utilized on shared-memory platforms Parallelization is either explicit, where programmer has full control over parallelization or through using compiler directives, existing in the source code. Thread is a process of a code is being executed. A thread of execution is the smallest unit of processing. Multiple threads can exist within the same process and share resources such as memory OpenMP Parallel Programming Introduction: OpenMP Programming Model Master thread is a single thread that runs sequentially; parallel execution occurs inside parallel regions and between two parallel regions, only the master thread executes the code. This is called the fork-join model: OpenMP Parallel Programming OpenMP Parallel Computing Hardware Shared memory allows immediate access to all data from all processors without explicit communication. Shared memory: multiple cpus are attached to the BUS all processors share the same primary memory the same memory address on different CPU's refer to the same memory location CPU-to-memory connection becomes a bottleneck: shared memory computers cannot scale very well OpenMP Parallel Programming OpenMP versus MPI OpenMP (Open Multi-Processing): easy to use; loop-level parallelism non-loop-level parallelism is more difficult limited to shared memory computers cannot handle very large problems An alternative is MPI (Message Passing Interface): require low-level programming; more difficult programming
    [Show full text]
  • A Fast Concurrent and Resizable Robin Hood Hash Table Endrias
    A Fast Concurrent and Resizable Robin Hood Hash Table by Endrias Kahssay Submitted to the Department of Electrical Engineering and Computer Science in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY February 2021 © Massachusetts Institute of Technology 2021. All rights reserved. Author................................................................ Department of Electrical Engineering and Computer Science Jan 29, 2021 Certified by. Julian Shun Assistant Professor Thesis Supervisor Accepted by . Katrina LaCurts Chair, Master of Engineering Thesis Committee 2 A Fast Concurrent and Resizable Robin Hood Hash Table by Endrias Kahssay Submitted to the Department of Electrical Engineering and Computer Science on Jan 29, 2021, in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science Abstract Concurrent hash tables are among the most important primitives in concurrent pro- gramming and have been extensively studied in the literature. Robin Hood hashing is a variant of linear probing that moves around keys to reduce probe distances. It has been used to develop state of the art serial hash tables. However, there is only one existing previous work on a concurrent Robin Hood table. The difficulty in making Robin Hood concurrent lies in the potential for large memory reorganization by the different table operations. This thesis presents Bolt, a concurrent resizable Robin Hood hash table engineered for high performance. Bolt treads an intricate balance between an atomic fast path and a locking slow path to facilitate concurrency. It uses a novel scheme to interleave the two without compromising correctness in the concur- rent setting.
    [Show full text]
  • Intel Threading Building Blocks
    Praise for Intel Threading Building Blocks “The Age of Serial Computing is over. With the advent of multi-core processors, parallel- computing technology that was once relegated to universities and research labs is now emerging as mainstream. Intel Threading Building Blocks updates and greatly expands the ‘work-stealing’ technology pioneered by the MIT Cilk system of 15 years ago, providing a modern industrial-strength C++ library for concurrent programming. “Not only does this book offer an excellent introduction to the library, it furnishes novices and experts alike with a clear and accessible discussion of the complexities of concurrency.” — Charles E. Leiserson, MIT Computer Science and Artificial Intelligence Laboratory “We used to say make it right, then make it fast. We can’t do that anymore. TBB lets us design for correctness and speed up front for Maya. This book shows you how to extract the most benefit from using TBB in your code.” — Martin Watt, Senior Software Engineer, Autodesk “TBB promises to change how parallel programming is done in C++. This book will be extremely useful to any C++ programmer. With this book, James achieves two important goals: • Presents an excellent introduction to parallel programming, illustrating the most com- mon parallel programming patterns and the forces governing their use. • Documents the Threading Building Blocks C++ library—a library that provides generic algorithms for these patterns. “TBB incorporates many of the best ideas that researchers in object-oriented parallel computing developed in the last two decades.” — Marc Snir, Head of the Computer Science Department, University of Illinois at Urbana-Champaign “This book was my first introduction to Intel Threading Building Blocks.
    [Show full text]
  • Unified Parallel C for GPU Clusters: Language Extensions and Compiler Implementation
    Unified Parallel C for GPU Clusters: Language Extensions and Compiler Implementation Li Chen1, Lei Liu1, Shenglin Tang1, Lei Huang2, Zheng Jing1, Shixiong Xu1, Dingfei Zhang1, Baojiang Shou1 1 Key Laboratory of Computer System and Architecture, Institute of Computing Technology, Chinese Academy of Sciences, China {lchen,liulei2007,tangshenglin,jingzheng,xushixiong, zhangdingfei, shoubaojiang}@ict.ac.cn; 2 Department of Computer Science, University of Houston; Houston, TX, USA [email protected] 5 Abstract. Unified Parallel C (UPC), a parallel extension to ANSI C, is designed for high performance computing on large-scale parallel machines. With General-purpose graphics processing units (GPUs) becoming an increasingly important high performance computing platform, we propose new language extensions to UPC to take advantage of GPU clusters. We extend UPC with hierarchical data distribution, revise the execution model of UPC to mix SPMD with fork-join execution model, and modify the semantics of upc_forall to reflect the data-thread affinity on a thread hierarchy. We implement the compiling system, including affinity-aware loop tiling, GPU code generation, and several memory optimizations targeting NVIDIA CUDA. We also put forward unified data management for each UPC thread to optimize data transfer and memory layout for separate memory modules of CPUs and GPUs. The experimental results show that the UPC extension has better programmability than the mixed MPI/CUDA approach. We also demonstrate that the integrated compile-time and runtime optimization is effective to achieve good performance on GPU clusters. 1 Introduction Following closely behind the industry-wide move from uniprocessor to multi-core and many-core systems, HPC computing platforms are undergoing another major change: from homogeneous to heterogeneous platform.
    [Show full text]
  • Lecture 12: Introduction to Openmp (Part 1)
    Lecture 12: Introduction to OpenMP (Part 1) 1 What is OpenMP Open specifications for Multi Processing Long version: Open specifications for MultiProcessing via collaborative work between interested parties from the hardware and software industry, government and academia. • An Application Program Interface (API) that is used to explicitly direct multi-threaded, shared memory parallelism. • API components: – Compiler directives – Runtime library routines – Environment variables • Portability – API is specified for C/C++ and Fortran – Implementations on almost all platforms including Unix/Linux and Windows • Standardization – Jointly defined and endorsed by major computer hardware and software vendors – Possibility to become ANSI standard 2 Brief History of OpenMP • In 1991, Parallel Computing Forum (PCF) group invented a set of directives for specifying loop parallelism in Fortran programs. • X3H5, an ANSI subcommittee developed an ANSI standard based on PCF. • In 1997, the first version of OpenMP for Fortran was defined by OpenMP Architecture Review Board. • Binding for C/C++ was introduced later. • Version 3.1 is available since 2011. 3 4 Thread • A process is an instance of a computer program that is being executed. It contains the program code and its current activity. • A thread of execution is the smallest unit of processing that can be scheduled by an operating system. • Differences between threads and processes: – A thread is contained inside a process. Multiple threads can exist within the same process and share resources such as memory. The threads of a process share the latter’s instructions (code) and its context (values that its variables reference at any given moment). – Different processes do not share these resources.
    [Show full text]
  • Programming Your GPU with Openmp*
    Programming Your GPU with OpenMP* Simon McIntosh-Smith, Matt Martineau, Andrei Poenaru, Patrick Atkinson University of Bristol [email protected] 1 * The name “OpenMP” is the property of the OpenMP Architecture Review Board. 1 Preliminaries: Part 2 • Our plan for the day .. Active learning! – We will mix short lectures with short exercises. – You will use your laptop to connect to a multiprocessor server. • Please follow these simple rules – Do the exercises that we assign and then change things around and experiment. – EmBrace active learning! –Don’t cheat: Do Not look at the solutions before you complete an exercise … even if you get really frustrated. 2 • Collaboration between GW4 Alliance (universities of Bristol, Bath, Cardiff, Exeter), the UK Met Office, Cray, and Arm • ~£3 million, funded by EPSRC • Expected to be the first large-scale, Arm-based production supercomputer • 10,000+ Armv8 cores • Also contains some Intel Xeon Phi (KNL), Intel Xeon (Broadwell), and NVIDIA P100 GPUs • Cray compilers provide the OpenMP implementation for GPU offloading 3 Plan Module Concepts Exercises OpenMP overview • OpenMP recap • None … we’ll use demo • Hardcore jargon of OpenMP mode so we can move fast The device model in • Intro to the Target directive • Vadd program OpenMP with default data movement Understanding • Intro to nvprof • nvprof ./vadd execution Working with the • CPU and GPU execution • Vadd with combined target directive models and the fundamental directive using nvprof to combined directive understand execution Basic memory •
    [Show full text]
  • 16 Concurrent Hash Tables: Fast and General(?)!
    Concurrent Hash Tables: Fast and General(?)! TOBIAS MAIER and PETER SANDERS, Karlsruhe Institute of Technology, Germany ROMAN DEMENTIEV, Intel Deutschland GmbH, Germany Concurrent hash tables are one of the most important concurrent data structures, which are used in numer- ous applications. For some applications, it is common that hash table accesses dominate the execution time. To efficiently solve these problems in parallel, we need implementations that achieve speedups inhighly concurrent scenarios. Unfortunately, currently available concurrent hashing libraries are far away from this requirement, in particular, when adaptively sized tables are necessary or contention on some elements occurs. Our starting point for better performing data structures is a fast and simple lock-free concurrent hash table based on linear probing that is, however, limited to word-sized key-value types and does not support 16 dynamic size adaptation. We explain how to lift these limitations in a provably scalable way and demonstrate that dynamic growing has a performance overhead comparable to the same generalization in sequential hash tables. We perform extensive experiments comparing the performance of our implementations with six of the most widely used concurrent hash tables. Ours are considerably faster than the best algorithms with similar restrictions and an order of magnitude faster than the best more general tables. In some extreme cases, the difference even approaches four orders of magnitude. All our implementations discussed in this publication
    [Show full text]