DOCSLIB.ORG

Hb Lee Hvac Upgrades Specifications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Hb Lee Hvac Upgrades Specifications SECTION 00 01 10 TABLE OF CONTENTS DESCRIPTION OF CONTENTS The complete Contract Documents contain the following: VOLUME 1 PROJECT MANUAL Division 0 Contracting Requirements Division 1 General Requirements Divisions 2-14 Building Technical Specification Divisions 21-23 Mechanical Technical Specification Divisions 26-28 Electrical Technical Specification Divisions 31-33 Site Technical Specification VOLUME 2 PROJECT DRAWINGS Division G General Drawings Division C Civil Drawings Division L Landscape Drawings Division A Architectural Drawings Division E Electrical Drawings Division M Mechanical Drawings Division P Plumbing Drawings VOLUME 1 PROJECT MANUAL Unit Number Description DIVISION 0 BIDDING AND CONTRACTING REQUIREMENTS Section 00 01 01 Introduction 00 01 10 Table of Contents 00 11 16 Invitation to Bidders 00 21 13 Instructions to the Bidders Substitution Request Form 00 41 00 Bid Form First-Tier Subcontractor Disclosure Form 00 50 00 Agreement Forms State of Oregon Public Improvement Agreement 00 61 00 Bond Forms Bid Bond Form Performance and Payment Bond Forms 00 72 00 General Conditions State of Oregon General Conditions for Public Improvement Contracts 00 73 43 Prevailing Wage Rates 00 91 13 Addendum DIVISION 1 GENERAL REQUIREMENTS Section 01 11 00 Summary of Work 01 21 13 Unit Cost Work Items 01 23 00 Alternative Bid Items 00 29 00 Payment Procedures June 9, 2016 Reynolds School District 7 00 01 10-1 HB Lee Middle School HVAC Upgrades SECTION 00 01 10 TABLE OF CONTENTS 01 31 00 Coordination 01 33 00 Submittals 01 40 00 Quality Requirements 01 50 00 Temporary Facilities and Controls 01 60 00 Product Requirements 01 70 00 Execution requirements 01 77 00 Closeout Procedures 01 90 00 General Commissioning Requirements DIVISION 2 DEMOLITION Section 02 22 50 Selective Demolition DIVISION 5 METALS Section 05 82 00 Fencing and Gates DIVISION 6 CARPENTRY Section 06 10 00 Rough Framing DIVISION 9 FINISHES Section 09 25 00 Gypsum Board 09 50 00 Lay-In Acoustic Ceilings 09 51 00 Acoustical Ceilings 09 90 00 Painting DIVISION 23 HEATING, VENTILATING, AND AIR CONDITIONING Section 23 05 00 HVAC Materials & Methods 23 05 90 Air Balance Detailed 23 07 00 Mechanical Insulation 23 09 23 DDC Controls 23 09 93 HVAC Sequence 23 10 00 Facility Fuel Systems 23 21 00 Hydronic System 23 25 00 Chemical Treatment 23 30 00 Air Distribution 23 34 00 HVAC Fans 23 40 00 HVAC Air Filters 23 52 00 Heating Boilers 23 62 15 Air Cooled Liquid Chiller DIVISION 26 ELECTRICAL Section 26 05 00 Common Work Results for Electrical 26 05 19 Electrical Power Conductors and Cables 26 05 29 Hangers and Supports for Electrical Systems 26 05 33 Raceway and Boxes for Electrical Systems 26 05 53 Identification for Electrical Systems 26 27 26 Wiring Devices 26 28 00 Circuit Protective Devices June 9, 2016 Reynolds School District 7 00 01 10-2 HB Lee Middle School HVAC Upgrades SECTION 00 01 10 TABLE OF CONTENTS VOLUME 2 PROJECT DRAWINGS A list of drawings is included on Project Drawings. C0.0 - Cover Sheet M1.0 - Mechanical Demo Plans M1.1 - Mechanical Demo Plan M1.2 - Mechanical Demo Plan M1.3 - Mechanical Demo Plan M1.4 - Mechanical Demo Plans M2.0 - Mechanical Plans M2.1 - Mechanical Plans M2.2 - Mechanical Plans M2.3 - Mechanical Plans M2.4 - Mechanical Plans M3.1 - Mechanical Piping Plans M5.1 - Mechanical Controls M5.2 - Mechanical Controls M6.0 - Mechanical Schedules M6.1 - Mechanical Details M6.2 - Mechanical Details E0.9 - Legends E1.0 - Electrical Demo Plan E1.1 - Electrical Demo Plan E1.2 - Electrical Demo Plan E1.3 - Electrical Demo Plan E1.4 - Electrical Demo Plan E1.5 - Lighting Plan E1.6 - Lighting Plan E1.7 - Power Plan E1.8 - Power Plan E1.9 - Power Plan E2.0 - Power Plan E2.1 - Power Plan E2.2 - One Line Diagram E2.3 - Panel Schedules E2.4 - HVAC Conduit & Wire Schedules END OF SECTION June 9, 2016 Reynolds School District 7 00 01 10-3 HB Lee Middle School HVAC Upgrades SECTION 02 22 50 SELECTIVE DEMOLITION PART 1 - GENERAL 1.01 SUMMARY A. Contract Conditions: Work of this Section is bound by the Contract Conditions and Division 1, bound herewith, in addition to this Specification and accompanying Drawings. B. Provide selective demolition as required. 1. Demolish interior ceilings and soffits where new work is placed. 2. Demolish exterior portions of facade, structures, and components designated to be removed. 3. Protect portions of building adjacent to or affected by selective demolition. 4. Remove and legally dispose of demolished materials off-site. 5. Notify Owner prior to shut-off of existing utilities. Cap off utilities to be discontinued in use. 6. Do all minor demolition required for proper completion of the work. 1.02 QUALITY ASSURANCE A. Compliance 1. In addition to complying with all pertinent codes and regulations, comply with the requirements of all insurance carriers providing coverage for this work. 1.03 PROJECT CONDITIONS A. Protection of Person & Property 1. Extend requirements of General Conditions to include: a. Protection of neighboring property, occupants of said property, customers, visitors, and passersby from injury and discomfort caused by dust. b. Provide dust tight chutes and sprinkle dust as necessary to accomplish this result. 2. Protect from damage those portions which are to remain. a. Allow no leaks, even temporary, in existing structures. b. Provide dustproof and/or soundproof partitions where indicated, and as detailed: provide other dust protection as required to protect occupied areas. 3. Repair all damage to Owner's property resulting from the minor demolition work. 4. Cooperate in maintaining continuous operation of Owner's facility. B. Objectionable Noise 1. Schedule work requiring air hammers or other noisy equipment in cooperation with Owner to minimize disruption. C. Asbestos 1. Contractor shall review the Owner's Management Plan and become familiar with the document. All known asbestos work will have been June 9, 2016 Reynolds School District 7 02 22 50 - 1 HB Lee Middle School HVAC Upgrades SECTION 02 22 50 SELECTIVE DEMOLITION abated prior to work of this contract. Do not disturb any suspect material. Report any suspicious materials to the Project Coordinator. PART 2 - PRODUCTS 2.01 SALVAGE A. To Contractor 1. All salvage becomes Contractor's property. 2. Contractor shall remove all salvaged items from the site at Contractor's expense. Storage or sale of items at project site is prohibited. 3. Specific items have been identified for reuse in the completed facility. Contractor is to remove store and install items as part of this contract. 4. See drawings for refrigerant recovery owner is to perform at chillers. B. To Owner 1. Owner will identify those salvage items in the project area to be delivered to Owner. PART 3 - EXECUTION 3.01 PREPARATION A. Site Inspection 1. Prior to work of this section, carefully inspect the entire site and determine what areas or items will require removal and which items will remain to accomplish the work. 2. Locate all existing active utility lines and determine the requirements for their protection. 3.02 MINOR DEMOLITION WORK A. Extent of Work in this Section 1. Do all minor demolition and removal for completion of the remodeling work shown on the drawings, specified herein or required for completion of the work. 2. Where flooring is removed or other finished materials which will be required to patch surfaces to make finished area match existing salvage material for this purpose. 3. Cease operations if public safety or remaining structures are endangered. Perform temporary corrective measures until operations can be continued properly. B. Utilities 1. Keep utilities intact and in continuous operation. 2. Do not close or obstruct streets, walks, drives or other occupied or used spaces or facilities without the written permission of the Owner and the authorities having jurisdiction. Do not interrupt utilities serving occupied or used facilities without the written permission of the Owner and authorities having jurisdiction. If necessary, provide temporary utilities. C. Concrete Sawing, when required June 9, 2016 Reynolds School District 7 02 22 50 - 2 HB Lee Middle School HVAC Upgrades SECTION 02 22 50 SELECTIVE DEMOLITION 1. Provide equipment with diamond blades, appropriate for suiting job conditions. 2. Saw cut existing concrete slabs and curbs where indicated or required for construction or work below slab. This is to include exterior walks and curbs. 3. When cutting openings through walls core drill corner of horizontal and vertical intersection of cut line, do not over run line at corner. D. Debris 1. Allow no debris to accumulate in structure, or on grounds, streets, alleys and walks. 2. Haul away and dispose of at legal disposal areas away from site, at Contractor's expense. E. Demolition Coordination: Reynolds School Districts Hazardous Material Abatement Contractor has been placed under contract for the removal of some but not all items noted on these demolition pages. The following items are removed by the Owner’s contractor. 1. Air handlers serving the old shop classrooms shown to be removed in detail 2M1.3 and 3M1.3. This includes associated ducts to allow removal of the units and to a point of the new duct connections shown on the new construction drawings. Piping from coil to new system connection or old boiler room connection is included in the air handler scope. 2. All Unit ventilators including coil connection to the mains in the wall or near the floor. 3. All hallway HVAC units including coil connection to the wall or floor. 4. Roof top exhaust fans scheduled to be replaced or removed. 5. All piping shown to be demoed in the boiler room and mechanical mezzanines.
Load more

