COMMUNICATING SEQUENTIAL PROCESSES通信顺序进程.pptVIP

COMMUNICATINGSEQUENTIALPROCESSES C. A. R. Hoare The Queen’s UniversityBelfast, North Ireland INTRODUCTION CSP is a simple programming language designed for multiprocessor machines Its key feature is its reliance on non-buffered message passing with explicit naming of source and destination processes CSP uses guarded commands to let processes wait for messages coming from different sources. The Model Each process runs on its own processor All communications between concurrent processes are made through message passing. CSP relies on the most primitive message passing mechanism: Non-buffered sends and receives Explicit naming of source and destination processes Non buffered sends and receives When a process issues a send( ), the system call does not complete until the message is received by another process Also called “blocking send” When a process issues a receive( ), the system call does not complete until a message is received by the process Also called “blocking receive” Explicit naming Also known as direct naming A process issuing a send( ) specifies the name of the process to which the message is sent A process issuing a receive( ) specifies the name of the process from which it expects a message The alternative: indirect naming Most message passing architectures include an intermediary entity often called port but also mailbox, message queue or socket A process issuing a send( ) specifies the port number to which the message is sent A process issuing a receive( ) specifies a port number and will wait for the the first message that arrives at that port The problem (I) Processes should be able to receive messages from different senders Can use blocking receive and indirect naming Process issuing a receive will wait for first message arriving at that port Can also use non-blocking receive anddirect naming Requires receiving process to poll senders The problem (II) Using blocking receives with direct naming does not allow the receiving process