DOCSLIB.ORG

Investigating the Potential of a GPU-Based Math Library

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Investigating the Potential of a GPU-Based Math Library Investigating the Potential of a GPU-based Math Library by Daniel Riley Fay B.S., University of Illinois, 2004 A thesis submitted to the Faculty of the Graduate School of the University of Colorado in partial fulfillment of the requirements for the degree of Master of Science Department of Electrical and Computer Engineering 2007 This thesis entitled: Investigating the Potential of a GPU-based Math Library written by Daniel Riley Fay has been approved for the Department of Electrical and Computer Engineering Professor Daniel A. Connors Professor Manish Vachharajani Professor Vince Heuring Date The final copy of this thesis has been examined by the signatories, and we find that both the content and the form meet acceptable presentation standards of scholarly work in the above mentioned discipline. iii Riley Fay, Daniel (M.S., Computer Engineering) Investigating the Potential of a GPU-based Math Library Thesis directed by Professor Daniel A. Connors In the last few years, the Graphics Processing Unit (GPU) has evolved from being a graphics-specific integrated circuit into a high performance programmable vec- tor/stream processor. Contemporary GPUs provide a compelling platform for running compute-intensive applications. In addition to tens of gigabytes per second of memory bandwidth, they also possess vast computation resources capable of achieving hun- dreds of giga-FLOPs of single precision floating-point computation power. Moreover, the consumer-oriented focus of contemporary GPUs means that even the highest end graphics cards cost well under a thousand dollars. Developments on the software side have also made GPU systems far more accessible for general-purpose use: new program- ming languages reduce the need for GPU programmers to understand esoteric graphics concepts, and high speed interconnect technologies improve CPU-GPU communication. Developing a high performance math library will help programmers make full use of increasingly-powerful GPUs as well as enabling the study of using GPUs for general purpose applications. Math functions are a critical part of many high performance applications, and their use consumes a large percentage of many programs’ CPU times. In order for a GPU-based math library to be useful, it must provide accurate results. Similarly, it must show a performance and/or power consumption advantage over a CPU-based math library. This thesis investigates the potential of porting Apple, Inc.’s vForce math library to four different GPUs found in current Apple computers. Using this hardware, the thesis investigates whether current GPU technology can be gainfully employed to run a high performance math library on the GPU. The thesis investigates the potential of a iv GPU-based math library using three metrics: accuracy, performance, and power/energy consumption. These three metrics are used to study the GPU-ported math library as it runs on the four GPUs. Comparisons are also made between the four different GPUs tested against the CPU version of vForce. v Contents Chapter 1 Introduction 1 2 General Purpose GPU Computing (GPGPU) 5 2.1 Characteristics of GPGPU Programs . 5 2.2 Where GPGPU Computing is Today . 8 2.3 GPGPU Numeric Considerations . 10 3 Background on GPUs 18 3.1 From Framebuffer to Fast Vector Machine: A Brief History of GPUs . 18 3.1.1 A History of the Hardware . 19 3.1.2 A History of the Software . 20 3.2 Assessment of Current GPU Technology . 21 3.3 The Future of GPUs . 25 4 Experimental Setup 27 4.1 Writing a GPGPU Math Library . 27 4.1.1 Algorithms Used . 27 4.1.2 The OpenGL Shading Language (GLSL) . 28 4.1.3 Porting the vForce Functions to Shader Programs . 31 4.2 Test Setup . 35 4.3 Testing a GPGPU Math Library . 43 vi 5 Experimental Results 49 5.1 Accuracy Results . 49 5.2 Performance Results . 54 5.3 Power/Energy Results . 66 5.4 Bandwidth Results . 70 6 Summary and conclusion 71 6.1 Summary of Results . 72 6.2 Current Suitability of a GPGPU Math Library . 74 6.3 Improving GPU Accuracy . 74 6.4 Future Suitability of a GPGPU-based Math Library . 75 Bibliography 78 Appendix A Cephes Math Library Code for sinf 83 B Detailed Accuracy Results 91 vii Tables Table 1.1 Different GPU interconnections. 3 4.1 System configurations tested. 36 4.2 Capabilities of the CPUs and GPUs. 37 B.1 Accuracy of built-in GLSL functions, NVIDIA 7300GT. 92 B.2 Accuracy of built-in GLSL functions, ATi x1600. 92 B.3 Accuracy of built-in GLSL functions, NVIDIA Quadro FX 4500. 93 B.4 Accuracy of ported vForce functions, ATi x1600. 94 B.5 Accuracy of ported vForce functions, NVIDIA Quadro FX 4500. 94 B.6 Accuracy of ported vForce functions, NVIDIA 7300GT. 95 B.7 Accuracy of built-in GLSL functions, ATi x1900XTX. 95 B.8 Accuracy of ported vForce functions, ATi x1900XTX. 96 B.9 Accuracy of basic operators, ATi x1900XTX. 96 B.10 Accuracy of basic operators, NVIDIA 7300GT. 97 B.11 Accuracy of basic operators, NVIDIA Quadro FX 4500. 97 B.12 Accuracy of basic operators, ATi x1600. 97 viii Figures Figure 1.1 Comparison of peak compute capacity and peak memory bandwidth of the NVIDIA and ATi GPUs along with Intel CPUs and the CPUs used by Apple. 2 2.1 Data-flow for a GPGPU program. 7 2.2 The IEEE 754 floating point format. 11 2.3 The floating point number line. 11 2.4 Differences relative to libm’s sinf caused by changing the rounding mode of Cephes’ argument reduction. 14 2.5 Argument reduction code of the Cephes sinf. 15 2.6 Comparison of the Control Flow Graphs (CFGs) of the Apple Libm imple- mentation of sinf along with the Cephes Math Library implementation of sinf..................................... 16 3.1 An example of a GPU-containing computer system.. 23 3.2 The GPU pipeline. 24 4.1 The intrinsic-to-GLSL translation system. 34 4.2 Diagram of the NVIDIA G7x pixel shader core. 38 4.3 Diagram of the fragment shader of the NVIDIA G7x. 39 4.4 Diagram of dual-issue and co-issue. 40 ix 4.5 Diagram of the ATi R5xx pixel shader core. 41 4.6 Diagram of the fragment shader of the ATi R5xx. 42 4.7 The GPU test harness. 44 4.8 The Apple OpenGL software stack. 46 5.1 The accuracy differences between the tested GPUs for the basic opera- tions, the built-in GLSL functions, and the ported vForce functions. 50 5.2 Comparison of the accuracy between the different GPUs for the basic operations, the built-in GLSL functions, and the ported vForce functions. 51 5.3 Accuracy improvement of the ported vForce functions vs. the built-in GLSL functions. 52 5.4 A performance comparison of the built-in GLSL functions versus the ported vForce functions. 53 5.5 A performance comparison of different texture sizes for the NVIDIA GPUs. 55 5.6 A performance comparison of different texture sizes for the ATi GPUs. 56 5.7 A performance comparison of the ported vForce functions. 58 5.8 A performance comparison of vForce running on different processors. 58 5.9 Speedups gained from using the vec4 data type as opposed to the float on all of the ported vForce functions. 60 5.10 Speedups gained from using the vec4 data type as opposed to the float data type on the restricted subset of the functions. 61 5.11 A comparison of the different GPUs using the float data type. 62 5.12 A comparison of the different GPUs using the vec4 data type. 64 5.13 A comparison of the performance of the ported vForce functions using an all-normals dataset versus a mixed dataset. 65 5.14 A raw bandwidth comparison. 65 x 5.15 A comparison of the system-level power consumption of different GPU- based math functions vs. vForce. 67 5.16 A comparison of the performance of different built in GLSL functions vs. vForce. 68 5.17 A comparison of the energy consumption of different GPU-based math functions vs. vForce. 69 5.18 The CPU-GPU transfer bandwidth for differing PCI-E widths. 69 Chapter 1 Introduction Over the last several years, GPUs have increased in both computation capacity and in available memory bandwidth at a rate far faster than any mainstream CPU. The two graphs shown in Figure 1.1 show the progression in peak computation capacity, in gigaflops per second (GFLOP/s) along with the progression in peak memory bandwidth in gigabytes per second (GB/s) from January, 2000 through April, 2007. For the GPUs, a zero entry for the memory bandwidth and compute capacity represents the time period when the GPU vendors made only non-programmable GPUs. For the CPUs, Figure 1.1 shows the CPUs’ peak floating point computation capacities per socket. In the last few years, GPUs have been better able to turn increased transistor budgets into higher performance than have CPUs. Such performance scaling, partic- ularly the rapid increase in computation throughput, is due to GPUs’ relative silicon efficiency: GPUs do not have the complicated branch predictors or sophisticated logic for extracting instruction level parallelism (ILP) out of programs that modern CPUs do. Similarly, GPU memory bandwidth has also greatly increased due to GPUs’ special- purpose nature. On a video board, the GPU’s memory can clock much higher because it is not part of an expandable, multi-drop stub bus that must accommodate multiple gigabytes of memory. Another factor making the GPU more useful as a high performance adjunct to the main CPU is the rapid increase in the bandwidth of the CPU-GPU interconnection.
Load more

