Download PPT - Global Operating Systems Technology Group

Advanced Operating Systems
Lecture notes
Dr. Clifford Neuman
University of Southern California
Information Sciences Institute
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Administration
 Instructors
 Dr. Clifford Neuman
 Office hours – SAL 212
– Friday 12:50 PM – 1:50 PM
 TA
 Younggeun Choi
 Office Hours – OFFICE TBD
 Monday,Thursday 10:00AM – 11:00AM
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Administration
Class Home Page
http://gost.isi.edu/555/
 Announcements
 Syllabus
 Lecture
Slides
 Reading list
Class e-mail: [email protected]
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Administrative Information
Reading list
 ~65 papers and
 ~20 book chapters
 Concentrated toward the first half
Text
 Distributed Systems: Concepts and
Design (fourth edition)
 By Coulouris, Dollimore, and Kindberg
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Administrative Information
Assignments
 4 Reports,
 Due 11 p.m. Wednesday nights
 Research Paper
 Due: last class
 Exams
 Mid-Term: Friday, October 17
 Final Exam: Friday, December 14
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Administrative Information
DEN site - Blackboard
 Lecture webcast
 Class forum on DEN
 Grades
Lecture notes to be posted before lecture
Academic Integrity

READ IT – It applies to you
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Academic Integrity
 I take Academic Integrity Seriously
 Every year I have too many cases of cheating
 Last year I assigned multiple F’s for the class
 What is and is not OK
 I encourage you to work with others to learn the material
 Do not to turn in the work of others
 Do not give others your work to use as their own
 Do not plagiarize from others (published or not)
 Do not try to deceive the instructors
 See section on web site and assignments
 More guidelines on academic integrity
 Links to university resources
 Don’t just assume you know what is acceptable.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Administration
Grading
 20%: Reading Reports
 20%: Midterm
 20%: Final
 30%: Research Paper
 10%: Class Participation & Quizes
 Class forum participation
 In class participation
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
How to survive?
Read the survival guide
How to read papers
 Read the papers in advance
 Be critical
 At least skim through
Build your own notes
Study group
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
CSci555:
Advanced Operating Systems
Lecture 1 – August 29, 2008
Dr. Clifford Neuman
University of Southern California
Information Sciences Institute
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
What you should learn in this course
You will gain a basic understanding of
distributed system concepts.
You will develop intuition for which
approaches work, and which don’t.
You will develop the ability to sense where
bottlenecks lie in system design.
You will remember where to look for more
information when you are faced with a
distributed system problem.
Above all, you will learn how to be critical of
what you are told by system designers.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Some things an operating system does (review)
Memory Management
Scheduling / Resource management
Communication
Protection and Security
File Management - I/O
Naming
Synchronization
User Interface
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Progression of Operating Systems
Primary goal of a distributed system:
 Sharing
Progression over past years
 Dedicated machines
 Batch Processing
 Time Sharing
 Workstations and PC’s
 Distributed Systems
 Devices
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Structure of Distributed Systems
Kernel
 Basic functionality and protection
Application Level
 Does the real work
Servers
 Service and support functions
needed by applications
 Many functions that used to be in
Kernel are now in servers.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Structure of Distributed Systems
UP
User Space
SVR
Kernel
User Space
SVR
Kernel
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Network vs. OS Layering
(No direct mapping, colors to stimulate discussion)
Application Layer
Applications
LIBRARIES
Presentation Layer
User Space
Session Layer
SERVICES
Servers
Transport Layer
Network Layer
OS SERVICES
Kernel
Link Layer
Physical
Hardware
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Characteristics of a Distributed System
Basic characteristics:
 Multiple Computers
 Interconnections
 Shared State
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Why Distributed Systems are Hard
Scale:
 Numeric
 Geographic
 Administrative
Loss of control over parts of the system
Unreliability of Messages
Parts of the system down or inaccessible
 Lamport: You know you have a distributed system
when the crash of a computer you have never heard of
stops you from getting any work done.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
End-to-End Argument
QUESTION: Where to place distributed
systems functions?
Layered system design:
 Different levels of abstraction for
simplicity.
 Lower layer provides service to upper
layer.
 Very well defined interfaces.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
E2E Argument (continued)
E2E paper argues that functions should
be moved closer to the application that
uses them.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
E2E Argument (continued)
 Rationale:
 Some functions can only be completely
and correctly implemented with
application’s knowledge.
 Example:
– Reliable message delivery,
security
– Encrypted e-mail
– Streaming media vs. Banking
 Applications that do not need certain
functions should not have to pay for
them.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
E2E Counter-Argument
 Performance
 Example: File transfer
 Reliability checks at lower layers detect
problems earlier.
 Abort transfer and re-try without having
