Английская Википедия:Communicating sequential processes

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Distinguish In computer science, communicating sequential processes (CSP) is a formal language for describing patterns of interaction in concurrent systems.[1] It is a member of the family of mathematical theories of concurrency known as process algebras, or process calculi, based on message passing via channels. CSP was highly influential in the design of the occam programming language[1][2] and also influenced the design of programming languages such as Limbo,[3] RaftLib, Erlang,[4] Go,[5][3] Crystal, and Clojure's core.async.[6]

CSP was first described in a 1978 article by Tony Hoare,[7] but has since evolved substantially.[8] CSP has been practically applied in industry as a tool for specifying and verifying the concurrent aspects of a variety of different systems, such as the T9000 Transputer,[9] as well as a secure ecommerce system.[10] The theory of CSP itself is also still the subject of active research, including work to increase its range of practical applicability (e.g., increasing the scale of the systems that can be tractably analyzed).[11]

History

The version of CSP presented in Hoare's original 1978 article was essentially a concurrent programming language rather than a process calculus. It had a substantially different syntax than later versions of CSP, did not possess mathematically defined semantics,[12] and was unable to represent unbounded nondeterminism.[13] Programs in the original CSP were written as a parallel composition of a fixed number of sequential processes communicating with each other strictly through synchronous message-passing. In contrast to later versions of CSP, each process was assigned an explicit name, and the source or destination of a message was defined by specifying the name of the intended sending or receiving process. For example, the process 

COPY = *[c:character; west?c → east!c]

repeatedly receives a character from the process named west and sends that character to process named east. The parallel composition 

[west::DISASSEMBLE || X::COPY || east::ASSEMBLE]

assigns the names west to the DISASSEMBLE process, X to the COPY process, and east to the ASSEMBLE process, and executes these three processes concurrently.[7]

Following the publication of the original version of CSP, Hoare, Stephen Brookes, and A. W. Roscoe developed and refined the theory of CSP into its modern, process algebraic form. The approach taken in developing CSP into a process algebra was influenced by Robin Milner's work on the Calculus of Communicating Systems (CCS) and conversely. The theoretical version of CSP was initially presented in a 1984 article by Brookes, Hoare, and Roscoe,[14] and later in Hoare's book Communicating Sequential Processes,[12] which was published in 1985. In September 2006, that book was still the third-most cited computer science reference of all time according to CiteseerШаблон:Citation needed (albeit an unreliable source due to the nature of its sampling). The theory of CSP has undergone a few minor changes since the publication of Hoare's book. Most of these changes were motivated by the advent of automated tools for CSP process analysis and verification. Roscoe's The Theory and Practice of Concurrency[1] describes this newer version of CSP.

Applications

An early and important application of CSP was its use for specification and verification of elements of the INMOS T9000 Transputer, a complex superscalar pipelined processor designed to support large-scale multiprocessing. CSP was employed in verifying the correctness of both the processor pipeline and the Virtual Channel Processor, which managed off-chip communications for the processor.[9]

Industrial application of CSP to software design has usually focused on dependable and safety-critical systems. For example, the Bremen Institute for Safe Systems and Daimler-Benz Aerospace modeled a fault-management system and avionics interface (consisting of about 23,000 lines of code) intended for use on the International Space Station in CSP, and analyzed the model to confirm that their design was free of deadlock and livelock.[15][16] The modeling and analysis process was able to uncover a number of errors that would have been difficult to detect using testing alone. Similarly, Praxis High Integrity Systems applied CSP modeling and analysis during the development of software (approximately 100,000 lines of code) for a secure smart-card certification authority to verify that their design was secure and free of deadlock. Praxis claims that the system has a much lower defect rate than comparable systems.[10]

Since CSP is well-suited to modeling and analyzing systems that incorporate complex message exchanges, it has also been applied to the verification of communications and security protocols. A prominent example of this sort of application is Lowe's use of CSP and the FDR refinement-checker to discover a previously unknown attack on the Needham–Schroeder public-key authentication protocol, and then to develop a corrected protocol able to defeat the attack.[17]

