DOCSLIB.ORG

ROBUST SOFTWARE DEVELOPMENT BUG PREVENTION and ISOLATION Erika Dignam and Ross Cunniff 04 April 2016 ABOUT US

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ROBUST SOFTWARE DEVELOPMENT BUG PREVENTION and ISOLATION Erika Dignam and Ross Cunniff 04 April 2016 ABOUT US April 4-7, 2016 | Silicon Valley ROBUST SOFTWARE DEVELOPMENT BUG PREVENTION AND ISOLATION Erika Dignam and Ross Cunniff 04 April 2016 ABOUT US Ross Cunniff Senior Software Engineer and NVIDIA SPEC representative. 15-year NVIDIA employee. Over 30 years of computer engineering experience. Erika Dignam Technical Program Manager and Bug Triager Studied computer arts. At NVIDIA for 9 years. 4/25/2016 2 Bug types | Triage and Tools | Recap STRUCTURE Process Details | Bookkeeping Prevention and Benchmarking 3 BUG TYPES Crash or TDR Corruption Performance SLI Scaling 4/25/2016 4 TOOLS AND TRIAGE Traces – All bug types What is a trace? Intercepts calls between application and driver | Records to a file NV apitrace APP Driver file.trace • Apitrace (DX and OpenGL) - http://apitrace.github.io/ • Pass along .trace file – Replay, performance info, and dump API stream • Simple to use - copy <API>.dll to executable location • Caveats - Long reproductions means large files | Tracing tools don’t always capture | Some apps are not tracing friendly out of the box 4/25/2016 5 TOOLS AND TRIAGE Traces More Tracing tools • GLIntercept (OpenGL) - https://github.com/dtrebilco/glintercept • Useful for error states and other tracing, a little older than apitrace • Copy opengl.dll and gliConfig.ini to executable folder location • Swapping the DebugContext.ini config file can give very helpful information, for example issues with SLI Scaling EXAMPLE: • OpenGL: Performance(Medium) 131234: SLI performance warning: SLI AFR copy and synchronization for texture mipmaps (42) 4/25/2016 6 TOOLS AND TRIAGE Crashes/TDR Dump files • Mini dump - Always helpful, you can simply right click the process from the task manager or process explorer and select “Dump to File” • Full dump - Better, but larger • https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx TDR – Timeout Detection and Recovery • Increase the TDR delay, what are the results then? • https://msdn.microsoft.com/en-us/library/windows/hardware/ff569918(v=vs.85).aspx 4/25/2016 7 TOOLS AND TRIAGE CPU Profilers - Performance Intel VTune • In-depth perf analysis, finer tuned control, filters noise | Needs a license, not free • https://software.intel.com/en-us/intel-vtune-amplifier-xe AMD CodeAnalyst • Simple, free, runs on both CPUs | Less robust than Vtune, no longer supported • http://developer.amd.com/tools-and-sdks/archive/amd-codeanalyst- performance-analyzer/ App bound? Driver bound? GPU bound? Performance paths taken 4/25/2016 8 TOOLS AND TRIAGE Performance/Resources Process Explorer • Free quick overview tool - Check loaded .dlls, can see load on resources, memory leaks, GPU or CPU bound • https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx GPUview • Free Windows tool included with the Windows Performance Toolkit (WPT) • https://graphics.stanford.edu/~mdfisher/GPUView.html • https://developer.nvidia.com/content/are-you-running-out-video-memory- detecting-video-memory-overcommitment-using-gpuview 4/25/2016 9 PROCESS EXPLORER 10 TOOLS AND TRIAGE Tools gDEBugger • http://www.gremedy.com/ • Free OpenGL debugging tool • Useful for data gathering, good for tracking state changes, dynamically look at stream • EXAMPLE: • Polygon count information from models • Performance bug was root caused to one mode of the model was sending a significant amount more polys into the OpenGL pipeline. 4/25/2016 11 NVIDIA TOOLS AND LOGS NVIDIA OpenGL Driver Error codes External Swak = Swiss Army Knife • NVIDIA tool used to capture detailed system information • Only available under NDA, on the partners site WSAppNotifier.exe – Profiles • For application profile problems, tells you which profiles are running/applied • You may have to launch the app twice • NDA only, on partner site 4/25/2016 12 WSAPPNOTIFIER.EXE 13 TRIAGE/DEBUGGING Profiles – Things to Try Changing Global Profiles • Workstation App - Dynamic Streaming | Turns off some optimized driver paths • 3D App – Game Development | Simulates a GeForce • SLI Aware Application | SLI performance testing • Threaded optimization = OFF | In Profile settings Notebooks • Try setting NVIDIA GPU to default | In profiles or SBIOS if available 4/25/2016 14 RECAP What tools for what bugs Crash or TDR • TDR Delay RegKeys | Collect dump files | Trace | GPUView Corruption • Trace | Changing profiles Performance • Changing profiles | apitrace | VTune/CodeAnalyst SLI Scaling • Debug Context from GLIntercept 4/25/2016 15 TRIAGE/DEBUGGING Vulkan https://www.khronos.org/vulkan/ • New API that puts the application developer in control, appDev manages GPU memory and resources Built in Validation Layer – API violations SDK - https://vulkan.lunarg.com/signin | Need account Demos • https://github.com/SaschaWillems/Vulkan | https://github.com/McNopper/Vulkan Renderdoc | Graphics Debugger https://github.com/baldurk/renderdoc 4/25/2016 16 TRIAGE/DEBUGGING Vulkan Vulkan Talks • S6818 – Vulkan and NVIDIA: The Essentials • S6138 – GPU Driven Rendering in Vulkan and OpenGL • S6133 – VKCPP: A C++ Layer on Top of Vulkan • Three Hangouts, Monday and Tuesday afternoons Resources • https://github.com/KhronosGroup/Khronosdotorg/blob/master/api/vulkan/resources.md 4/25/2016 17 BUG PROCESS Normal External Bug Flow • External Bug -> QA -> Triage -> Engineering Accounts to file bugs • partners.nvidia.com – Needs NDA • developer.nvidia.com\join • Access to early release drivers and NVIDIA tools, report bugs! 4/25/2016 18 BUG PROCESS Overview NVBUGS Start by filing as a software issue Important to have basic reproduction steps • OS, driver, card, application and version if applicable, system information, frequency • Severity and impact for you • Type - Performance, Crash, Corruption, TDR Regression information is very helpful if can be provided 4/25/2016 19 20 TOOLS AND TRIAGE Overview Simple app/license • A trace would be great, no license/app/model needed • Avoids delays, very useful when a third party has a repro others can’t get • If not possible, then models/scenes/app/license/demo will be needed – Time sink What to attach to bugs • Logs, traces, performance snap shots, dump files, videos, event logs • System information via externSwak (NVTOOL) 4/25/2016 21 WHAT HAPPENS TO YOUR BUG Fixes -> Driver | Branches ODE = Optimized Driver for Enterprise QNF = Quadro New Feature • Long lived branch • Short lived branch • Multiple releases or dot version per • One release per branch branch • Release driver for testing new • For production use and features and fixes certification WHQL = Windows Hardware Quality Labs Testing and Signed 22 4/25/2016 PREVENTION What NVIDIA does ATP and QA • We have QA teams with application experts around the world testing applications, GPUs, OSs, and drivers • ATP is our automated test harness for further testing to cover more configurations DVS • Driver Validation System. Automated and run with every single code change. 10 million images/tests per day German Test Lab and Global Test Lab • 24/7 automated testing of professional applications and features 4/25/2016 23 PREVENTION Best Process We want benchmarks and test suites! • Early detection of bugs and issues • Early detection of performance regressions • Get involved in industry standard benchmarks, example SPEC Over to Ross to discuss Performance Benchmark creation! 4/25/2016 24 PERFORMANCE BENCHMARKING A key to high-quality user experience 25 “WHEN YOU CANNOT MEASURE IT… …your knowledge is of a meagre and unsatisfactory kind” – Lord Kelvin Anything a computer can do, a human can do. Given enough time… Computers are accelerators. Without good performance, user experience is bad. Benchmarking is the technique to ensure repeatable performance 26 WHAT MAKES A BENCHMARK? Originally a surveying mark which provided a repeatable reference for placing a leveling rod. Key attributes: #1: repeatable #2: accurate #3: reportable 27 UNITS ARE NOT BENCHMARKS Many common units exist: MIPS, FLOPS, FPS, LPM, … Just because you can run a test and get units out, does not make your test a benchmark Quiz: if your test returns a result 60 FPS, what might you be measuring? What about 30, 20, 15, … FPS? 28 REPEATABILITY First principle: make sure the same operations are benchmarked on all configs Most benchmarks exhibit some randomness in performance The causes are many; some examples: Non-deterministic operating system process / thread scheduler Disk I/O – variable times to reach a sector with rotational media; variable wear leveling for solid state media Build-to-build variation due to cache layout changes Virus scan cycles Rule of thumb: a variation of up to 5% is generally acceptable (if higher, use multiple runs and rely on regression toward the mean) 29 ACCURACY “Do these numbers reflect reality?” Always verify assumptions. Do you expect your benchmark to be GPU limited? Then verify on GPUs with different performance levels. Faster is not always better – ensure work is actually being done that reflects end- user experience A good benchmark has a means to verify correct operation Make sure the key portion of your benchmark runs long enough that you can actually measure its performance, not virtual memory subsystem latency or other irrelevant metrics 30 NOTES ON TUNING If you are not measuring properly, you might not be able to make improvements 60Hz example – sync-to-vblank (default on NVIDIA) Bottleneck shift. A graphics benchmark may start CPU/API-limited, then after tuning move to being limited by GPU vertex processing. Or even change to being limited by pixel-processing as window sizes change or as workloads
Load more

Recommended publications
  • An Introduction to Analysis and Optimization with AMD Codeanalyst™ Performance Analyzer
    An introduction to analysis and optimization with AMD CodeAnalyst™ Performance Analyzer Paul J. Drongowski AMD CodeAnalyst Team Advanced Micro Devices, Inc. Boston Design Center 8 September 2008 Introduction This technical note demonstrates how to use the AMD CodeAnalyst™ Performance Analyzer to analyze and improve the performance of a compute-bound program. The program that we chose for this demonstration is an old classic: matrix multiplication. We'll start with a "textbook" implementation of matrix multiply that has well-known memory access issues. We will measure and analyze its performance using AMD CodeAnalyst. Then, we will improve the performance of the program by changing its memory access pattern. 1. AMD CodeAnalyst AMD CodeAnalyst is a suite of performance analysis tools for AMD processors. Versions of AMD CodeAnalyst are available for both Microsoft® Windows® and Linux®. AMD CodeAnalyst may be downloaded (free of charge) from AMD Developer Central. (Go to http://developer.amd.com and click on CPU Tools.) Although we will use AMD CodeAnalyst for Windows in this tech note, engineers and developers can use the same techniques to analyze programs on Linux. AMD CodeAnalyst performs system-wide profiling and supports the analysis of both user applications and kernel- mode software. It provides five main types of data collection and analysis: • Time-based profiling (TBP), • Event-based profiling (EBP), • Instruction-based sampling (IBS), • Pipeline simulation (Windows-only feature), and • Thread profiling (Windows-only feature). We will look at the first three kinds of analysis in this note. Performance analysis usually begins with time-based profiling to identify the program hot spots that are candidates for optimization.
    [Show full text]
  • Software Optimization Guide for Amd Family 15H Processors (.Pdf)
    Software Optimization Guide for AMD Family 15h Processors Publication No. Revision Date 47414 3.06 January 2012 Advanced Micro Devices © 2012 Advanced Micro Devices, Inc. All rights reserved. The contents of this document are provided in connection with Advanced Micro Devices, Inc. (“AMD”) products. AMD makes no representations or warranties with respect to the accuracy or completeness of the contents of this publication and reserves the right to make changes to specifications and product descriptions at any time without notice. The infor- mation contained herein may be of a preliminary or advance nature and is subject to change without notice. No license, whether express, implied, arising by estoppel or other- wise, to any intellectual property rights is granted by this publication. Except as set forth in AMD’s Standard Terms and Conditions of Sale, AMD assumes no liability whatsoever, and disclaims any express or implied warranty, relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particular purpose, or infringement of any intellectual property right. AMD’s products are not designed, intended, authorized or warranted for use as compo- nents in systems intended for surgical implant into the body, or in other applications intended to support or sustain life, or in any other application in which the failure of AMD’s product could create a situation where personal injury, death, or severe property or environmental damage may occur. AMD reserves the right to discontinue or make changes to its products at any time without notice. Trademarks AMD, the AMD Arrow logo, and combinations thereof, AMD Athlon, AMD Opteron, 3DNow!, AMD Virtualization and AMD-V are trademarks of Advanced Micro Devices, Inc.
    [Show full text]
  • AMD Codexl 1.7 GA Release Notes
    AMD CodeXL 1.7 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft® Visual Studio® 2010 extension o CodeXL Microsoft® Visual Studio® 2012 extension o CodeXL Microsoft® Visual Studio® 2013 extension o CodeXL Remote Agent For 64-bit Linux platforms o CodeXL Standalone application o CodeXL Remote Agent Note about installing CodeAnalyst after installing CodeXL for Windows AMD CodeAnalyst has reached End-of-Life status and has been replaced by AMD CodeXL. CodeXL installer will refuse to install on a Windows station where AMD CodeAnalyst is already installed. Nevertheless, if you would like to install CodeAnalyst, do not install it on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5000 series or newer, desktop or mobile version) or APU is required. o The AMD Catalyst Driver must be installed, release 13.11 or later. Catalyst 14.12 (driver 14.501) is the recommended version. See "Getting the latest Catalyst release" section below. For GPU API-Level Debugging, a working OpenCL/OpenGL configuration is required (AMD or other). CPU Profiling o Time-Based Profiling can be performed on any x86 or AMD64 (x86-64) CPU/APU.
    [Show full text]
  • AMD Codexl 1.8 GA Release Notes
    AMD CodeXL 1.8 GA Release Notes Contents AMD CodeXL 1.8 GA Release Notes ......................................................................................................... 1 New in this version .............................................................................................................................. 2 System Requirements .......................................................................................................................... 2 Getting the latest Catalyst release ....................................................................................................... 4 Note about installing CodeAnalyst after installing CodeXL for Windows ............................................... 4 Fixed Issues ......................................................................................................................................... 4 Known Issues ....................................................................................................................................... 5 Support ............................................................................................................................................... 6 Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft® Visual Studio®
    [Show full text]
  • Instruction-Based Sampling: a New Performance Analysis Technique for AMD Family 10H Processors
    Instruction-Based Sampling: A New Performance Analysis Technique for AMD Family 10h Processors Paul J. Drongowski AMD CodeAnalyst Project Advanced Micro Devices, Inc. Boston Design Center 16 November 2007 1. Introduction Software applications must use computational resources efficiently in order to deliver best results in a timely manner. This is especially true for time-sensitive applications such as transaction processing, real-time control, multi-media and games. A program profile is a histogram that reflects dynamic program behavior. For example, a profile shows where a program is spending its time. Program profiling helps software developers to meet performance goals by identifying performance bottlenecks and issues. Profiling is most effective when a developer can quickly identify the location and cause of a performance issue. Instruction-Based Sampling (IBS) is a new profiling technique that provides rich, precise program performance information. IBS is introduced by AMD Family10h processors (AMD Opteron Quad- Core processor “Barcelona.”) IBS overcomes the limitations of conventional performance counter sampling. Data collected through performance counter sampling is not precise enough to isolate performance issues to individual instructions. IBS, however, precisely identifies instructions which are not making the best use of the processor pipeline and memory hierarchy. IBS collects a wide range of performance information in a single program run, making it easier to conduct performance testing. The AMD CodeAnalyst performance analysis tool suite supports IBS and correlates the instruction-level IBS information with processes, program modules, functions and source code. IBS in combination with CodeAnalyst helps a developer to find, analyze and ameliorate performance problems. This technical note is a brief introduction to Instruction-Based Sampling.
    [Show full text]
  • AMD Codexl 1.1 GA Release Notes
    AMD CodeXL 1.1 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use our CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: CodeXL Visual Studio 2012 and 2010 packages and Standalone application, for 32-bit and 64-bit Windows platforms CodeXL for 64-bit Linux platforms Kernel Analyzer v2 for both Windows and Linux platforms Note about 32-bit Windows CodeXL 1.1 Upgrade Error On 32-bit Windows platforms, upgrading from previous version of CodeXL using the CodeXL 1.1 installer will remove the previous version and then display an error message without installing CodeXL 1.1. The recommended method is to uninstall previous CodeXL before installing CodeXL 1.1. If you ran the 1.1 installer to upgrade a previous installation and encountered the error mentioned above, ignore the error and run the installer again to install CodeXL 1.1. Note about installing CodeAnalyst after installing CodeXL for Windows CodeXL can be safely installed on a Windows station where AMD CodeAnalyst is already installed. However, do not install CodeAnalyst on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5xxx or newer) or APU is required o The AMD Catalyst Driver must be installed, release 12.8 or later.
    [Show full text]
  • AMD Codexl 1.9 GA Release Notes
    AMD CodeXL 1.9 GA Release Notes Contents AMD CodeXL 1.9 GA Release Notes ......................................................................................................... 1 New in this version .............................................................................................................................. 2 System Requirements .......................................................................................................................... 2 Getting the latest Radeon software release ......................................................................................... 4 Note about installing CodeAnalyst after installing CodeXL for Windows ............................................... 4 Fixed Issues ......................................................................................................................................... 4 Known Issues ....................................................................................................................................... 5 Support ............................................................................................................................................... 7 Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft® Visual Studio® 2010
    [Show full text]
  • AMD Technology & Software
    AMD Technology & Software Justin Boggs, Sr. Developer Relations Engineer [email protected] Q3’06 Agenda • Desktop Overview • Processors & Roadmap • Software Architecture & Performance • Desktop Platforms • Future AMD Technology Directions • AMD Developer Resources • Call to Action 2 AMD Technology & Software AMD Desktop Overview AMD Desktop Advantage • Built from the ground up, AMD x86 processor technology makes it possible to improve responsiveness to changing business needs AMD64 offers flexibility by supporting 32- and 64-bit applications across desktop, mobile and server applications Direct Connect Architecture enables increased performance, scalability and improved multi-tasking AMD Dual Core provides enhanced performance without increasing power requirements AMD Cool ‘n’ Quiet™ decreases overall power consumption by optimizing performance on demand Enhanced Virus Protection adds an extra level of virus protection to your security solution 4 AMD Technology & Software AMD64™ Powerful 64-Bit Computing • Technology that gives total backward compatibility with leading-edge 32-bit computing performance. • Technology that paves the way to multi-core computing with cutting-edge communications technology. • Technology is more than 64-bit computing— it’s also about next-generation architecture. • Technology that allows software developers to create new functionality for end users. • Technology that solves real problems. 5 AMD Technology & Software AMD Direct Connect Architecture Direct Connect Architecture moves more data more efficiently,
    [Show full text]
  • Improving Program Performance with AMD Codeanalyst for Linux® Paul J. Drongowski AMD Codeanalyst Team May 9, 2007
    Improving program performance with AMD CodeAnalyst for Linux® Paul J. Drongowski AMD CodeAnalyst team May 9, 2007 AMD CodeAnalyst for Linux® Identify and investigate performance hot-spots Easy to use graphical user interface – Simplified configuration of performance events – GUI is consistent for cross-platform use Low overhead, system-wide data collection – Can profile dynamically loaded modules – Can profile kernel mode drivers as well as applications Results are displayed in configurable views – Source and disassembly annotated with performance data – Rates and ratios assist interpretation of results 2 May 9, 2007 Using AMD CodeAnalyst for Linux AMD CodeAnalyst for Linux Open source – Uses oprofile for data collection – Can import oprofile data – CodeAnalyst GUI is Qt-based Java profiling support – Version 2.5: Modified oprofile driver and daemon – Version 2.6: Modified daemon only 3 May 9, 2007 Using AMD CodeAnalyst for Linux Presentation outline AMD CodeAnalyst in action – Time-based profiling – Event-based profiling – Tuning Downloading AMD CodeAnalyst On-line resources 4 May 9, 2007 Using AMD CodeAnalyst for Linux AMD CodeAnalyst in action 5 May 9, 2007 Using AMD CodeAnalyst for Linux Performance tuning cycle Measure performance Change Identify program hot-spot Identify cause 6 May 9, 2007 Using AMD CodeAnalyst for Linux Kinds of analysis Identify hot-spot: Time-based profiling – Where is the application or system spending time? Identify cause: Event-based profiling – How is the application behaving on the CPU? Memory?
    [Show full text]
  • Efficient Implementation of Finite Element Operators on Gpus
    FRIEDRICH-ALEXANDER-UNIVERSITAT¨ ERLANGEN-NURNBERG¨ INSTITUT FUR¨ INFORMATIK (MATHEMATISCHE MASCHINEN UND DATENVERARBEITUNG) Lehrstuhl f¨ur Informatik 10 (Systemsimulation) Efficient Implementation of Finite Element Operators on GPUs Severin Strobl Studienarbeit Efficient Implementation of Finite Element Operators on GPUs Severin Strobl Studienarbeit Aufgabensteller: Prof. Dr. C. Pflaum Betreuer: Prof. Dr. C. Pflaum Bearbeitungszeitraum: 01.01.2008 – 02.09.2008 Erkl¨arung: Ich versichere, dass ich die Arbeit ohne fremde Hilfe und ohne Benutzung anderer als der angegebenen Quellen angefertigt habe und dass die Arbeit in gleicher oder ¨ahnlicher Form noch keiner anderen Prufungsbeh¨ ¨orde vorgelegen hat und von dieser als Teil einer Prufungs-¨ leistung angenommen wurde. Alle Ausfuhrungen,¨ die w¨ortlich oder sinngem¨aß ubernommen¨ wurden, sind als solche gekennzeichnet. Erlangen, den 1. September 2008 . Abstract Graphics processing units (GPUs) of the current generation are highly programmable using interfaces like NVIDIA’s Compute Unified Device Architecture (CUDA) while of- fering a massive computational power for a relatively low price. The solution of systems of linear equations described by stencils representing finite element operators by iterative solvers is a application which can utilize these benefits of GPUs. This thesis describes the implementation of a parallelized Gauss-Seidel solver achieving up to 40 times the perfor- mance of a corresponding solver on standard CPUs. The solver is part of a library named GPUsolve, which offers the infrastructure to integrate this GPU-enabled application into object oriented C++ code. 4 Contents 1 Introduction 7 2 GPU Programming 8 2.1 GPU Hardware .................................... 8 2.2 Shader Programming ................................. 9 2.2.1 BrookGPU .................................. 10 2.2.2 Sh ......................................
    [Show full text]
  • A Methodology for Efficient Multiprocessor System-On
    A Methodology for Efficient Multiprocessor System-on-Chip Software Development Von der Fakult¨at f¨ur Elektrotechnik und Informationstechnik der Rheinisch–Westf¨alischen Technischen Hochschule Aachen zur Erlangung des akademischen Grades eines Doktors der Ingenieurwissenschaften genehmigte Dissertation vorgelegt von M.Sc. Jianjiang Ceng aus Zhejiang/China Berichter: Univ.-Prof. Dr. rer. nat. Rainer Leupers Univ.-Prof. Dr.-Ing. Gerd Ascheid Tag der m¨undlichen Pr¨ufung: 28.04.2011 Diese Dissertation ist auf den Internetseiten der Hochschulbibliothek online verf¨ugbar. Contents 1 Introduction 1 1.1 Background ...................................... 1 1.2 MPSoCSoftwareDevelopmentChallenge . ........ 3 1.2.1 ProgrammingModel .............................. 4 1.2.2 ApplicationParallelization . ...... 6 1.2.3 MappingandScheduling . .. 6 1.2.4 CodeGeneration ................................ 7 1.2.5 ArchitectureModelingandSimulation . ...... 7 1.2.6 Summary .................................... 8 1.3 ThesisOrganization. .. ... .. .. .. .. .. ... .. .. .. .. .. ..... 8 2 Related Work 11 2.1 GeneralPurposeMulti-Processor . ........ 11 2.1.1 Cell ....................................... 12 2.2 GeneralPurposeGraphicsProcessingUnit . ......... 13 2.3 Embedded Multi-Processor System-on-Chip . .......... 14 2.3.1 MPCore ..................................... 14 2.3.2 IXP ....................................... 14 2.3.3 OMAP...................................... 15 2.3.4 CoMPSoC.................................... 17 2.3.5 SHAPES....................................
    [Show full text]
  • Innovatives Supercomputing in Deutschland
    inSiDE • Vol. 8 No.1 • Spring 2010 Innovatives Supercomputing in Deutschland Editorial Contents Welcome to this new issue of InSiDE the physics of galactic nuclei and the the journal on innovative Supercomput- global parameter optimization of a News ing in Germany published by the Gauss physics-based united-residue force field PRACE: Ready for Implementation 4 Center for Supercomputing. for proteins. New JUVIS Visualization Cluster 7 The focus of the last months all over Projects are an important driving fac- Europe was on the European HPC initia- tor for our community. They provide Applications tive PRACE (Partnership for Advanced a chance to develop and test new Direct Numerical Simulation of Computing in Europe) and the Gauss methods and tools. They allow further Active Separation Control Devices 8 Center for Supercomputing has played improving existing codes and building a very active and important role in the tools we need in order to harness Numerical Simulation and Analysis of Cavitating Flows 14 this process. As a result of all these the performance of our systems. activities PRACE is now ready for the A comprehensive section of projects Modelling Convection over West Africa 18 implementation phase. Here you find an describes among other the recent ad- overview of the results achieved in this vances in the UNICORE 6 middleware Driving Mechanisms of the Geodynamo 26 Editorial issue. In our autumn edition we will be software. This is a good example how Contents able to report on the next steps which a nationally funded project that was The Maturing of Giant Galaxies by Black Hole Activity 32 will include the founding of a formal supported by European projects finally European organization.
    [Show full text]