Recommended publications
  • Automatic Temperature Controls
    230900S03 INSTRUMENTATION AND CONTROL FOR HVAC UK Controls Standard SECTION 230900S03 - AUTOMATIC TEMPERATURE CONTROLS PART 1 - GENERAL RELATED DOCUMENTS: Drawings and general provisions of the Contract, including General and Supplementary Conditions, General Mechanical Provisions and General Requirements, Division 1 Specification Sections apply to the work specified in this section. DESCRIPTION OF WORK: Furnish a BACnet system compatible with existing University systems. All building controllers, application controllers, and all input/output devices shall communicate using the protocols and network standards as defined by ANSI/ASHRAE Standard 135-2001, BACnet. This system shall communicate with the University of Kentucky Facility Management’s existing BACnet head-end software using BACnet/IP at the tier 1 level and BACnet/MSTP at the tier 2 level. No gateways shall be used for communication to controllers installed under section. BACnet/MSTP or BACnet/IP shall be used for all other tiers of communication. No servers shall be used for communication to controllers installed under this section. If servers are required, all hardware and operating systems must be approved by the Facilities Management Controls Engineering Manager and/or the Facilities Management Information Technology Manager. All Building Automation Devices should be located behind the University firewall, but outside of the Medical Center Firewall and on the environmental VLAN. Provide all necessary hardware and software to meet the system’s functional specifications. Provide Protocol Implementation Conformance Statement (PICS) for Windows-based control software and every controller in system, including unitary controllers. These must be in compliance with Front End systems PICS and BIBBS and attached Tridium PICS and BIBBS.
    [Show full text]
  • High Performance Platforms
    High Performance Platforms Salvatore Orlando High Perfoamnce Computing - S. Orlando 1 Scope of Parallelism: the roadmap towards HPC • Conventional architectures are coarsely comprised of – processor, memory system, I/O • Each of these components presents significant performance bottlenecks. – It is important to understand each of these performance bottlenecks to reduce their effects • Parallelism addresses each of these components in significant ways to improve performance and reduce the bottlenecks • Applications utilize different aspects of parallelism, e.g., – data intensive applications utilize high aggregate memory bandwidth – server applications utilize high aggregate network bandwidth – scientific applications typically utilize high processing and memory system performance High Perfoamnce Computing - S. Orlando 2 Implicit Parallelism: Trends in Microprocessor Architectures • Microprocessor clock speeds have posted impressive gains over the past two decades (two to three orders of magnitude) – there are limits to this increase, also due to power consumption and heat dissipation • Higher levels of device integration have made available a large number of transistors – the issue is how best to transform these large amount of transistors into computational power • Single-core processors use these resources in multiple functional units and execute multiple instructions in the same cycle. • The precise manner in which these instructions are selected and executed provides impressive diversity in architectures. High Perfoamnce Computing - S. Orlando 3 ILP High Perfoamnce Computing - S. Orlando 4 Instruction Level Parallelism • Pipelining overlaps various stages of instruction execution to achieve performance • At a high level of abstraction, an instruction can be executed while the next one is being decoded and the next one is being fetched. • This is akin to an assembly line for manufacture of cars.
    [Show full text]
  • Multiprocessing Contents
    Multiprocessing Contents 1 Multiprocessing 1 1.1 Pre-history .............................................. 1 1.2 Key topics ............................................... 1 1.2.1 Processor symmetry ...................................... 1 1.2.2 Instruction and data streams ................................. 1 1.2.3 Processor coupling ...................................... 2 1.2.4 Multiprocessor Communication Architecture ......................... 2 1.3 Flynn’s taxonomy ........................................... 2 1.3.1 SISD multiprocessing ..................................... 2 1.3.2 SIMD multiprocessing .................................... 2 1.3.3 MISD multiprocessing .................................... 3 1.3.4 MIMD multiprocessing .................................... 3 1.4 See also ................................................ 3 1.5 References ............................................... 3 2 Computer multitasking 5 2.1 Multiprogramming .......................................... 5 2.2 Cooperative multitasking ....................................... 6 2.3 Preemptive multitasking ....................................... 6 2.4 Real time ............................................... 7 2.5 Multithreading ............................................ 7 2.6 Memory protection .......................................... 7 2.7 Memory swapping .......................................... 7 2.8 Programming ............................................. 7 2.9 See also ................................................ 8 2.10 References .............................................
    [Show full text]
  • K1DM3 Control System Software User's Guide
    K1DM3 Control System Software User's Guide William Deich University of California Observatories 07 Jan 2020 ver 3.7b Contents 1 Overview 6 1.1 Active Components of K1DM3..........................6 1.1.1 Drum....................................6 1.1.2 Swingarm..................................9 1.2 Position Summary................................. 13 1.3 Motion Controllers................................. 13 1.4 Software....................................... 14 1.4.1 Back-end Services............................. 14 1.4.2 End-User Applications........................... 15 1.5 K1DM3 Private Network.............................. 15 2 Starting, Stopping, Suspending Services 17 2.1 Starting/Stopping................................. 17 2.2 Suspending Dispatchers.............................. 19 2.3 Special No-Dock Engineering Version....................... 19 2.4 Periodic Restarts.................................. 20 3 Components, Assemblies, and Sequencers 21 3.1 Elementary Components.............................. 21 3.2 Compound Keywords............................... 22 3.3 Assemblies...................................... 22 3.4 Sequencers..................................... 23 3.5 The ACTIVATE Sequencer............................ 24 3.6 The M3AGENT Sequencer............................ 27 3.7 Monitoring Sequencer Execution......................... 27 4 Dispatcher Interfaces for Routine Operations 29 4.1 TCS Operations.................................. 31 4.2 M3AGENT..................................... 32 4.3 Hand Paddle...................................
    [Show full text]
  • Computer Structures for Distributed Systems Liam
    COMPUTER STRUCTURES FOR DISTRIBUTED SYSTEMS LIAM MAURICE CASEY C DOCTOR OF PHILOSOPHY UNIVERSITY OF EDINBURGH 1977. - ABSTRPCI: A building block approach to configuring large corruter. iEerns is attractive because the blocks, either primitive processors or small computers, are daily becoming cheaper and because this approach alloiis a close match of the pcwer required to the pciler supplied. This thesis addresses the design goal of an expandable system where there is no premium paid for a minimal configuration and the cost of extra units of capacity is constant. It is shoiin that a distributed system, a system of homogeneous canputers loosely coupled by a cartmunication subsystem, is likely to be the best approach to this design goal. Some consideration is given to the form of the canmunication subsystem but the rain research is directed to.ards the software organisation required to achieve efficient co-operation between the canputers constituting the distributed system. An organisation based on the domain structures of protection schenEs is found to have advantages. Hitherto dcirtain management using capabilities has been centred around systems with shared. primary memory. This is because central tables have been required to implement the capability rrechanism. A model is developed which, by restricting. the sharing of some items and providing a 'global object' managerrent scheme to cover essential sharing, enables central tables to be dispensed with and dcmain managenent to be distributed. The main goal in achieving this extension is to facilitate dynamic and efficient load sharing but the model could equally well be used to provide, in distributed systems, the protection normally associated with danains.
    [Show full text]
  • Stuart Elliot Madnick V37
    STUART ELLIOT MADNICK V37 John Norris Maguire Professor of Information Technology Sloan School of Management and Professor of Engineering Systems Sloan School of Engineering Massachusetts Institute of Technology TABLE OF CONTENTS EDUCATION ............................................................................................. 1 PRINCIPAL FIELD OF INTEREST ........................................................ 1 NAME AND RANK OF OTHER FACULTY IN SAME FIELD ......... 1 1. SUMMARY OF NON-MIT EXPERIENCE ....................................... 2 2. SUMMARY OF MIT APPOINTMENTS ........................................... 4 3. COMMITTEES ...................................................................................... 5 4. CONSULTING ACTIVITIES .............................................................. 8 5. PROFESSIONAL ACTIVITIES ............................................................ 11 6. PROFESSIONAL SOCIETIES ............................................................. 14 7. SUBJECTS TAUGHT ............................................................................ 15 8. THESIS SUPERVISION ....................................................................... 19 9. RESEARCH PROJECT SUPERVISION (Principal Investigator or co-PI) .... 28 10. PUBLICATIONS ................................................................................ 32 10.1 BOOKS AND MONOGRAPHS ........................................................................................................ 32 10.2 BOOK CHAPTERS ...........................................................................................................................
    [Show full text]
  • DOWNLOAD the Labmart 2013 Catalog
    Alconox Detergents 24 Bags 10 Balances 11-17, 70 Welcome To Baths 35 Beakers 3, 60 About Us Benchtop Covers 23 For more than 160 years, The LabMart® has offered NEW and INNOVATIVE Biotechnology 68 products at affordable prices! We look forward to suppling you with all Bottles 3, 9, 53-57 your lab needs in the future & thank you for your past patronage. Brushes 22 Buffers, pH 51 Burners 38 Contact Us Carts 22 Call: 800-684-1234 Fax: 908-561-3002 Calculators 39 Online: www.labmart.com E-mail: [email protected] Centrifuges & Accessories 18-21 Mail: J&H Berge/The LabMart® Cleaning 22-24, 33 4111 South Clinton Avenue PO Box 310 Corning Glassware Sale 3-7 South Plainfield, NJ 07080 Cryoware 25-26 Cylinders 4, 55 This Edition Desiccator 27 This edition offers our best products at the best prices. WE WENT GREEN and cut Dishes, Glass / Petri 7, 69 back on resources to reduce our carbon footprint. We still have a full line catalog, Dispensers 44, 54 just contact us and will will be happy to send it to you. And of course, our online Disposal, Safety 8 catalog (www.labmart.com) lists every product and chemical we offer. If you don’t Electrophoresis 27 see it or can’t find it, call us. We can cross-reference any competitors’ product number Electrodes, pH 52 Filtration / Paper 28-30 or description and beat their price. Flasks 5-7, 69 Food Prep / Handling 59, 70-71 New and Free Stuff Funnels 60 We have packed this catalog with the latest and best products Gloves 31-34 produced by leading manufacturers.
    [Show full text]
  • Some Computer Organizations and Their Effectiveness Michael J Flynn
    Some Computer Organizations and Their Effectiveness Michael J Flynn IEEE Transactions on Computers. Vol. c-21, No.9, September 1972 Introduction Attempts to codify a computer have been from three points of view ! Automata Theoritic or microscopic ! Individual Problem Oriented ! Global or Statistical Microscopic View: ! Relationships are described exhaustively ! All parameters are considered irrespective of their importance in the problem Individual Poblem Oriented: ! Compare Computer Organizations based on their relative performances in a peculiar environment ! Such comparisons are limited because of their ad hoc nature Global or Statistical Comparisons: ! Made on basis of statistical tabulations of relative performances on various jobs or mixture of jobs Drawback: The analysis is of little consequence in the system as the base premise on which they were based has been changed Objective of this paper: To reexamine the principal interactions within a processor system so as to generate a more “macroscopic” view, yet without reference to a particular environment Limitations: 1. I/O problems are not treated as a limiting resource 2. No assessment of particular instruction set 3. In spite of the fact that either (1) or (2) will dominate the assessment we will use the notion of efficiency Classification: Forms of Computing Systems Stream : sequence of items (instructions or data) Based on the magnitude of interactions of the instructions and data streams, machines are classified as 1. SISD - Single Instruction, Single Data Stream 2. SIMD - Single Instruction, Multiple Data Stream 3. MISD - Multiple Instruction, Single Data Stream 4. MIMD - Multiple Instruction, Multiple Data Stream Let us formalize the stream view of Computing in order to obtain a better insight.
    [Show full text]
  • Intel Thread Building Blocks, Part III
    Intel Thread Building Blocks, Part III SPD course 2014-15 Massimo Coppola 12/05/2015 MCSN – M. Coppola – Strumenti di programmazione per sistemi paralleli e distribuiti 1 Parallel_do template< typename InputIterator, typename Body> void parallel_do( InputIterator first, InputIterator last, Body body [, task_group_context& group] ); • Parallel_do has two forms, both using the object- oriented syntax • Applies a function object body to a specified interval – The body can add additional tasks dynamically – Iterator is a standard C++ one, however • a purely serial input iterator is a bottleneck • It is better to use iterators over random-access data structures • Replaces the deprecated parallel_while MCSN – M. Coppola – Strumenti di programmazione per sistemi paralleli e distribuiti 2 Parallel_do Template< typename Container, typename Body> void parallel_do( Container c, Body body [, task_group_context& group] ); • Shorter equivalent for processing a whole container – iterators are provided by the Container type – equivalent to passing std::begin() and std:: end() with the other syntax MCSN – M. Coppola – Strumenti di programmazione per sistemi paralleli e distribuiti 3 Computing and adding items in a do • The body class need to compute on the template T type e.g. operator() – Body also needs a copy constructor and a destroyer B::operator()( T& item, parallel_do_feeder<T>& feeder ) const B::operator()( T& item ) const • Adding items depends on the signature of the Body operator() -- two possible signatures – First signature, with extra parameter, allows each item to call a feeder callback to add more items dinamically à e.g. allows dynamically bound parallel do, feedback, divide & conquer – Second signature means the do task set is static – You can’t define both! MCSN – M.
    [Show full text]
  • Grid Computing
    Grid computing This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (July 2010) This article needs attention from an expert on the subject. See the talk page for details. Consider associating this request with a WikiProject. (July 2010) Grid computing is a term referring to the combination of computer resources from multiple administrative domains to reach a common goal. The grid can be thought of as a distributed system with non-interactive workloads that involve a large number of files. What distinguishes grid computing from conventional high performance computing systems such as cluster computing is that grids tend to be more loosely coupled, heterogeneous, and geographically dispersed. Although a grid can be dedicated to a specialized application, it is more common that a single grid will be used for a variety of different purposes. Grids are often constructed with the aid of general-purpose grid software libraries known as middleware. Grid size can vary by a considerable amount. Grids are a form of distributed computing whereby a ―super virtual computer‖ is composed of many networked loosely coupled computers acting together to perform very large tasks. Furthermore, ―distributed‖ or ―grid‖ computing, in general, is a special type of parallel computing that relies on complete computers (with onboard CPUs, storage, power supplies, network interfaces, etc.) connected to a network (private, public or the Internet) by a conventional network interface, such as Ethernet. This is in contrast to the traditional notion of a supercomputer, which has many processors connected by a local high- speed computer bus.
    [Show full text]
  • Multithreading Contents
    Master Program (Laurea Magistrale) in Computer Science and Networking High Performance Computing Systems and Enabling Platforms Marco Vanneschi Multithreading Contents • Main features of explicit multithreading architectures • Relationships with ILP • Relationships with multiprocessors and multicores • Relationships with network processors • GPUs MCSN - M. Vanneschi: High Performance Computing Systems and Enabling Platforms 2 Basic principle • Concurrently execute instructions of different threads of control within a single pipelined processor • Notion of thread in this context: – NOT “software thread” as in a multithreaded OS, – Hardware-firmware supported thread: an independent execution sequence of a (general- purpose or specialized) processor: • A process • A compiler generated thread • A microinstruction execution sequence • A task scheduled to a processor core in a GPU architecture • Even an OS thread (e.g. POSIX) • In a multithreaded architecture, a thread is the unit of instruction scheduling for ILP – Neverthless, multithreading might be a powerful mechanism for multiprocessing too (i.e., parallelism at process level in multiprocessors architectures) • (Unfortunately, there is a lot of confusion around the word “thread”, which is used in several contexts often with very different meanings) MCSN - M. Vanneschi: High Performance Computing Systems and Enabling Platforms 3 Basic architecture • More independent program counters • Tagging mechanism (unique identifiers) to distinguish instructions of different threads within the pipeline • Efficient mechanisms for thread switching: very efficient context switching, from zero to very few clock cycles • Multiple register sets Request DM – (not always statically allocated) IM Queue Interleave the execution of instructions of different threads in the same pipeline. IU Pipelined EU Request FIXED RG ICIC Queue FIXED RG Try “to fill” the ICIC FIXED RG latencies as much as FLOAT RG FLOAT RG possible.
    [Show full text]
  • Minimization of Supervisor Conflict For
    MINIMIZATION OF SUPERVISOR CONFLICT FOR MULTIPROCESSOR COMPUTER SYSTEMS A THESIS Presented to The Faculty of the Division of Graduate Studies and Research by Randy J. Raynor In Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy in the School of Information and Computer Science Georgia Institute of Technology June, 1974 MINIMIZATION OF SUPERVISOR CONFLICT FOR MULTIPROCESSOR COMPUTER SYSTEMS Approved: jifclri M. Gwyimf" Jr j/, ChaiAan r r \-~ - —- - , i Michael D. Kelly <T Donovan B. Young\I Date approved by Chairman: S/ZSyyCi- ii ACKNOWLEDGMENTS I would first like to thank my thesis advisor, Dr. John Gwynn, for his support, ideas, and constructive criticism throughout my grad­ uate career. Our numerous discussions have been of inestimable value to me. The members of my guidance and reading committees, Drs. Robert Cooper, Michael Kelly, and Donovan Young deserve my thanks for their continued support and encouragement during my research and for their careful reading of my thesis drafts. I would also like to thank Dr. Donald Chand of Georgia State University and Dr. James Browne of The University of Texas at Austin for reading and commenting on this thesis. A note of thanks goes to Mr. Bill Brown of Univac and to the Office of Computing Services of Georgia Tech for their assistance in setting up the special use of the Univac computer. This research was partially supported by NSF Grant GN-655. Finally, special thanks are given to my wife, Vickie. Her assistance, patience, and impatience were an essential contribution to the completion of this thesis. Ill TABLE OF CONTENTS Page ACKNOWLEDGMENTS ±± LIST OF TABLES v LIST OF ILLUSTRATIONS vi SUMMARY vii Chapter I.
    [Show full text]