DOCSLIB.ORG

The Requirements of I/O OS Basics: I/O in a Picture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Requirements of I/O OS Basics: I/O in a Picture The Requirements of I/O CS162 • So far in this course: Operating Systems and – We have learned how to manage CPU and memory Systems Programming Lecture 16 • What about I/O? – Without I/O, computers are useless (disembodied brains?) General I/O – But… thousands of devices, each slightly different » How can we standardize the interfaces to these devices? October 24th, 2016 – Devices unreliable: media failures and transmission errors Prof. Anthony D. Joseph » How can we make them reliable??? http://cs162.eecs.Berkeley.edu – Devices unpredictable and/or slow » How can we manage them if we don’t know what they will do or how they will perform? 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.2 OS Basics: I/O In a Picture Threads Read / Address Spaces Windows Write wires Processes Files Sockets Processor OS Hardware Virtualization Core I/O Software Controllers Hardware ISA Memory interrupts Secondary Read / DMA transfer Write Main Secondary Storage Core Processor Protection Memory Storage (Disk) Boundary (DRAM) OS (SSD) Ctrlr Networks storage • I/O devices you recognize are supported by I/O Controllers • Processors accesses them by reading and writing IO registers as if they were memory Displays – Write commands and arguments, read status and results Inputs 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.3 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.4 Operational Parameters for I/O Kernel Device Structure • Data granularity: Byte vs. Block The System Call Interface – Some devices provide single byte at a time (e.g., keyboard) – Others provide whole blocks (e.g., disks, networks, etc.) Process Memory Device Filesystems Networking Management Management Control • Access pattern: Sequential vs. Random Concurrency, Virtual Files and dirs: TTYs and Connectivity – Some devices must be accessed sequentially (e.g., tape) multitasking memory the VFS device access File System – Others can be accessed “randomly” (e.g., disk, cd, etc.) Types Network » Fixed overhead to start transfers Architecture Subsystem Memory Device Dependent – Some devices require continual monitoring Manager Control Code Block IF drivers – Others generate interrupts when they need service Devices • Transfer Mechanism: Programmed IO and DMA 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.5 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.6 The Goal of the I/O Subsystem Want Standard Interfaces to Devices • Block Devices: e.g. disk drives, tape drives, DVD-ROM • Provide Uniform Interfaces, Despite Wide Range of Different – Access blocks of data Devices – Commands include open(), read(), write(), seek() – This code works on many different devices: – Raw I/O or file-system access FILE%fd =%fopen("/dev/something", "rw"); – Memory-mapped file access possible for%(int i =%0;%i <%10;%i++)%{ • Character Devices: e.g. keyboards, mice, serial ports, some USB fprintf(fd,%"Count%%d\n",%i); devices } – Single characters at a time close(fd); – Commands include get(), put() – Why? Because code that controls devices (“device driver”) – Libraries layered on top allow line editing implements standard interface • Network Devices: e.g. Ethernet, Wireless, Bluetooth • We will try to get a flavor for what is involved in actually – Different enough from block/character to have own interface controlling devices in rest of lecture – Unix and Windows include socket interface – Can only scratch surface! » Separates network protocol from network operation » Includes select()%functionality – Usage: pipes, FIFOs, streams, queues, mailboxes 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.7 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.8 How Does User Deal with Timing? Chip-scale Features of 2011 x86 (SandyBridge) • Blocking Interface: “Wait” • Significant pieces: – When request data (e.g. read() system call), put process to sleep until data is ready – Four OOO cores » New Advanced Vector eXtensions (256-bit FP) – When write data (e.g. write() system call), put process to sleep until device is ready for data » Special purpose instructions: AES, Galois-Field mult • Non-blocking Interface: “Don’t Wait” » 4 µ-ops/cycle – Returns quickly from read or write request with count of bytes – Integrated GPU, System Agent (Mem, Fast I/O) successfully transferred – Shared L3 cache divided in 4 banks – Read may return nothing, write may write nothing – On-chip Ring bus network • Asynchronous Interface: “Tell Me Later” » High-BW access to L3 Cache – When request data, take pointer to user’s buffer, return immediately; • Integrated I/O later kernel fills buffer and notifies user – Integrated memory controller (IMC) – When send data, take pointer to user’s buffer, return immediately; later » Two independent channels of DDR3 DRAM kernel takes data and notifies user – High-speed PCI-Express (for Graphics cards) – DMI Connection to SouthBridge (PCH) 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.9 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.10 SandyBridge I/O: PCH Chip-scale Features of 2015 x86 (Sky Lake) • Platform Controller Hub • Significant pieces: – Used to be – Four OOO cores with deeper buffers “SouthBridge,” but no » New Intel MPX (Memory Protection Extensions) “NorthBridge” now » New Intel SGX (Software Guard Extensions) – Connected to processor » Issue up to 6 µ-ops/cycle with proprietary bus – Integrated GPU, System Agent (Mem, Fast I/O) » Direct Media Interface – Larger shared L3 cache with on-chip ring bus • Types of I/O on PCH: » 2 MB/core instead of 1.5 MB/core – USB, Ethernet » High-BW access to L3 Cache – Audio, BIOS support • Integrated I/O – More PCI Express (lower – Integrated memory controller (IMC) speed than on Processor) SandyBridge » Two independent channels of DDR3L/DDR4 DRAM – SATA (for Disks) System Configuration – High-speed PCI-Express (for Graphics cards) – DMI Connection to SouthBridge (PCH) 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.11 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.12 Sky Lake I/O: PCH Modern I/O Systems • Platform Controller Hub – Used to be “SouthBridge,” but no “NorthBridge” now – Connected to processor with proprietary bus » Direct Media Interface • Types of I/O on PCH: network – USB, Ethernet – Thunderbolt 3 – Audio, BIOS support – More PCI Express (lower Sky Lake speed than on Processor) System Configuration – SATA (for Disks) 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.13 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.14 Example Device-Transfer Rates in Mb/s Example: PCI Architecture (Sun Enterprise 6000) Memory RAM CPU Bus Host Bridge PCI #0 ISA Bridge PCI Bridge PCI #1 ISA PCI Slots USB SATA Controller Scanner Controller Controller Legacy Root Devices Hub Hard DVD Disk 10m ROM Hub Webcam • Device Rates vary over 12 orders of magnitude !!! – System better be able to handle this wide range Mouse Keyboard – Better not have high overhead/byte for fast devices! – Better not waste time waiting for slow devices 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.15 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.16 Administrivia Recall: Internet of Things Botnets • Hackers take over Internet of Things devices: • Midterm 2 TOMORROW on Tue 10/25 6:30-8PM – Mirai (233,000 infected IoT devices) and Bashlight (963,000) – All topics up to and including Lecture 15 • Responsible for 620 Gb/s attack against Brian Krebs’ website » Focus will be on Lectures 9 – 15 and associated readings – Largest Distributed Denial of Service attack ever!! » Projects 1 & 2, Homework 0 – 2 – Closed book with 2 pages of hand-written notes both sides • Followed a few days later by 1.1 Tb/s attack against French – Room assignments by last name: cloud and web hosting provider » 10 Evans (A – K), 1 LeConte (L – S), 60 Evans (T – Z) – Largest Distributed Denial of Service attack ever!! – Roughly 145,000 Internet attached cameras • IoT devices compromised using default and hardcoded passwords 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.17 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.18 Friday Oct 21 2016 IoT Attack Solutions? • Legislative? – Criminal charges – already exists but how to identify who is responsible? – Mandatory recall – how to identify white label devices? how to enforce? » Hangzhou Xiongmai Tech hardcoded passwords into camera boards (announced recall? on Monday 10/24) – Fines – who should be fined? – ISPs block users – huge customer support nightmare… • Technical? – Blocking IP addresses – attack used spoofed IP addresses – Create a “good” worm to patch vulnerable devices – how would users • IoT attack against DNS servers run by Dyn Corp gain access to their devices? Some devices have hardcoded passwords – 3 attack waves: 7:00 am ET, 12:00pm ET, (third attack blocked) • UL Label? – Mirai botnet spoofed (faked) 10Ms of IP addr (maybe 50k hosts) – Develop industry standards and best practices » TCP SYN floods to DNS servers port 53, also DNS prepend attack – Mandate thorough security testing of IoT devices – Affected Twitter, SoundCloud, Spotify, Reddit, Amazon, Netflix, PayPal, Airbnb, Reddit, Etsy, New York Times, 10k+ more sites … 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.19 10/24/16 Joseph CS162 ©UCB Fall 2016 Lec 16.20 How does the processor actually talk to the device? Processor Memory Bus Regular Memory CPU Bus Bus Adaptor Adaptor Device Address + Controller Other Devices Data Bus Hardware Interrupt or Buses Interface Controller Controller Interrupt Request read write Addressable • CPU interacts with a Controller control Memory – Contains a set of registers that status and/or can be read and written Registers Queues – May contain memory for request (port 0x20) Memory Mapped queues or bit-mapped images Region: 0x8f008020
Load more

Recommended publications
  • Sun Server X2-8 System Architecture White Paper
    An Oracle White Paper July 2011; Revised July 2012 Oracle¶V Sun Server X2-8 System Architecture 2UDFOH¶V6XQServer X2-8 System Architecture Introduction ....................................................................................... 1 2UDFOH¶V6XQServer X2-8 System ..................................................... 2 The Sun Server X2-8 System Architecture ........................................ 5 CPU Module .................................................................................. 6 Memory ......................................................................................... 9 PCI Express ExpressModule ....................................................... 10 Network Express Module ............................................................. 12 Internal Drives ............................................................................. 13 Chassis and External Interfaces .................................................. 13 Cooling ........................................................................................ 14 Power .......................................................................................... 15 System Management ....................................................................... 16 ILOM Service Processor .............................................................. 16 SNMP Support ............................................................................ 20 ® Oracle Enterprise Manager Ops Center Software ...................... 21 A Choice of Operating Systems ......................................................
    [Show full text]
  • A100 40GB Pcie Product Brief
    NVIDIA A100 40GB PCIe GPU Accelerator Product Brief PB-10137-001_v03 | September 2020 Document History PB-10137-001_v03 Version Date Authors Description of Change 01 September 14, 2020 AS, SM Initial Release 02 September 15, 2020 AS, SM Removed “confidential” markings 03 September 22, 2020 AS, SM Updated naming convention for vCompute Server to NVIDIA Virtual Compute Server (Table 3) NVIDIA A100 40GB PCIe GPU Accelerator PB-10137-001_v03 | ii Table of Contents Overview ............................................................................................................................ 1 Specifications.................................................................................................................... 3 Product Specifications ......................................................................................................3 Multi-Instance GPU Support..............................................................................................5 Environmental and Reliability Specifications ......................................................................5 Airflow Direction Support ................................................................................................ 6 Product Features.............................................................................................................. 7 Form Factor .....................................................................................................................7 NVLink Bridge Support .....................................................................................................8
    [Show full text]
  • Hypertransport
    HyperTransport Dennis Vega Ryan Rawlins What is HyperTransport (HT)? • A point‐to‐point interconnect technology that links processors to other processors, coprocessors, I/O controllers, and peripheral controllers. How Does HyperTransport Work? • Point‐to‐Point Link Topology – Structure of the link • Electrical/Signal Characteristics – Physical Characteristics of the signal interface • Packet Protocols – How data is organized and transferred across the link Point‐to‐Point Link Topology • Employs dual, unidirectional data links with a concise signal set using 1.2V LVDS • The daisy‐chain topology includes a required “host” device and at least one end‐point or “cave”. • Optional: – “Tunnel” devices that connect the link to other HT devices – “Bridge” devices that interface with non‐HT interconnect technologies. Point‐to‐Point Link Topology Electrical/Signal Characteristics • The unidirectional links include a data path, one or more clock lines, and a single control line. Electrical/Signal Characteristics • Each LVDS line is implemented by means of a balanced or differential line – Prevents electrical noise from affecting and potentially corrupting the signal detection process • The HT architectures can be implemented with fewer PCB traces and less signal shielding precautions due to the lower number of signal lines for a given bandwidth. Electrical/Signal Characteristics Packet Protocols • Command information is transferred as a control packet of 4 or 8 bytes. • HT data traffic is delivered as a data packet that consists of an 8‐ or 12‐ byte header followed by a 4‐64 byte data payload. • For a write request, there is an 8‐byte control packet followed by the data packet. • For a read request, there is an 8‐byte control packet, followed by a 4‐bytes read response packet, and followed by the data packet.
    [Show full text]
  • Intel® Xeon® Processor E7-4800/8800 V3 Product Families Datasheet Volume1: EMTS, May 2015 Table of Contents
    Intel® Xeon® Processor E7- 4800/8800 v3 Product Families Datasheet - Volume 1: Electrical, Mechanical and Thermal May 2015 Reference Number: 332314-001US Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Learn more at Intel.com, or from the OEM or retailer. No computer system can be absolutely secure. Intel does not assume any liability for lost or stolen data or systems or any damages resulting from such losses. You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548- 4725 or by visiting www.intel.com/design/literature.htm. Intel and the Intel logo are trademarks of Intel Corporation in the U.S.
    [Show full text]
  • The Requirements of I/O OS Basics: I/O in a Picture
    The Requirements of I/O CS162 • So far in this course: Operating Systems and – We have learned how to manage CPU and memory Systems Programming Lecture 16 • What about I/O? – Without I/O, computers are useless (disembodied brains?) General I/O – But… thousands of devices, each slightly different » How can we standardize the interfaces to these devices? October 18th, 2017 – Devices unreliable: media failures and transmission errors Neeraja J. Yadwadkar » How can we make them reliable??? http://cs162.eecs.Berkeley.edu – Devices unpredictable and/or slow » How can we manage them if we don’t know what they will do or how they will perform? 10/18/17 CS162 © UCB Spring 2017 Lec 16.2 OS Basics: I/O In a Picture Threads Read / Address Spaces Windows Write wires Processes Files Sockets Processor OS Hardware Virtualization Core I/O Software Controllers Hardware ISA Memory interrupts Secondary Read / DMA transfer Write Main Secondary Storage Processor Protection Core Memory Storage (Disk) Boundary (DRAM) (SSD) OS Ctrlr Networks storage • I/O devices you recognize are supported by I/O Controllers • Processors accesses them by reading and writing IO registers as if they were memory Displays – Write commands and arguments, read status and results Inputs 10/18/17 CS162 © UCB Spring 2017 Lec 16.3 10/18/17 CS162 © UCB Spring 2017 Lec 16.4 Operational Parameters for I/O Kernel Device Structure • Data granularity: Byte vs. Block The System Call Interface – Some devices provide single byte at a time (e.g., keyboard) – Others provide whole blocks (e.g., disks, networks, etc.) Process Memory Device Filesystems Networking Management Management Control • Access pattern: Sequential vs.
    [Show full text]
  • Hypertransport System Architecture / Mindshare, Inc., Jay Trodden & Don Anderson
    world-class technical training Are your company’s technical training needs being addressed in the most effective manner? MindShare has over 25 years experience in conducting technical training on cutting-edge technologies. We understand the challenges companies have when searching for quality, effective training which reduces the students’ time away from work and provides cost-effective alternatives. MindShare offers many fl exible solutions to meet those needs. Our courses are taught by highly-skilled, enthusiastic, knowledgeable and experienced instructors. We bring life to knowledge through a wide variety of learning methods and delivery options. training that fi ts your needs MindShare recognizes and addresses your company’s technical training issues with: • Scalable cost training • Customizable training options • Reducing time away from work • Just-in-time training • Overview and advanced topic courses • Training delivered effectively globally • Training in a classroom, at your cubicle or home offi ce • Concurrently delivered multiple-site training MindShare training courses expand your technical skillset 2 PCI Express 2.0 ® 2 Serial Attached SCSI (SAS) 2 Intel Core 2 Processor Architecture 2 DDR2/DDR3 DRAM Technology 2 AMD Opteron Processor Architecture 2 PC BIOS Firmware 2 Intel 64 and IA-32 Software Architecture 2 High-Speed Design 2 Intel PC and Chipset Architecture 2 Windows Internals and Drivers 2 PC Virtualization 2 Linux Fundamentals 2 USB 2.0 ... and many more. 2 Wireless USB All courses can be customized to meet your 2 Serial
    [Show full text]
  • PCI Express and Its Interface to Storage Architectures Ron Emerick Oracle Corporation
    PCI Express and Its Interface to Storage Architectures Ron Emerick Oracle Corporation 20122013 Storage Developer Conference. © InsertOracle Your Corporation. Company All Name. Rights All Reserved. Rights Reserved. Abstract PCI Express and Its Interface to Storage Architectures • PCI Express Gen2 and Gen3, IO Virtualization, FCoE, SSD and PCI Express Storage Devices are here. What are PCI Express Storage Devices – Why do you care? This session describes PCI Express, Single Root and the implications on FCoE, SSD, PCI Express Storage Devices and impacts of all these changes on storage connectivity, storage transfer rates. The potential implications to the Storage Industry and Data Center Infrastructure will also be discussed. Knowledge of PCIe Architecture, PCIe Roadmap, System Root Complexes Expected Industry Roll Out of latest IO Technology and required Root Complex capabilities Implications and Impacts of FCoE, SSD and NVMe Devices to storage Connectivity What Might the Data Center Look Like? 20122013 Storage Developer Conference. © InsertOracle Your Corporation. Company All Name. Rights All Reserved. Rights Reserved. 2 Agenda • IO Architectures PCI Express is Here to Stay PCI Express Tutorial New PCI Express based architectures How does PCI Express work • IO Evolving Beyond the Motherboard Serial Interfaces InfniBand, 10 GbE, 40 GbE, 100 GbE PCIe IO Virtualization Review of PCI Express IO Virtualization Impact of PCI Express on Storage 20122013 Storage Developer Conference. © InsertOracle Your Corporation. Company All Name. Rights All Reserved. Rights Reserved. 3 I/O Architecture • PCI provides a solution to connect processor to IO Standard interface for peripherals – HBA, NIC etc Many man years of code developed based on PCI Would like to keep this software investment • Performance keeps pushing IO interface speed PCI/PCI-X 33 Mhz, 66 Mhz to 133 Mhz PCI-X at 266 Mhz released Problems at PCI-X 512 Mhz with load and trace length • Parallel interfaces are almost all replaced • Parallel PCI has migrated to serial PCI Express 20122013 Storage Developer Conference.
    [Show full text]
  • Project Olympus Intel BIOS Specification
    Project Olympus Intel® Xeon® Scalable Processor BIOS Specification Author: Mallik Bulusu, Principal Firmware Engineering Manager, Microsoft 2 November 1, 2017 Revision History Date Description 11/1/17 Version 1.0 http://opencompute.org 1 © 2017 Microsoft Corporation. As of November 1, 2017, the following persons or entities have made this Specification available under the Open Web Foundation Final Specification Agreement (OWFa 1.0), which is available at http://www.openwebfoundation.org/legal/the- owf-1-0-agreements/owfa-1-0 Microsoft Corporation. You can review the signed copies of the Open Web Foundation Agreement Version 1.0 for this Specification at Project Olympus License Agreements, which may also include additional parties to those listed above. Your use of this Specification may be subject to other third party rights. THIS SPECIFICATION IS PROVIDED "AS IS." The contributors expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the Specification. The entire risk as to implementing or otherwise using the Specification is assumed by the Specification implementer and user. IN NO EVENT WILL ANY PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS SPECIFICATION OR ITS GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. CONTRIBUTORS AND LICENSORS OF THIS SPECIFICATION MAY HAVE MENTIONED CERTAIN TECHNOLOGIES THAT ARE MERELY REFERENCED WITHIN THIS SPECIFICATION AND NOT LICENSED UNDER THE OWF CLA OR OWFa.
    [Show full text]
  • An Introduction to the Intel Quickpath Interconnect
    An Introduction to the Intel® QuickPath Interconnect January 2009 Document Number: 320412-001US Notice: This document contains information on products in the design phase of development. The information here is subject to change without notice. Do not finalize a design with this information. INFORMATIONLegal Lines and Disclaimers IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See http://www.intel.com/products/processor_number for details. Products which implement the Intel® QuickPath Interconnect may contain design defects or errors known as errata which may cause the product to deviate from published specifications.
    [Show full text]
  • WP350 (V1.2) October 28, 2014
    White Paper: UltraScale and Virtex-7 FPGAs R WP350 (v1.2) October 28, 2014 Understanding Performance of PCI Express Systems By: Jason Lawley PCI Express® technology, which is a serialized point-to-point interconnect protocol, provides a high-bandwidth scalable solution for reliable data transport. Although PCI Express system transfer rates can seem extremely fast compared to those of its predecessor, PCI, users should understand the difference in raw bit rate movement versus data transfer performance. This white paper explores factors of the PCI Express technology that can impact performance. It also provides guidance on how to estimate the performance of a system. This white paper includes information on PCI Express Gen 3, available in Xilinx UltraScale™ and Virtex®-7 XT/HT devices. © Copyright 2008–2014 Xilinx, Inc. Xilinx, the Xilinx logo, Artix, ISE, Kintex, Spartan, Virtex, Vivado, Zynq, and other designated brands included herein are trademarks of Xilinx in the United States and other countries. PCI, PCIe, and PCI Express are trademarks of PCI-SIG and used under license. All other trademarks are the property of their respective owners. WP350 (v1.2) October 28, 2014 www.xilinx.com 1 R Performance Defined Performance Defined The specified maximum transfer rate of Generation 1 (Gen 1) PCI Express systems is 2.5 Gb/s; Generation 2 (Gen 2) PCI Express systems, 5.0 Gb/s; and Generation 3 (Gen 3) PCI Express systems, 8.0 Gb/s. These rates specify the raw bit transfer rate per lane in a single direction and not the rate at which data is transferred through the system.
    [Show full text]
  • Intel(R) X38 Chipset External Design Specification
    Intel® 3200 and 3210 Chipset Datasheet — For the Intel® 3200 and 3210 Chipset Memory Controller Hub (MCH) November 2007 Document Number: 318463-001 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The Intel® 3200/3210 Memory Controller Hub (MCH) may contain design defects or errors known as errata, which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. I2C is a two-wire communications bus/protocol developed by Philips. SMBus is a subset of the I2C bus/protocol and was developed by Intel.
    [Show full text]
  • California State University, Northridge Pcie Configuration for Data Transfer at Rate of 2.5-Giga Bytes Per Second (Gbps): for Da
    CALIFORNIA STATE UNIVERSITY, NORTHRIDGE PCIE CONFIGURATION FOR DATA TRANSFER AT RATE OF 2.5-GIGA BYTES PER SECOND (GBPS): FOR DATA ACQUISITION SYSTEM A graduate project submitted in partial fulfillment of the requirements For the degree of Master of Science in Electrical Engineering By Avani Dave May 2013 The graduate project of Avani Dave is approved: Dr. Emad El Wakil Date Dr. Somnath Chattopadhayay Date Dr. Nagi El Naga, Chair Date California State University, Northridge ii ACKNOWLEDGEMENT I wish to express my appreciation to those who have served on my graduate project. Firstly, I would like to thank Dr. Nagi El Naga for his valuable advice and guidance throughout my project. His constant support and encouragement has helped me learn a great deal all through the project. He was instrumental in providing not only all the guidance but also inspiration that I needed. I also wish to acknowledge special appreciation to Information and Technology Department’s Mr. Emil Henry and Mr. Armando Tellez for their help and support for driver’s installations. Special thanks to Dr. Somnath Chattopadhyay and Dr. Emad El wakil for their valuable comments on my work. I also wish to acknowledge special appreciation and thanks to the best and brightest engineers of Xilinx help and supports, who have helped me throughout my project. Their input, comments and guidance helped immensely in learning the finer details of the subject, grasping new ways of learning concepts and successfully completing this project. Finally, the patience and support from my parents, family and friends has been enormously important to me while I have been engaged in the graduate project.
    [Show full text]