Informal description

Шаблон:Unreferenced section As its name suggests, CSP allows the description of systems in terms of component processes that operate independently, and interact with each other solely through message-passing communication. However, the "Sequential" part of the CSP name is now something of a misnomer, since modern CSP allows component processes to be defined both as sequential processes, and as the parallel composition of more primitive processes. The relationships between different processes, and the way each process communicates with its environment, are described using various process algebraic operators. Using this algebraic approach, quite complex process descriptions can be easily constructed from a few primitive elements.

Primitives

CSP provides two classes of primitives in its process algebra:

Events
Events represent communications or interactions. They are assumed to be indivisible and instantaneous. They may be atomic names (e.g. on, off), compound names (e.g. valve.open, valve.close), or input/output events (e.g. mouse?xy, screen!bitmap).
Primitive processes
Primitive processes represent fundamental behaviors: examples include STOP (the process that communicates nothing, also called deadlock), and SKIP (which represents successful termination).

Algebraic operators

CSP has a wide range of algebraic operators. The principal ones are:

Prefix
The prefix operator combines an event and a process to produce a new process. For example, <math display="block">a \to P</math> is the process that is willing to communicate Шаблон:Mvar with its environment and, after Шаблон:Mvar, behaves like the process Шаблон:Mvar.
Deterministic choice
The deterministic (or external) choice operator allows the future evolution of a process to be defined as a choice between two component processes and allows the environment to resolve the choice by communicating an initial event for one of the processes. For example, <math display="block">(a \to P) \Box (b \to Q)</math> is the process that is willing to communicate the initial events Шаблон:Mvar and Шаблон:Mvar and subsequently behaves as either Шаблон:Mvar or Шаблон:Mvar, depending on which initial event the environment chooses to communicate. If both Шаблон:Mvar and Шаблон:Mvar were communicated simultaneously, the choice would be resolved nondeterministically.
Nondeterministic choice
The nondeterministic (or internal) choice operator allows the future evolution of a process to be defined as a choice between two component processes, but does not allow the environment any control over which one of the component processes will be selected. For example, <math display="block">(a \to P) \sqcap (b \to Q)</math> can behave like either <math>(a \to P)</math> or <math>(b \to Q)</math>. It can refuse to accept Шаблон:Mvar or Шаблон:Mvar and is only obliged to communicate if the environment offers both Шаблон:Mvar and Шаблон:Mvar. Nondeterminism can be inadvertently introduced into a nominally deterministic choice if the initial events of both sides of the choice are identical. So, for example, <math display="block">(a \to a \to \text{STOP}) \Box (a \to b \to \text{STOP})</math> is equivalent to <math display="block">a \to \big((a \to \text{STOP}) \sqcap (b \to \text{STOP})\big)</math>
Interleaving
The interleaving operator represents completely independent concurrent activity. The process <math display="block">P \;|||\; Q</math> behaves as both Шаблон:Mvar and Шаблон:Mvar simultaneously. The events from both processes are arbitrarily interleaved in time.
Interface parallel
The interface parallel operator represents concurrent activity that requires synchronization between the component processes: any event in the interface set can only occur when all component processes are able to engage in that event. For example, the process <math display="block">P \;|[\{ a \}]|\; Q</math> requires that Шаблон:Mvar and Шаблон:Mvar must both be able to perform event Шаблон:Mvar before that event can occur. So, for example, the process <math display="block">(a \to P) \;|[\{ a \}]|\; (a \to Q)</math> can engage in event Шаблон:Mvar and become the process <math display="block">P \;|[\{ a \}]|\; Q</math> while <math display="block">(a \to P ) \;|[\{ a, b \}]|\; (b \to Q)</math> will simply deadlock.
Hiding
The hiding operator provides a way to abstract processes by making some events unobservable. A trivial example of hiding is <math display="block">(a \to P) \setminus \{ a \}</math> which, assuming that the event Шаблон:Mvar doesn't appear in Шаблон:Mvar, simply reduces to <math display="block">P</math>