to wait till whole file is transmitted.
 Abstraction
 Less repetition across apps
Bottom line: “spread” functionality across layers.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Slides for Lecture 2
The following slides are for lecture 2.
They are included here in case we
progress faster than expected in class.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Outline: Communications Models
 Communication Models:
 General concepts.
 Message passing.
 Distributed shared memory (DSM).
 Remote procedure call (RPC) [Birrel et al.]
 Light-weight RPC [Bershad et al.]
 DSM case studies
 IVY [Li et al.]
 Linda [Carriero et al.]
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Communication Models
Support for processes to
communicate among themselves.
Traditional (centralized) OS’s:
 Provide local (within single
machine) communication support.
 Distributed OS’s: must provide
support for communication across
machine boundaries.
 Over LAN or WAN.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Communication Paradigms
 2 paradigms
 Message Passing (MP)
 Distributed Shared Memory (DSM)
 Message Passing
 Processes communicate by sending
messages.
 Distributed Shared Memory
 Communication through a “virtual shared
memory”.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Message Passing
 Basic communication primitives:
 Send message.
Send

Receive message.
Receive
Sending Q
...
Receiving Q
...
 Modes of communication:
 Synchronous versus asynchronous.
 Semantics:
 Reliable versus unreliable.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Synchronous Communication
Blocking send
 Blocks until message is transmitted
 Blocks until message acknowledged
Blocking receive
 Waits for message to be received
Process synchronization.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Asynchronous Communication
 Non-blocking send: sending process continues
as soon message is queued.
 Blocking or non-blocking receive:
 Blocking:
 Timeout.
 Threads.
 Non-blocking: proceeds while waiting for
message.
 Message is queued upon arrival.
 Process needs to poll or be interrupted.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Reliability of Communication
 Reliable communication:
 Different degrees of reliability.
 Processes have some guarantee that messages
will be delivered.
 Example: Transmission Control Protocol (TCP)
 Reliability mechanisms:
 Positive acknowledgments (ACKs).
 Negative Acknowledgments (NACKs).
 Possible to build reliability atop unreliable
service (E2E argument).
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Distributed Shared Memory
Motivated by development of sharedmemory multiprocessors which do
share memory.
Abstraction used for sharing data
among processes running on
machines that do not share memory.
Processes think they read from and
write to a “virtual shared memory”.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
DSM 2
Primitives: read and write.
OS ensures that all processes see all
updates.
 Happens transparently to
processes.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
DSM and MP
 DSM is an abstraction!
 Gives programmers the flavor of a centralized
memory system, which is a well-known
programming environment.
 No need to worry about communication and
synchronization.
 But, it is implemented atop MP.
 No physically shared memory.
 OS takes care of required communication.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Caching in DSM
 For performance, DSM caches data locally.
 More efficient access (locality).
 But, must keep caches consistent.
 Caching of pages for of page-based DSM.
 Issues:
 Page size.
 Consistency mechanism.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Approaches to DSM
Hardware-based:
 Multi-processor architectures with
processor-memory modules connected
by high-speed LAN (E.g., Stanford’s
DASH).
 Specialized hardware to handle reads
and writes and perform required
consistency mechanisms.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Approaches to DSM
Page-based:
 Example: IVY.
 DSM implemented as region of
processor’s virtual memory;
occupies same address space
range for every participating
process.
 OS keeps DSM data consistency
as part of page fault handling.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
Approaches to DSM
Library-based:
 Or language-based.
 Example: Linda.
 Language or language extensions.
 Compiler inserts appropriate library
calls whenever processes access DSM
items.
 Library calls access local data and
communicate when necessary.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
DSM Case Studies: IVY
 Environment:”loosely coupled”
multiprocessor.
 Memory is physically distributed.
 Memory mapping managers (OS kernel):
 Map local memories to shared virtual space.
 Local memory as cache of shared virtual space.
 Memory reference may cause page fault; page
retrieved and consistency handled.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
IVY
Issues:
 Read-only versus writable data.
 Locality of reference.
 Granularity (1 Kbyte page size).
 Bigger pages versus smaller
pages.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
IVY
Memory coherence strategies:
 Page synchronization
 Invalidation
 Write broadcast
 Page ownership
 Fixed: page always owned by same
processor
 Dynamic
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
IVY Page Synchronization
 Invalidation:
 On write fault, invalidate all copies; give
faulting process write access; gets copy of
page if not already there.
 Problem: must update page on reads.
 Write broadcast:
 On write fault, fault handler writes to all
copies.
 Expensive!
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE
IVY Memory Coherence
Paper discusses approaches to memory
coherence in page-based DSM.
 Centralized: single manager
residing on a single processor
managing all pages.
 Distributed: multiple managers
on multiple processors managing
subset of pages.
Copyright © 1995-2008 Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE