操作系统课件CCH04-Process.ppt

4.8 Complexity and Computer Engineering Software applications have grown more and more complex. An application cannot consist of only one process taking care of everything. Applications consist of several processes cooperating with one another. Independent vs cooperating processes Independent processes do not affect, and are not affected by, other processes. Cooperating processes do affect and can be affected by other processes. Cooperating “organs” But for cooperation…the OS has to provide for… Communication facilities between cooperating processes. The OS is responsible for providing those services. IPC services. For cooperation there must be coordination…synchronization! Again it’s the responsibility of the OS to provide those synchronization mechanisms. Interprocess Communication (IPC) The OS must provide the mechanisms for communication among processes. (a) Shared memory! (b) Message passing. Shared memory It is fast! (advantage). But… It breaks the protected memory scheme and must be requested explicitly by the processes. AP must manage SM. AP must supply the protection and synchronization for the use of SM. Message passing More general than Shared Memory (it works on distributed systems too!) The sending process creates a message in its own address space. The OS transfer that message to the address space of the receiver process. Message passing MP is usually implemented in two mechanisms: send(message); receive(message); When two processes want to “talk” they need to request a communication link to… …the OS, of course! Design issues Naming or addressing: How do sender and receiver identify themselves? Synchronization: Do processes continue after a send or a receive? Buffering: How many messages fit in the buffer? Exceptions: When an error occurs, how can the process recover? Direct Commu-nication Processes name each other send(P, message) receive(Q, message) Send message to process P, receive message from process Q. Convenient when one-to-one communica