Examples

One of the archetypal CSP examples is an abstract representation of a chocolate vending machine and its interactions with a person wishing to buy some chocolate. This vending machine might be able to carry out two different events, “coin” and “choc” which represent the insertion of payment and the delivery of a chocolate respectively. A machine which demands payment (only in cash) before offering a chocolate can be written as:

<math display="block">\mathrm{VendingMachine} = \mathrm{coin} \rightarrow \mathrm{choc} \rightarrow \mathrm{STOP}</math>

A person who might choose to use a coin or card to make payments could be modelled as:

<math display="block">\mathrm{Person} = (\mathrm{coin} \rightarrow \mathrm{STOP}) \Box (\mathrm{card} \rightarrow \mathrm{STOP})</math>

These two processes can be put in parallel, so that they can interact with each other. The behaviour of the composite process depends on the events that the two component processes must synchronise on. Thus,

<math display="block">\mathrm{VendingMachine} \left\vert\left[\left\{ \mathrm{coin}, \mathrm{card} \right\}\right]\right\vert \mathrm{Person} \equiv \mathrm{coin} \rightarrow \mathrm{choc} \rightarrow \mathrm{STOP}</math>

whereas if synchronization was only required on “coin”, we would obtain

<math display="block">\mathrm{VendingMachine} \left\vert\left[\left\{ \mathrm{coin} \right\}\right]\right\vert \mathrm{Person} \equiv \left (\mathrm{coin} \rightarrow \mathrm{choc} \rightarrow \mathrm{STOP}\right ) \Box \left (\mathrm{card} \rightarrow \mathrm{STOP}\right )</math>

If we abstract this latter composite process by hiding the “coin” and “card” events, i.e.

<math display="block">\left (\left (\mathrm{coin} \rightarrow \mathrm{choc} \rightarrow \mathrm{STOP}\right ) \Box \left (\mathrm{card} \rightarrow \mathrm{STOP}\right )\right ) \setminus \left\{\mathrm{coin, card}\right\}</math>

we get the nondeterministic process

<math display="block">\left (\mathrm{choc} \rightarrow \mathrm{STOP}\right ) \sqcap \mathrm{STOP}</math>

This is a process which either offers a “choc” event and then stops, or just stops. In other words, if we treat the abstraction as an external view of the system (e.g., someone who does not see the decision reached by the person), nondeterminism has been introduced.

Formal definition

Syntax

The syntax of CSP defines the “legal” ways in which processes and events may be combined. Let Шаблон:Mvar be an event, and Шаблон:Mvar be a set of events. Then the basic syntax of CSP can be defined as:

<math display="block"> \begin{array}{lcll} {Proc} & ::= & \mathrm{STOP} & \; \\ &|& \mathrm{SKIP} & \; \\ &|& e \rightarrow {Proc} & (\text{prefixing})\\ &|& {Proc} \;\Box\; {Proc} & (\text{external} \; \text{choice})\\ &|& {Proc} \;\sqcap\; {Proc} & (\text{nondeterministic} \; \text{choice})\\ &|& {Proc} \;\vert\vert\vert\; {Proc} & (\text{interleaving}) \\ &|& {Proc} \;|[ \{ X \} ]| \;{Proc} & (\text{interface} \; \text{parallel})\\ &|& {Proc} \setminus X & (\text{hiding})\\ &|& {Proc} ; {Proc} & (\text{sequential} \; \text{composition})\\ &|& \mathrm{if} \; b \; \mathrm{then} \; {Proc}\; \mathrm{else}\; Proc & (\text{boolean} \; \text{conditional})\\ &|& {Proc} \;\triangleright\; {Proc} & (\text{timeout})\\ &|& {Proc} \;\triangle\; {Proc} & (\text{interrupt}) \end{array} </math>

Note that, in the interests of brevity, the syntax presented above omits the <math>\mathbf{div}</math> process, which represents divergence, as well as various operators such as alphabetized parallel, piping, and indexed choices.

Formal semantics

Шаблон:Expand section

CSP has been imbued with several different formal semantics, which define the meaning of syntactically correct CSP expressions. The theory of CSP includes mutually consistent denotational semantics, algebraic semantics, and operational semantics.

Denotational semantics

The three major denotational models of CSP are the traces model, the stable failures model, and the failures/divergences model. Semantic mappings from process expressions to each of these three models provide the denotational semantics for CSP.[1]

The traces model defines the meaning of a process expression as the set of sequences of events (traces) that the process can be observed to perform. For example,

  • <math>\mathrm{traces}\left(\mathrm{STOP}\right) = \left\{ \langle\rangle \right\}</math> since <math>\mathrm{STOP}</math> performs no events
  • <math>\mathrm{traces}\left(a\rightarrow b \rightarrow \mathrm{STOP}\right) = \left\{\langle\rangle ,\langle a \rangle, \langle a, b \rangle \right\}</math> since the process <math>(a\rightarrow b \rightarrow \mathrm{STOP})</math> can be observed to have performed no events, the event Шаблон:Mvar, or the sequence of events Шаблон:Mvar followed by Шаблон:Mvar

More formally, the meaning of a process Шаблон:Mvar in the traces model is defined as <math>\mathrm{traces}\left(P\right) \subseteq \Sigma^{\ast}</math> such that:

  1. <math>\langle\rangle \in \mathrm{traces}\left(P\right)</math> (i.e. <math>\mathrm{traces}\left(P\right)</math> contains the empty sequence)
  2. <math>s_1 \smallfrown s_2 \in \mathrm{traces}\left(P\right) \implies s_1 \in \mathrm{traces}\left(P\right)</math> (i.e. <math>\mathrm{traces}\left(P\right)</math> is prefix-closed)

where <math>\Sigma^{\ast}</math> is the set of all possible finite sequences of events.

The stable failures model extends the traces model with refusal sets, which are sets of events <math>X \subseteq \Sigma</math> that a process can refuse to perform. A failure is a pair <math>\left(s,X\right)</math>, consisting of a trace Шаблон:Mvar, and a refusal set Шаблон:Mvar which identifies the events that a process may refuse once it has executed the trace Шаблон:Mvar. The observed behavior of a process in the stable failures model is described by the pair <math>\left(\mathrm{traces}\left(P\right), \mathrm{failures}\left(P\right)\right)</math>. For example,

<math display="block">\mathrm{failures}\left(\left(a \rightarrow \mathrm{STOP}\right) \Box \left(b \rightarrow \mathrm{STOP}\right)\right) = \left\{\left(\langle\rangle,\emptyset\right), \left(\langle a \rangle, \left\{a,b\right\}\right), \left(\langle b \rangle,\left\{a,b\right\}\right) \right\}</math> <math display="block">\mathrm{failures}\left(\left(a \rightarrow \mathrm{STOP}\right) \sqcap \left(b \rightarrow \mathrm{STOP}\right)\right) = \left\{ \left(\langle\rangle,\left\{a\right\}\right), \left(\langle\rangle,\left\{b\right\}\right), \left(\langle a \rangle, \left\{a,b\right\}\right), \left(\langle b \rangle,\left\{a,b\right\}\right) \right\}</math>

The failures/divergence model further extends the failures model to handle divergence. The semantics of a process in the failures/divergences model is a pair <math>\left(\mathrm{failures}_\perp\left(P\right), \mathrm{divergences}\left(P\right)\right)</math> where <math>\mathrm{divergences}\left(P\right)</math> is defined as the set of all traces that can lead to divergent behavior and <math>\mathrm{failures}_\perp\left(P\right) = \mathrm{failures}\left(P\right) \cup \left\{\left(s,X\right) \mid s \in \mathrm{divergences}\left(P\right)\right\}</math>.

