1. COT 4600 Operating Systems Spring 2011 Dan C. Marinescu Office: HEC 304 Office hours: Tu-Th 5:00 – 6:00 PM

2. Last time:  Memory  Interpreters.  Communication links. Today:  Communication – The Internet  Naming; Use by: value/name Binding and indirection Next time Generic naming model Name mapping algorithms Comparing names; name discovery Practical design of naming scheme Contexts Name overloading UNIX File System Lecture 7 – Thursday, February 3, 2011 Lecture 72

3. 3 The Internet – an extreme example of what hides behind the communication link abstraction Hourglass communication model Protocol stack Internet Core and Edge The hardware  Router  Network adaptor

4. Lecture 74 Internet Core and Edge

5. Lecture 75 Hourglass communication model

6. Lecture 76 Transport and Network Services

7. Lecture 77 Multiplexing and Demultiplexing

8. Lecture 78 Application, Transport, Network, and Data Link Layer Protocols

9. Lecture 79 It's a long way to Tipperary it's a long way to go!!

10. Lecture 710 From Local Area to Wide Area Networks

11. Lecture 711 Message delivery to processes

12. Lecture 712 Sockets and Ports

13. Lecture 713 Router

14. Lecture 714 Router supporting QoS (Quality of Service)

15. Lecture 715 The network adaptor

16. Lecture 7 Naming The three abstractions manipulate objects identified by name. How could object A access object B:  Make a copy of object B and include it in A  use by value Safe  there is a single copy of B How to implement sharing of object B?  Pass to A the means to access B using its name  use by reference Not inherently safe  both A and C may attempt to modify B at the same time. Need some form of concurrency control. 16

17. Lecture 7 Binding and indirection Names allow the system designer to: 1. organize the modules of a system and to define communication patterns among them 2. defer for a later time to create object B referred to by object A select the specific object A wishes to use Indirection  decoupling objects from their physical realization through names. Binding  linking the object to names. Examples:  A compiler constructs a table of variables and their relative address in the data section of the memory map of the process a list of unsatisfied external references  A linker binds the external references to modules from libraries 17