Search results
the evolution of operating systems. LO 1.3 List and compare the common desktop operating systems in use today. LO 1.4 List the most common mobile OSs, the devices associated with them, and the features found in most of these devices. Introduction to Operating Systems chapter 1 ©Yuriy Rudyy/Shutterstock Final PDF to printer
virtual address space, set of resources (object handles), and one or more threads. A thread are the unit of dispatching. Each thread has: scheduling state (ready, running, etc.), other scheduling parameters (priority, etc), context slot, and (generally) an associated process.
- 780KB
- 168
History of Operating Systems. Phase 1: Hardware expensive, humans cheap. User at console: single-user systems. Batching systems. Multi-programming systems. Phase 2: Hardware cheap, humans expensive. Timesharing: Users use cheap terminals and share CPU. Timesharing (1970-) Timer interrupt used to multiplex CPU between jobs.
An introductory course to operating systems-Classic OS concepts and principles-Prepare you for advanced OS and distributed system course -OS concepts often asked in tech interview questions A practice course for hands-on experience with OS-Four large programming assignments on a small but realOS-Reinforce your understandings about the theories
- Staff
- Slides
- Overview
- What is an Operating System?
- Computer System Components
- Operating system roles
- Example: file systems
- OS challenges
- Why should I study Operating Systems?
- Example: Rio: I/O sharing implemented in the operating system kernel
- Application layer
- Client
- Video demo of Rio
- Overview
- Operating systems history (start)
- Hardware – expensive ; Human – cheap
- Speeding up I/O: Direct Memory Access (DMA)
- Batch Systems - I/O completion
- Multiprogramming
- Hardware – getting cheaper; Human – getting expensive
- Hardware – cheap ; Human – expensive
- Hardware – very cheap ; Human – very expensive
- Overview
- Computer System & OS Structures
- I/O devices
- Direct Memory Access (DMA)
- I/O completion
- Interrupts
- Interrupt handling
- Hardware Protection
- Should a process be able to execute any instructions?
- Dual-mode operation
- CPU Protection
- Memory Protection
- Should load instructions for the base and limit
- I/O Protection
- Question
- System services or system programs
- Storage Structure
- Storage Hierarchy
- OS Task: Process Management
- OS Task: Memory Management
- OS Task: Secondary Storage and I/O Management
- OS Task: File System Management
- OS Task: Protection and Security
- Summary of this week’s lecture
- GeneratedCaptionsTabForHeroSec
Instructor Ardalan Amiri Sani (ardalan@uci.edu) Staff Teaching Assistants: Saehanseul Yi Farzad Habibi Ashwin Gerard Colaco
Will upload first draft of the slides for all of the week on Tuesday Might (and most likely will) update slides for each class before the class Will mention on the website which pages have been updated
What is an operating system? Operating systems history Computer system and operating system structure
What is an Operating System? • is the software that acts an intermediary between the applications and computer hardware.
Hardware Provides basic computing resources (CPU, memory, I/O devices). Operating System Controls and coordinates the use of hardware among application programs. Application Programs Solve computing problems of users (compilers, database systems, video games, business programs). Users People, other computers
Referee Resource allocation among users, applications Isolation of different users, applications from each other Communication between users, applications Operating system roles Illusionist Each application appears to have the entire machine to itself Infinite number of processors, (near) infinite amount of memory, reliable storage, reliable networ...
Referee Allocates storage space for files for each user Prevent users from accessing each other’s files without permission Illusionist Files can grow (nearly) arbitrarily large Files persist even when the machine crashes in the middle of a save Glue Named directories, printf, ...
OS challenges Reliability Does the system do what it was designed to do? OS challenges Availability What portion of the time is the system working? Mean Time To Failure (MTTF), Mean Time to Repair OS challenges Security Can the system be compromised by an attacker? OS challenges Privacy Data is accessible only to authorized users OS challenges Perf...
Why should I study Operating Systems? Need to understand interaction between the hardware and software Need to understand basic principles in the design of computer systems efficient resource management, security, etc. Why should I study Operating Systems? • it enables you to do things that are difficult/impossible otherwise.
(Slides on Rio are not part of the course material)
User space Kernel Application Daemons, Libraries User space Kernel Device driver I/O device
User space Kernel Device file /dev/foo Device driver I/O device Server Key idea: device files as the boundary Application File operations User space Kernel Virtual device file /dev/foo Client User space Kernel Device file /dev/foo Device driver I/O device Server Key idea: device files as the boundary Application File operations User space Kernel Vi...
https://www.yecl.org/rio.html (end of slides on Rio) Operating systems are everywhere Operating systems are everywhere Operating systems are everywhere Operating systems are everywhere
What is an operating system? Operating systems history Computer system and operating system structure
Early Systems Simple Batch Systems Multiprogrammed Batch Systems Time-sharing Systems Personal and Mobile Computer Systems (The slides on the OS history are for your own study and won’t be used in the exams.)
Structure Large machines run from console Single user system Programmer/User as operator Punched cards, paper tape, and magnetic tape Early software Assemblers, compilers, linkers, loaders, device drivers, libraries of common subroutines. Secure execution Inefficient use of expensive resources Low CPU utilization, high setup time.
Data moved directly between CPU can work on other tasks I/O instructions I/O devices and memory Memory CPU I/O devices
How do we know that I/O is complete? Polling: Device sets a flag when it is busy. Program tests the flag in a loop waiting for completion of I/O. Interrupts: On completion of I/O, device forces CPU to jump to a specific instruction address that contains the interrupt service routine. After the interrupt has been processed, CPU returns to code it wa...
Use interrupts to run multiple programs simultaneously When a program performs I/O, instead of polling, execute another program till interrupt is received. Requires secure memory, I/O for each program. Requires intervention if program infinite loops. Requires CPU scheduling to choose the next job to run.
Programs queued for execution in FIFO order. Like multiprogramming, but timer device interrupts after a quantum (timeslice). Interrupted program is returned to end of FIFO Next program is taken from head of FIFO Control card interpreter replaced by command language interpreter. Timesharing (cont.) Interactive (action/response) when OS finishes exec...
Single user systems, portable. I/O devices - keyboards, mice, display screens, small printers. Single user systems may not need advanced CPU utilization or protection features. Advantages: user convenience, responsiveness, ubiquitous
Single user, multiple computers Laptops Smartphones Tablets Smart glasses Smart watches (End of slides on history)
What is an operating system? Operating systems history Computer system and operating system structure
Computer System Organization Process abstraction and hardware protection System call and OS services Storage architecture OS organization OS tasks Virtual Machines Computer
I/O devices I/O devices and the CPU execute concurrently. Each device controller is in charge of a particular device type Each device controller has a local buffer. I/O is from the device to local buffer of controller CPU moves data from/to main memory to/from the local buffers
Typically used for I/O devices with a lot of data to transfer (in order to reduce load on CPU). Device controller transfers blocks of data to/from local buffer directly to main memory without CPU intervention. Only one interrupt is generated per block, rather than one per byte (or word). CPU Memory I/O instructions I/O devices
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
A PDF file of the first lecture of a course on operating systems at UCI, covering the definition, roles, challenges and examples of operating systems. The file also contains slides on the computer system components, the operating system structure and the hardware abstraction layer.
Operating System Concepts Tenth Edition Avi Silberschatz Peter Baer Galvin Greg Gagne John Wiley & Sons, Inc. ISBN 978-1-118-06333-0 Face The Real World of Operating Systems Fully Equipped. Welcome to the Web Page supporting Operating System Concepts, Tenth Edition. This new edition (April 15, 2018), which is published by
People also ask
What is operating system concept?
What is a desktop operating system?
Which operating system runs on a desktop computer?
What is a portable operating system?
Jul 29, 2019 · Download, borrow, or stream the 10th edition of Operating System Concepts, a textbook by Abraham Silberschatz, Peter B. Galvin, and Greg Gagne. The book covers operating system topics in English language.