Tools

Over the years, a number of tools for analyzing and understanding systems described using CSP have been produced. Early tool implementations used a variety of machine-readable syntaxes for CSP, making input files written for different tools incompatible. However, most CSP tools have now standardized on the machine-readable dialect of CSP devised by Bryan Scattergood, sometimes referred to as CSPM.[18] The CSPM dialect of CSP possesses a formally defined operational semantics, which includes an embedded functional programming language.

The most well-known CSP tool is probably Failures/Divergence Refinement 2 (FDR2), which is a commercial product developed by Formal Systems (Europe) Ltd. FDR2 is often described as a model checker, but is technically a refinement checker, in that it converts two CSP process expressions into Labelled Transition Systems (LTSs), and then determines whether one of the processes is a refinement of the other within some specified semantic model (traces, failures, or failures/divergence).[19] FDR2 applies various state-space compression algorithms to the process LTSs in order to reduce the size of the state-space that must be explored during a refinement check. FDR2 has been succeeded by FDR3, a completely re-written version incorporating amongst other things parallel execution and an integrated type checker. It is released by the University of Oxford, which also released FDR2 in the period 2008–12.[20]

The Adelaide Refinement Checker (ARC)[21] is a CSP refinement checker developed by the Formal Modelling and Verification Group at The University of Adelaide. ARC differs from FDR2 in that it internally represents CSP processes as Ordered Binary Decision Diagrams (OBDDs), which alleviates the state explosion problem of explicit LTS representations without requiring the use of state-space compression algorithms such as those used in FDR2.

The ProB project,[22] which is hosted by the Institut für Informatik, Heinrich-Heine-Universität Düsseldorf, was originally created to support analysis of specifications constructed in the B method. However, it also includes support for analysis of CSP processes both through refinement checking, and LTL model-checking. ProB can also be used to verify properties of combined CSP and B specifications. A ProBE CSP Animator is integrated in FDR3.

