Computer Hardware

Total Page：16

File Type：pdf, Size：1020Kb

COMPUTER HARDWARE A computer consists of two broad categories of components: hardware and software. Computer hardware includes all of the physical components that make up the system unit plus other devices connected to it. These connected devices are referred to as peripheral devices because they are outside, or peripheral to, the computer. Examples include a monitor, keyboard, mouse, hard disk drive, camera, and printer. Some peripheral devices, such as the monitor and hard disk drive, are essential components of a personal computer system. Categories of hardware devices include the system unit, input devices, output devices, storage devices, and communication devices. System Unit The system unit is a relatively small plastic or metal cabinet that houses the electronic components, which process data into information. Inside the cabinet, the main circuit board, called the motherboard, provides for the installation and connection of other electronic components. Once installed on the motherboard, the components can communicate with each other, thereby allowing the processing of data into information. The motherboard has two components, the central processing unit (CPU), also called the microprocessor (or simply processor), and the internal memory. The processor consists of one or more electronic chips that read, interpret, and execute instructions that operate the computer and perform specific computing tasks. When a program is executed, the processor temporarily stores the program’s instructions and the data needed for the instructions into the computer’s memory. Memory, also called primary storage, consists of small electronic chips that provide temporary storage for instructions and data during processing. Input Devices An input device is a hardware device that allows users to enter program instructions, data, and commands into a computer. The program or application being used determines the type of input device needed. Common input devices are the keyboard, mouse, and microphone. Output Devices An output device is a device that makes information available to the user. Popular output devices include display screens (monitors), printers, television screens, and speakers. Some output devices, such as a printer, produce output in hard copy (tangible) form, such as on paper or plastic. Other output devices, such as a monitor, produce output in soft copy (intangible) form that can be viewed but not physically handled. .

Copy Link

Recommended publications

Supercomputing in Plain English: Overview
Supercomputing in Plain English An Introduction to High Performance Computing Part I: Overview: What the Heck is Supercomputing? Henry Neeman, Director OU Supercomputing Center for Education & Research Goals of These Workshops To introduce undergrads, grads, staff and faculty to supercomputing issues To provide a common language for discussing supercomputing issues when we meet to work on your research NOT: to teach everything you need to know about supercomputing – that can’t be done in a handful of hourlong workshops! OU Supercomputing Center for Education & Research 2 What is Supercomputing? Supercomputing is the biggest, fastest computing right this minute. Likewise, a supercomputer is the biggest, fastest computer right this minute. So, the definition of supercomputing is constantly changing. Rule of Thumb: a supercomputer is 100 to 10,000 times as powerful as a PC. Jargon: supercomputing is also called High Performance Computing (HPC). OU Supercomputing Center for Education & Research 3 What is Supercomputing About? Size Speed OU Supercomputing Center for Education & Research 4 What is Supercomputing About? Size: many problems that are interesting to scientists and engineers can’t fit on a PC – usually because they need more than 2 GB of RAM, or more than 60 GB of hard disk. Speed: many problems that are interesting to scientists and engineers would take a very very long time to run on a PC: months or even years. But a problem that would take a month on a PC might take only a few hours on a supercomputer. OU Supercomputing
[Show full text]
Computer Hardware Architecture Lecture 4
Computer Hardware Architecture Lecture 4 Manfred Liebmann Technische UniversitätMünchen Chair of Optimal Control Center for Mathematical Sciences, M17 [email protected] November 10, 2015 Manfred Liebmann November 10, 2015 Reading List • Pacheco - An Introduction to Parallel Programming (Chapter 1 - 2) { Introduction to computer hardware architecture from the parallel programming angle • Hennessy-Patterson - Computer Architecture - A Quantitative Approach { Reference book for computer hardware architecture All books are available on the Moodle platform! Computer Hardware Architecture 1 Manfred Liebmann November 10, 2015 UMA Architecture Figure 1: A uniform memory access (UMA) multicore system Access times to main memory is the same for all cores in the system! Computer Hardware Architecture 2 Manfred Liebmann November 10, 2015 NUMA Architecture Figure 2: A nonuniform memory access (UMA) multicore system Access times to main memory differs form core to core depending on the proximity of the main memory. This architecture is often used in dual and quad socket servers, due to improved memory bandwidth. Computer Hardware Architecture 3 Manfred Liebmann November 10, 2015 Cache Coherence Figure 3: A shared memory system with two cores and two caches What happens if the same data element z1 is manipulated in two different caches? The hardware enforces cache coherence, i.e. consistency between the caches. Expensive! Computer Hardware Architecture 4 Manfred Liebmann November 10, 2015 False Sharing The cache coherence protocol works on the granularity of a cache line. If two threads manipulate different element within a single cache line, the cache coherency protocol is activated to ensure consistency, even if every thread is only manipulating its own data.
[Show full text]
Embedded System Introduction.Pdf
EmbeddedEmbedded SystemSystem IntroductionIntroduction ANDES Confidential WWW.ANDESTECH.COM Embedded System vs Desktop Page 2 相同點 CPU Storage I/O 相異點 Desktop ‧可執行多種功能 ‧作業系統對於系統資源的管理較為複雜 Embedded System ‧執行特定功能 ‧作業系統對於系統資源的管理較為簡單 Page 3 SystemSystem LayerLayer Application Application Operating System Operating System Firmware Firmware Firmware Hardware Hardware Hardware Desktop computer Complex embedded Simple embedded computer computer Page 4 HardwareHardware ArchitectureArchitecture DesktopDesktop ComputerComputer SystemSystem HardwareHardware ArchitectureArchitecture CPU AGP Slot North Bridge Memory PCI Interface USB Interface South Bridge IDE Interface System BIOS ISA Interface Super IO Port Page 5 HardwareHardware ArchitectureArchitecture EmbeddedEmbedded SystemSystem ComputerComputer HardwareHardware ArchitectureArchitecture ADC CPU SPI Digital I/O ROM IIC Host RAM Timers Computer UART Bus Interface Memory Network Interface I/O Page 6 What is the Embedded System? Page 7 IntroductionIntroduction Challenges in embedded system design. Design methodologies. Page 8 EmbeddedEmbedded SystemSystem ?? •An embedded system is a special-purpose computer system designed to perform one or a few dedicated functions •with real-time computing constraints • include hardware, software and mechanical parts Page 9 EmbeddingEmbedding aa computercomputer Page 10 ComponentsComponents ofof anan embeddedembedded systemsystem Characteristics Low power Closed operating environment Cost sensitive Page 11 ComponentsComponents ofof anan embeddedembedded
[Show full text]
14 Los Alamos National Laboratory
14 Los Alamos National Laboratory Every year for the past 17 years, the director of Los Alamos alternative for assessing the safety, reliability, and perfor- National Laboratory has had a legally required task: write mance of the stockpile: virtual-world simulations. a letter—a personal assessment of Los Alamos–designed warheads and bombs in the U.S. nuclear stockpile. Th i s I, Iceberg letter is sent to the secretaries of Energy and Defense and to Hollywood movies such as the Matrix series or I, Robot the Nuclear Weapons Council. Th rough them the letter goes typically portray supercomputers as massive, room-fi lling to the president of the United States. machines that churn out answers to the most complex questions—all by themselves. In fact, like the director’s Th e technical basis for the director’s assessment comes from Annual Assessment Letter, supercomputers are themselves the Laboratory’s ongoing execution of the nation’s Stockpile the tip of an iceberg. Stewardship Program; Los Alamos’ mission is to study its portion of the aging stockpile, fi nd any problems, and address them. And for the past 17 years, the director’s letter has said, Without people, a supercomputer in eff ect, that any problems that have arisen in Los Alamos would be no more than a humble jumble weapons are being addressed and resolved without the need for full-scale underground nuclear testing. of wires, bits, and boxes. When it comes to the Laboratory’s work on the annual assess- Although these rows of huge machines are the most visible ment, the director’s letter is just the tip of the iceberg.
[Show full text]
Advanced Engineering Mathematics
5 Linear Systems of ODEs 5.1 Systems of ODEs In a sense, Chapter 5 equals Chapter 2 “plus” Chapter 3, in the sense that Chapter 5 combines use of matrix theory and ordinary differential equation (ODE) methods. When we have more than one linear ODE, results from matrix theory turn out to be useful. Example 5.1 For the circuit shown in Figure 5.1, let v(t) be the voltage drop across the capacitor and I(t) be the loop current. The input V(t) is a given function. Assume, as usual, that L, R, and C are constants. Write down a system of ODEs in R2 that models this circuit. Method: The series RLC circuit shown in Figure 5.1 is analogous to the DC series RLC circuit discussed near the end of Section 3.3. The first ODE models the voltage drop across the capacitor being v(t) = 1 q(t),whereq(t) is the charge on the capacitor and C ˙ q˙(t) = I(t). The second ODE in the system is Kirchhoff’s voltage law, LI(t)+RI(t)+v(t) = V(t), after dividing through by L. The system is ⎧ ⎫ ⎨˙( ) = 1 ( ) ⎬ v t C I t ⎩ ⎭ . (5.1) ˙( ) = 1 ( ( ) − ( ) − ( )) I t L V t RI t v t More generally, consider a system of two ODEs in unknowns x1(t), x2(t): ⎧ ⎫ ˙ ⎨x1(t) = F1 t, x1(t), x2(t) ⎬ ⎩ ⎭ . (5.2) ˙ x2(t) = F2 t, x1(t), x2(t) A special case is ⎧ ⎫ ˙ ⎨x1(t) = a11(t)x1 + a12(t)x2 + f1(t)⎬ ⎩ ⎭ , (5.3) ˙ x2(t) = a21(t)x1 + a22(t)x2 + f2(t) which is called a linear system.
[Show full text]
Hardware Components and Internal PC Connections
Technological University Dublin ARROW@TU Dublin Instructional Guides School of Multidisciplinary Technologies 2015 Computer Hardware: Hardware Components and Internal PC Connections Jerome Casey Technological University Dublin, [email protected] Follow this and additional works at: https://arrow.tudublin.ie/schmuldissoft Part of the Engineering Education Commons Recommended Citation Casey, J. (2015). Computer Hardware: Hardware Components and Internal PC Connections. Guide for undergraduate students. Technological University Dublin This Other is brought to you for free and open access by the School of Multidisciplinary Technologies at ARROW@TU Dublin. It has been accepted for inclusion in Instructional Guides by an authorized administrator of ARROW@TU Dublin. For more information, please contact [email protected], [email protected]. This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 4.0 License Higher Cert/Bachelor of Technology – DT036A Computer Systems Computer Hardware – Hardware Components & Internal PC Connections: You might see a specification for a PC 1 such as "containing an Intel i7 Hexa core processor - 3.46GHz, 3200MHz Bus, 384 KB L1 cache, 1.5MB L2 cache, 12 MB L3 cache, 32nm process technology; 4 gigabytes of RAM, ATX motherboard, Windows 7 Home Premium 64-bit operating system, an Intel® GMA HD graphics card, a 500 gigabytes SATA hard drive (5400rpm), and WiFi 802.11 bgn". This section aims to discuss a selection of hardware parts, outline common metrics and specifications
[Show full text]
Rapid Mapping of Digital Integrated Circuit Logic Gates Via Multi-Spectral Backside Imaging
RAPID MAPPING OF DIGITAL INTEGRATED CIRCUIT LOGIC GATES VIA MULTI-SPECTRAL BACKSIDE IMAGING RONEN ADATO1;4;∗, AYDAN UYAR1;4, MAHMOUD ZANGENEH1;4, BOYOU ZHOU1;4, AJAY JOSHI1;4, BENNETT GOLDBERG1;2;3;4 AND M SELIM UNL¨ U¨ 1;3;4 Abstract. Modern semiconductor integrated circuits are increasingly fabricated at untrusted third party foundries. There now exist myriad security threats of malicious tampering at the hardware level and hence a clear and pressing need for new tools that enable rapid, robust and low-cost validation of circuit layouts. Optical backside imaging offers an attractive platform, but its limited resolution and throughput cannot cope with the nanoscale sizes of modern circuitry and the need to image over a large area. We propose and demonstrate a multi-spectral imaging approach to overcome these obstacles by identifying key circuit elements on the basis of their spectral response. This obviates the need to directly image the nanoscale components that define them, thereby relaxing resolution and spatial sampling requirements by 1 and 2 - 4 orders of magnitude respectively. Our results directly address critical security needs in the integrated circuit supply chain and highlight the potential of spectroscopic techniques to address fundamental resolution obstacles caused by the need to image ever shrinking feature sizes in semiconductor integrated circuits. 1. Introduction Semiconductor integrated circuits (ICs) are pervasive and essential components in virtually all modern devices, from personal computers, to medical equipment, to varied military systems and technologies. Their functionality is defined by a massive number (∼ 106 − 109 currently) of in- terconnected logic gates that correspond physically to various nanoscale doped regions, polysilicon and metal (usually copper and tungsten) structures.
[Show full text]
Introduction to PC Operating Systems
Introduction to PC Operating Systems Operating System Concepts 8th Edition Written by: Abraham Silberschatz, Peter Baer Galvin and Greg Gagne John Wiley & Sons, Inc. ISBN: 978-0-470-12872-5 Chapter 1 Introduction An operating system is a program that manages the computer hardware. It also provides a basis for application programs and acts as an intermediary between the computer user an the computer hardware. Mainframe, Personal Computers, Handheld Computes, others. Mainframe Operating Systems Designed primarily to optimize utilization of hardware. Personal Computer Operating Systems Designed to support complex games, business applications, etc. Handheld Computer Operating Systems Provide an environment in which a user can easily interface with the computer to execute programs. Other Operating Systems Are designed to be convenient, and some to be efficient and some a combination of the two. (i.e. number pad, indicator lights) Objectives • To provide a grand tour of the major components of operating systems. • To describe the basic organization of computer systems. What Operating Systems Do First, we need to understand that a computer system can be divided roughly into four components; hardware, operating system, application programs and users. Computer Hardware is the physical components of your computer system. Operating system is the set of computer instructions, called a computer program, that controls the allocation of computer hardware such as memory, disk devices, printers, and CD and DVD drives, and provides the capability for you to communicate with the computer. Systems software functions as a bridge between computer system hardware and the application software and is made up of many control programs, including the operating system, communications software and database manager.
[Show full text]
Multithreading and Parallel Computing
Multithreading and Parallel Computing What do you think Trip has been up to this quarter? (wrong answers only in the chat) Object-Oriented Programming Roadmap C++ basics Implementation User/client vectors + grids arrays dynamic memory stacks + queues management sets + maps linked data structures real-world Diagnostic algorithms Life after CS106B! Core algorithmic recursive Tools testing analysis problem-solving Object-Oriented Programming Roadmap C++ basics Implementation User/client vectors + grids arrays Where the heck are we now? dynamic memory stacks + queues management sets + maps linked data structures real-world Diagnostic algorithms Life after CS106B! Core algorithmic recursive Tools testing analysis problem-solving Object-Oriented Programming Roadmap C++ basics Implementation User/client vectors + grids arrays Where the heck are we now? dynamic memory stacks + queues management sets + maps linked data structures real-world Diagnostic algorithms Life after CS106B! Core algorithmic recursive Tools testing analysis problem-solving A picture you’ll see again... A picture you’ll see again... You are here! A picture you’ll see again... Multithreading! CS140 Operating Systems A picture you’ll see again... Multithreading! CS140 Operating But I think you’ll see why it was taught Systems formally 106B in quarters of yore :) How can we harness the Today’s cores in our computer in order to parallelize a question workload safely? woah. How can we harness the Today’s cores in our computer in order to parallelize a question workload safely? Parallelize work?? Multiple cores? How can we harness the Today’s cores in our computer in order to parallelize a question workload safely? 1. Review (short!) Today’s 2.
[Show full text]
A Beginner's Guide to High–Performance Computing
A Beginner's Guide to High{Performance Computing 1 Module Description Developer: Rubin H Landau, Oregon State University, http://science.oregonstate.edu/ rubin/ Goals: To present some of the general ideas behind and basic principles of high{performance com- puting (HPC) as performed on a supercomputer. These concepts should remain valid even as the technical specifications of the latest machines continually change. Although this material is aimed at HPC supercomputers, if history be a guide, present HPC hardware and software become desktop machines in less than a decade. Outcomes: Upon completion of this module and its tutorials, the student should be able to • Understand in a general sense the architecture of high performance computers. • Understand how the the architecture of high performance computers affects the speed of programs run on HPCs. • Understand how memory access affects the speed of HPC programs. • Understand Amdahl's law for parallel and serial computing. • Understand the importance of communication overhead in high performance computing. • Understand some of the general types of parallel computers. • Understand how different types of problems are best suited for different types of parallel computers. • Understand some of the practical aspects of message passing on MIMD machines. Prerequisites: • Experience with compiled language programming. • Some familiarity with, or at least access to, Fortran or C compiling. • Some familiarity with, or at least access to, Python or Java compiling. • Familiarity with matrix computing and linear algebra. 1 Intended Audience: Upper{level undergraduates or graduate students. Teaching Duration: One-two weeks. A real course in parallel computing would of course be at least a full term.
[Show full text]
Multi-Threading in IDL
Multi-Threading in IDL Copyright © 2001-2007 ITT Visual Information Solutions All Rights Reserved http://www.ittvis.com/ IDL® is a registered trademark of ITT Visual Information Solutions for the computer software described herein and its associated documentation. All other product names and/or logos are trademarks of their respective owners. Multi-Threading in IDL Table of Contents I. Introduction 3 Introduction to Multi-Threading in IDL 3 What is Multi-Threading? 3 Why Apply Multi-Threading to IDL? 5 A Related Concept: Distributed Processing 5 II. The Thread Pool 7 Design and Implementation of the Thread Pool 7 The IDL Thread Pool 7 Why The Thread Pool Beats Alternatives 9 Re-Architecture of IDL 9 Automatically Parallelizing Compilers 10 Threading at the User Level 11 III. Performance of the Thread Pool 13 Your Mileage May Vary 13 Amdahl’s Law 13 Interpreting TIME_THREAD Plots 15 Example System Results 17 Platform Comparisons 31 IV. Conclusions 36 Summary 36 Advice (So What Should I Buy?) 37 V. Appendices 39 Appendix A: IDL Routines that use the Thread Pool 39 Appendix B: Additional Benchmark Results 41 Appendix C: Glossary 53 ITT Visual Information Solutions • 4990 Pearl East Circle Boulder, CO 80301 P: 303.786.9900 • F: 303.786.9909 • www.ittvis.com Page 2 of 54 Multi-Threading in IDL Introduction Introduction to Multi-Threading in IDL ITT-VIS has added support for using threads internally in IDL to accelerate specific numerical computations on multi-processor systems. Multi-processor capable hardware has finally become cheap and widely available. Most operating systems have support for SMP (Symmetric Multi-Processing), and IDL users are beginning to own such hardware.
[Show full text]
UNIT-I - OVERVIEW of EMBEDDED SYSTEMS Embedded System
UNIT-I - OVERVIEW OF EMBEDDED SYSTEMS Embedded System . An embedded system can be thought of as a computer hardware system having software embedded in it. An embedded system can be an independent system or it can be a part of a large system. An embedded system is a microcontroller or microprocessor based system which is designed to perform a specific task. For example, a fire alarm is an embedded system; it will sense only smoke. An embedded system has three components − It has hardware. It has application software. It has Real Time Operating system (RTOS) that supervises the application software and provide mechanism to let the processor run a process as per scheduling by following a plan to control the latencies. RTOS defines the way the system works. It sets the rules during the execution of application program. A small scale embedded system may not have RTOS. So we can define an embedded system as a Microcontroller based, software driven, reliable, real-time control system. Characteristics of an Embedded System Single-functioned − An embedded system usually performs a specialized operation and does the same repeatedly. For example: A pager always functions as a pager. Tightly constrained − All computing systems have constraints on design metrics, but those on an embedded system can be especially tight. Design metrics is a measure of an implementation's features such as its cost, size, power, and performance. It must be of a size to fit on a single chip, must perform fast enough to process data in real time and consume minimum power to extend battery life.
[Show full text]