Recommended publications
  • GPU Architecture • Display Controller • Designing for Safety • Vision Processing
    i.MX 8 GRAPHICS ARCHITECTURE FTF-DES-N1940 RAFAL MALEWSKI HEAD OF GRAPHICS TECH ENGINEERING CENTER MAY 18, 2016 PUBLIC USE AGENDA • i.MX 8 Series Scalability • GPU Architecture • Display Controller • Designing for Safety • Vision Processing 1 PUBLIC USE #NXPFTF 1 PUBLIC USE #NXPFTF i.MX is… 2 PUBLIC USE #NXPFTF SoC Scalability = Investment Re-Use Replace the Chip a Increase capability. (Pin, Software, IP compatibility among parts) 3 PUBLIC USE #NXPFTF i.MX 8 Series GPU Cores • Dual Core GPU Up to 4 displays Accelerated ARM Cores • 16 Vec4 Shaders Vision Cortex-A53 | Cortex-A72 8 • Up to 128 GFLOPS • 64 execution units 8QuadMax 8 • Tessellation/Geometry total pixels Shaders Pin Compatibility Pin • Dual Core GPU Up to 4 displays Accelerated • 8 Vec4 Shaders Vision 4 • Up to 64 GFLOPS • 32 execution units 4 total pixels 8QuadPlus • Tessellation/Geometry Compatibility Software Shaders • Dual Core GPU Up to 4 displays Accelerated • 8 Vec4 Shaders Vision 4 • Up to 64 GFLOPS 4 • 32 execution units 8Quad • Tessellation/Geometry total pixels Shaders • Single Core GPU Up to 2 displays Accelerated • 8 Vec4 Shaders 2x 1080p total Vision • Up to 64 GFLOPS pixels Compatibility Pin 8 • 32 execution units 8Dual8Solo • Tessellation/Geometry Shaders • Single Core GPU Up to 2 displays Accelerated • 4 Vec4 Shaders 2x 1080p total Vision • Up to 32 GFLOPS pixels 4 • 16 execution units 8DualLite8Solo • Tessellation/Geometry Shaders 4 PUBLIC USE #NXPFTF i.MX 8 Series – The Doubles GPU Cores • Dual Core GPU Up to 4 displays Accelerated • 16 Vec4 Shaders Vision
    [Show full text]
  • Directx and GPU (Nvidia-Centric) History Why
    10/12/09 DirectX and GPU (Nvidia-centric) History DirectX 6 DirectX 7! ! DirectX 8! DirectX 9! DirectX 9.0c! Multitexturing! T&L ! SM 1.x! SM 2.0! SM 3.0! DirectX 5! Riva TNT GeForce 256 ! ! GeForce3! GeForceFX! GeForce 6! Riva 128! (NV4) (NV10) (NV20) Cg! (NV30) (NV40) XNA and Programmable Shaders DirectX 2! 1996! 1998! 1999! 2000! 2001! 2002! 2003! 2004! DirectX 10! Prof. Hsien-Hsin Sean Lee SM 4.0! GTX200 NVidia’s Unified Shader Model! Dualx1.4 billion GeForce 8 School of Electrical and Computer 3dfx’s response 3dfx demise ! Transistors first to Voodoo2 (G80) ~1.2GHz Engineering Voodoo chip GeForce 9! Georgia Institute of Technology 2006! 2008! GT 200 2009! ! GT 300! Adapted from David Kirk’s slide Why Programmable Shaders Evolution of Graphics Processing Units • Hardwired pipeline • Pre-GPU – Video controller – Produces limited effects – Dumb frame buffer – Effects look the same • First generation GPU – PCI bus – Gamers want unique look-n-feel – Rasterization done on GPU – Multi-texturing somewhat alleviates this, but not enough – ATI Rage, Nvidia TNT2, 3dfx Voodoo3 (‘96) • Second generation GPU – Less interoperable, less portable – AGP – Include T&L into GPU (D3D 7.0) • Programmable Shaders – Nvidia GeForce 256 (NV10), ATI Radeon 7500, S3 Savage3D (’98) – Vertex Shader • Third generation GPU – Programmable vertex and fragment shaders (D3D 8.0, SM1.0) – Pixel or Fragment Shader – Nvidia GeForce3, ATI Radeon 8500, Microsoft Xbox (’01) – Starting from DX 8.0 (assembly) • Fourth generation GPU – Programmable vertex and fragment shaders
    [Show full text]
  • MSI Afterburner V4.6.4
    MSI Afterburner v4.6.4 MSI Afterburner is ultimate graphics card utility, co-developed by MSI and RivaTuner teams. Please visit https://msi.com/page/afterburner to get more information about the product and download new versions SYSTEM REQUIREMENTS: ...................................................................................................................................... 3 FEATURES: ............................................................................................................................................................. 3 KNOWN LIMITATIONS:........................................................................................................................................... 4 REVISION HISTORY: ................................................................................................................................................ 5 VERSION 4.6.4 .............................................................................................................................................................. 5 VERSION 4.6.3 (PUBLISHED ON 03.03.2021) .................................................................................................................... 5 VERSION 4.6.2 (PUBLISHED ON 29.10.2019) .................................................................................................................... 6 VERSION 4.6.1 (PUBLISHED ON 21.04.2019) .................................................................................................................... 7 VERSION 4.6.0 (PUBLISHED ON
    [Show full text]
  • Graphics Shaders Mike Hergaarden January 2011, VU Amsterdam
    Graphics shaders Mike Hergaarden January 2011, VU Amsterdam [Source: http://unity3d.com/support/documentation/Manual/Materials.html] Abstract Shaders are the key to finalizing any image rendering, be it computer games, images or movies. Shaders have greatly improved the output of computer generated media; from photo-realistic computer generated humans to more vivid cartoon movies. Furthermore shaders paved the way to general-purpose computation on GPU (GPGPU). This paper introduces shaders by discussing the theory and practice. Introduction A shader is a piece of code that is executed on the Graphics Processing Unit (GPU), usually found on a graphics card, to manipulate an image before it is drawn to the screen. Shaders allow for various kinds of rendering effect, ranging from adding an X-Ray view to adding cartoony outlines to rendering output. The history of shaders starts at LucasFilm in the early 1980’s. LucasFilm hired graphics programmers to computerize the special effects industry [1]. This proved a success for the film/ rendering industry, especially at Pixars Toy Story movie launch in 1995. RenderMan introduced the notion of Shaders; “The Renderman Shading Language allows material definitions of surfaces to be described in not only a simple manner, but also highly complex and custom manner using a C like language. Using this method as opposed to a pre-defined set of materials allows for complex procedural textures, new shading models and programmable lighting. Another thing that sets the renderers based on the RISpec apart from many other renderers, is the ability to output arbitrary variables as an image—surface normals, separate lighting passes and pretty much anything else can be output from the renderer in one pass.” [1] The term shader was first only used to refer to “pixel shaders”, but soon enough new uses of shaders such as vertex and geometry shaders were introduced, making the term shaders more general.
    [Show full text]
  • CPU-GPU Benchmark Description
    UC San Diego UC San Diego Electronic Theses and Dissertations Title Heterogeneity and Density Aware Design of Computing Systems Permalink https://escholarship.org/uc/item/9qd6w8cw Author Arora, Manish Publication Date 2018 Peer reviewed|Thesis/dissertation eScholarship.org Powered by the California Digital Library University of California UNIVERSITY OF CALIFORNIA, SAN DIEGO Heterogeneity and Density Aware Design of Computing Systems A dissertation submitted in partial satisfaction of the requirements for the degree Doctor of Philosophy in Computer Science (Computer Engineering) by Manish Arora Committee in charge: Professor Dean M. Tullsen, Chair Professor Renkun Chen Professor George Porter Professor Tajana Simunic Rosing Professor Steve Swanson 2018 Copyright Manish Arora, 2018 All rights reserved. The dissertation of Manish Arora is approved, and it is ac- ceptable in quality and form for publication on microfilm and electronically: Chair University of California, San Diego 2018 iii DEDICATION To my family and friends. iv EPIGRAPH Do not be embarrassed by your failures, learn from them and start again. —Richard Branson If something’s important enough, you should try. Even if the probable outcome is failure. —Elon Musk v TABLE OF CONTENTS Signature Page . iii Dedication . iv Epigraph . v Table of Contents . vi List of Figures . viii List of Tables . x Acknowledgements . xi Vita . xiii Abstract of the Dissertation . xvi Chapter 1 Introduction . 1 1.1 Design for Heterogeneity . 2 1.1.1 Heterogeneity Aware Design . 3 1.2 Design for Density . 6 1.2.1 Density Aware Design . 7 1.3 Overview of Dissertation . 8 Chapter 2 Background . 10 2.1 GPGPU Computing . 10 2.2 CPU-GPU Systems .
    [Show full text]
  • Model System of Zirconium Oxide An
    First-principles based treatment of charged species equilibria at electrochemical interfaces: model system of zirconium oxide and titanium oxide by Jing Yang B.S., Physics, Peking University, China Submitted to the Department of Materials Science and Engineering in partial fulfillment of the requirements for the degree of Doctor of Philosophy at the MASSACHUSETTS INSTITUTE OF TECHONOLOGY February 2020 © Massachusetts Institute of Technology 2020. All rights reserved. Signature of Author: Jing Yang Department of Materials Science and Engineering January 10th, 2020 Certified by: Bilge Yildiz Professor of Materials Science and Engineering And Professor of Nuclear Science and Engineering Thesis Supervisor Accepted by: Donald R. Sadoway John F. Elliott Professor of Materials Chemistry Chair, Department Committee on Graduate Studies 2 First-principles based treatment of charged species equilibria at electrochemical interfaces: model system of zirconium oxide and titanium oxide by Jing Yang Submitted to the Department of Materials Science and Engineering on Jan. 10th, 2020 in partial fulfillment of the requirements for the degree of Doctor of Philosophy Abstract Ionic defects are known to influence the magnetic, electronic and transport properties of oxide materials. Understanding defect chemistry provides guidelines for defect engineering in various applications including energy storage and conversion, corrosion, and neuromorphic computing devices. While DFT calculations have been proven as a powerful tool for modeling point defects in bulk oxide materials, challenges remain for linking atomistic results with experimentally-measurable materials properties, where impurities and complicated microstructures exist and the materials deviate from ideal bulk behavior. This thesis aims to bridge this gap on two aspects. First, we study the coupled electro-chemo-mechanical effects of ionic impurities in bulk oxide materials.
    [Show full text]
  • ATI Radeon Driver for Plan 9 Implementing R600 Support
    Introduction Radeon Specifics Plan 9 Specifics Conclusion ATI Radeon Driver for Plan 9 Implementing R600 Support Sean Stangl ([email protected]) 15-412, Carnegie Mellon University October 23, 2009 1 Introduction Radeon Specifics Plan 9 Specifics Conclusion Introduction Chipset Schema Project Goal Radeon Specifics Available Documentation ATOMBIOS Command Processor Plan 9 Specifics Structure of Plan 9 Graphics Drivers Conclusion Figures and Estimates Questions 2 Introduction Radeon Specifics Plan 9 Specifics Conclusion Chipset Schema Radeon Numbering System I ATI has released many cards under the Radeon label. I Modern cards are prefixed with "HD". Rough Mapping from Chipset to Marketing Name R200 : Radeon {8500, 9000, 9200, 9250} R300 : Radeon {9500, 9600, 9700, 9800} R420 : Radeon {X700, X740, X800, X850} R520 : Radeon {X1300, X1600, X1800, X1900} R600 : Radeon HD {2400, 3600, 3800, 3870 X2} R700 : Radeon HD {4300, 4600, 4800, 4800 X2} 3 I R520 introduces yet another new shader model. I ATI develops ATOMBIOS, a collection of data tables and scripts stored in the ROM on each card. I R600 supports the Unified Shader Model. I The 2D engine gets unified into the 3D engine. I The register specification is completely different. I R700 is an optimized R600. Introduction Radeon Specifics Plan 9 Specifics Conclusion Chipset Schema Notable Chipset Deltas Each family roughly coincides with a DirectX version bump. I R200, R300, and R420 use a similar architecture. I Each family changes the pixel shader. 4 I R600 supports the Unified Shader Model. I The 2D engine gets unified into the 3D engine. I The register specification is completely different.
    [Show full text]
  • 04-Prog-On-Gpu-Schaber.Pdf
    Seminar - Paralleles Rechnen auf Grafikkarten Seminarvortrag: Übersicht über die Programmierung von Grafikkarten Marcus Schaber 05.05.2009 Betreuer: J. Kunkel, O. Mordvinova 05.05.2009 Marcus Schaber 1/33 Gliederung ● Allgemeine Programmierung Parallelität, Einschränkungen, Vorteile ● Grafikpipeline Programmierbare Einheiten, Hardwarefunktionalität ● Programmiersprachen Übersicht und Vergleich, Datenstrukturen, Programmieransätze ● Shader Shader Standards ● Beispiele Aus Bereich Grafik 05.05.2009 Marcus Schaber 2/33 Programmierung Einschränkungen ● Anpassung an Hardware Kernels und Streams müssen erstellt werden. Daten als „Vertizes“, Erstellung geeigneter Fragmente notwendig. ● Rahmenprogramm Programme können nicht direkt von der GPU ausgeführt werden. Stream und Kernel werden von der CPU erstellt und auf die Grafikkarte gebracht 05.05.2009 Marcus Schaber 3/33 Programmierung Parallelität ● „Sequentielle“ Sprachen Keine spezielle Syntax für parallele Programmierung. Einzelne shader sind sequentielle Programme. ● Parallelität wird durch gleichzeitiges ausführen eines Shaders auf unterschiedlichen Daten erreicht ● Hardwareunterstützung Verwaltung der Threads wird von Hardware unterstützt 05.05.2009 Marcus Schaber 4/33 Programmierung Typische Aufgaben ● Geeignet: Datenparallele Probleme Gleiche/ähnliche Operationen auf vielen Daten ausführen, wenig Kommunikation zwischen Elementen notwendig ● Arithmetische Dichte: Anzahl Rechenoperationen / Lese- und Schreibzugiffe ● Klassisch: Grafik Viele unabhängige Daten: Vertizes, Fragmente/Pixel Operationen:
    [Show full text]
  • 1 Títol: Aceleración Con CUDA De Procesos 3D Volum
    84 mm Títol: Aceleración con CUDA de Procesos 3D Volum: 1/1 Alumne: Jose Antonio Raya Vaquera Director/Ponent: Enric Xavier Martin Rull 55 mm Departament: ESAII Data: 26/01/2009 1 2 DADES DEL PROJECTE Títol del Projecte: Aceleración con CUDA de procesos 3D Nom de l'estudiant: Jose Antonio Raya Vaquera Titulació: Enginyeria en Informàtica Crèdits: 37.5 Director/Ponent: Enric Xavier Martín Rull Departament: ESAII MEMBRES DEL TRIBUNAL (nom i signatura) President: Vocal: Secretari: QUALIFICACIÓ Qualificació numèrica: Qualificació descriptiva: Data: 3 4 ÍNDICE Índice de figuras ............................................................................................................... 9 Índice de tablas ............................................................................................................... 12 1. Introducción ............................................................................................................ 13 1.1 Motivación ....................................................................................................... 13 1.2 Objetivos .......................................................................................................... 14 2. Antecedentes ........................................................................................................... 17 3. Historia .................................................................................................................... 21 3.1 Evolución de las tarjetas gráficas ....................................................................
    [Show full text]
  • HP Z800 Workstation Overview
    QuickSpecs HP Z800 Workstation Overview HP recommends Windows Vista® Business 1. 3 External 5.25" Bays 2. Power Button 3. Front I/O: 3 USB 2.0, 1 IEEE 1394a, 1 Headphone out, 1 Microphone in DA - 13278 North America — Version 2 — April 13, 2009 Page 1 QuickSpecs HP Z800 Workstation Overview 4. Choice of 850W, 85% or 1110W, 89% Power Supplies 9. Rear I/O: 1 IEEE 1394a, 6 USB 2.0, 1 serial, PS/2 keyboard/mouse 5. 12 DIMM Slots for DDR3 ECC Memory 2 RJ-45 to Integrated Gigabit LAN 1 Audio Line In, 1 Audio Line Out, 1 Microphone In 6. 3 External 5.25” Bays 10. 2 PCIe x16 Gen2 Slots 7. 4 Internal 3.5” Bays 11.. 2 PCIe x8 Gen2, 1 PCIe x4 Gen2, 1 PCIe x4 Gen1, 1 PCI Slot 8. 2 Quad Core Intel 5500 Series Processors 12 3 Internal USB 2.0 ports Form Factor Rackable Minitower Compatible Operating Genuine Windows Vista® Business 32-bit* Systems Genuine Windows Vista® Business 64-bit* Genuine Windows Vista® Business 32-bit with downgrade to Windows® XP Professional 32-bit custom installed** Genuine Windows Vista® Business 64-bit with downgrade to Windows® XP Professional x64 custom installed** HP Linux Installer Kit for Linux (includes drivers for both 32-bit & 64-bit OS versions of Red Hat Enterprise Linux WS4 and WS5 - see: http://www.hp.com/workstations/software/linux) For detailed OS/hardware support information for Linux, see: http://www.hp.com/support/linux_hardware_matrix *Certain Windows Vista product features require advanced or additional hardware.
    [Show full text]
  • Nvidia's GPU Microarchitectures
    NVidia’s GPU Microarchitectures By Stephen Lucas and Gerald Kotas Intro Discussion Points - Difference between CPU and GPU - Use s of GPUS - Brie f History - Te sla Archite cture - Fermi Architecture - Kepler Architecture - Ma xwe ll Archite cture - Future Advances CPU vs GPU Architectures ● Few Cores ● Hundreds of Cores ● Lots of Cache ● Thousands of Threads ● Handful of Threads ● Single Proce ss Exe cution ● Independent Processes Use s of GPUs Gaming ● Gra phics ● Focuses on High Frames per Second ● Low Polygon Count ● Predefined Textures Workstation ● Computation ● Focuses on Floating Point Precision ● CAD Gra p hics - Billions of Polygons Brief Timeline of NVidia GPUs 1999 - World’s First GPU: GeForce 256 2001 - First Programmable GPU: GeForce3 2004 - Sca la ble Link Inte rfa ce 2006 - CUDA Architecture Announced 2007 - Launch of Tesla Computation GPUs with Tesla Microarchitecture 2009 - Fermi Architecture Introduced 2 0 13 - Kepler Architecture Launched 2 0 16 - Pascal Architecture Tesla - First microarchitecture to implement the unified shader model, which uses the same hardware resources for all fragment processing - Consists of a number of stream processors, which are scalar and can only operate on one component at a time - Increased clock speed in GPUs - Round robin scheduling for warps - Contained local, shared, and global memory - Conta ins Spe cia l-Function Units which are specialized for interpolating points - Allowed for two instructions to execute per clock cycle per SP Fermi Peak Performance Overview: ● Each SM has 32
    [Show full text]
  • Evaluating ATTILA, a Cycle-Accurate GPU Simulator
    Evaluating ATTILA, a cycle-accurate GPU simulator Miguel Ángel Martínez del Amor Department of Computer and Information Science Norwegian University of Science and Technology (NTNU) [email protected] Project supervisor: Lasse Natvig [email protected] 26 th January 2007 Abstract. As GPUs’ technology grow more and more, new simulators are needed to help on the task of designing new architectures. Simulators have several advantages compared to an implementation directly in hardware, so they are very useful in GPU development. ATTILA is a new GPU simulator that was born to provide a framework for working with real OpenGL applications, simulating at the same time a GPU that has an architecture similar to the current designs of the major GPU vendors like NVIDIA or ATI. This architecture is highly configurable, and also ATTILA gives a lot of statistics and information about what occurred into the simulated GPU during the execution. This project will explain the main aspects of this simulator, with an evaluation of this tool that is young but powerful and helpful for researchers and developers of new GPUs. 1. Introduction The main brain of computers is the CPU (Central Processing Unit), where the instructions are executed, manipulating by this way the data stored in memory. But with the new applications that demand even more resources, the CPU is becoming a bottleneck. There is a lot of works about how to improve the CPI (Cycles per Instruction) which is a good parameter for making comparisons between uniprocessor architectures, and the search for parallelism is the best way to do it.
    [Show full text]