The Process Analysis Toolkit (PAT) [23][24] is a CSP analysis tool developed in the School of Computing at the National University of Singapore. PAT is able to perform refinement checking, LTL model-checking, and simulation of CSP and Timed CSP processes. The PAT process language extends CSP with support for mutable shared variables, asynchronous message passing, and a variety of fairness and quantitative time related process constructs such as deadline and waituntil. The underlying design principle of the PAT process language is to combine a high-level specification language with procedural programs (e.g. an event in PAT may be a sequential program or even an external C# library call) for greater expressiveness. Mutable shared variables and asynchronous channels provide a convenient syntactic sugar for well-known process modelling patterns used in standard CSP. The PAT syntax is similar, but not identical, to CSPM.[25] The principal differences between the PAT syntax and standard CSPM are the use of semicolons to terminate process expressions, the inclusion of syntactic sugar for variables and assignments, and the use of slightly different syntax for internal choice and parallel composition.

VisualNets[26] produces animated visualisations of CSP systems from specifications, and supports timed CSP.

CSPsim[27] is a lazy simulator. It does not model check CSP, but is useful for exploring very large (potentially infinite) systems.

SyncStitch is a CSP refinement checker with interactive modeling and analyzing environment. It has a graphical state-transition diagram editor. The user can model the behavior of processes as not only CSP expressions but also state-transition diagrams. The result of checking are also reported graphically as computation-trees and can be analyzed interactively with peripheral inspecting tools. In addition to refinement checks, It can perform deadlock check and livelock check.

Related formalisms

Several other specification languages and formalisms have been derived from, or inspired by, the classic untimed CSP, including:

Comparison with the actor model

In as much as it is concerned with concurrent processes that exchange messages, the actor model is broadly similar to CSP. However, the two models make some fundamentally different choices with regard to the primitives they provide:

  • CSP processes are anonymous, while actors have identities.
  • CSP uses explicit channels for message passing, whereas actor systems transmit messages to named destination actors. These approaches may be considered duals of each other, in the sense that processes receiving through a single channel effectively have an identity corresponding to that channel, while the name-based coupling between actors may be broken by constructing actors that behave as channels.
  • CSP message-passing fundamentally involves a rendezvous between the processes involved in sending and receiving the message, i.e. the sender cannot transmit a message until the receiver is ready to accept it. In contrast, message-passing in actor systems is fundamentally asynchronous, i.e. message transmission and reception do not have to happen at the same time, and senders may transmit messages before receivers are ready to accept them. These approaches may also be considered duals of each other, in the sense that rendezvous-based systems can be used to construct buffered communications that behave as asynchronous messaging systems, while asynchronous systems can be used to construct rendezvous-style communications by using a message/acknowledgement protocol to synchronize senders and receivers.

Note that the aforementioned properties do not necessarily refer to the original CSP paper by Hoare, but rather the modern incarnation of the idea as seen in implementations such as Go and Clojure's core.async. In the original paper, channels were not a central part of the specification, and the sender and receiver processes actually identify each other by name.

Award

In 1990, “A Queen’s Award for Technological Achievement has been conferred ... on [Oxford University] Computing Laboratory. The award recognises a successful collaboration between the laboratory and Inmos Ltd. … Inmos’ flagship product is the ‘transputer’, a microprocessor with many of the parts that would normally be needed in addition built into the same single component.”[29] According to Tony Hoare,[30] “The INMOS Transputer was as embodiment of the ideas … of building microprocessors that could communicate with each other along wires that would stretch between their terminals. The founder had the vision that the CSP ideas were ripe for industrial exploitation, and he made that the basis of the language for programming Transputers, which was called Occam. … The company estimated it enabled them to deliver the hardware one year earlier than would otherwise have happened. They applied for and won a Queen’s award for technological achievement, in conjunction with Oxford University Computing Laboratory.”

See also

References

Шаблон:Reflist

Further reading

External links

Шаблон:Concurrent computing

Партнерские ресурсы
Криптовалюты
Магазины
Хостинг
Разное

  1. ↑ 1,0 1,1 1,2 1,3 Шаблон:Cite book
  2. ↑ Шаблон:Cite book, INMOS document 72 occ 45 03.
  3. ↑ 3,0 3,1 Шаблон:Cite web
  4. ↑ Шаблон:Cite web
  5. ↑ Шаблон:Cite web
  6. ↑ Шаблон:Cite web
  7. ↑ 7,0 7,1 Шаблон:Cite journal
  8. ↑ Шаблон:Cite book
  9. ↑ 9,0 9,1 Шаблон:Cite journal
  10. ↑ 10,0 10,1 Шаблон:Cite journal
  11. ↑ Шаблон:Cite thesis
  12. ↑ 12,0 12,1 Шаблон:Cite book
  13. ↑ Шаблон:Cite thesis
  14. ↑ Шаблон:Cite journal
  15. ↑ Шаблон:Cite conference
  16. ↑ Шаблон:Cite conference
  17. ↑ Шаблон:Cite conference
  18. ↑ Шаблон:Cite thesis
  19. ↑ Шаблон:Cite book
  20. ↑ Шаблон:Cite web
  21. ↑ Шаблон:Cite conference
  22. ↑ Шаблон:Cite conference
  23. ↑ Шаблон:Cite conference
  24. ↑ Шаблон:Cite conference
  25. ↑ Шаблон:Cite conference
  26. ↑ Шаблон:Cite conference
  27. ↑ Шаблон:Cite conference
  28. ↑ ISO 8807, Language of Temporal Ordering Specification
  29. ↑ Шаблон:Cite journal
  30. ↑ Шаблон:Cite journal
Источник — http://wikihandbk.com/ruwiki/index.php?title=Английская_Википедия:Communicating_sequential_processes&oldid=14034964