Parallel programming model: Difference between revisions

Revision as of 16:43, 27 April 2019

Revision as of 08:05, 29 April 2019

Line 16:

====Message passing====

{{main|Message passing}}

In a message-passing model, parallel processes exchange data through passing messages to one another. These communications can be asynchronous, where a message can be sent before the receiver is ready, or synchronous, where the receiver must be ready. The [[Communicating sequential processes]] (CSP) formalisation of message passing uses synchronous communication channels to connect processes, and led to important languages such as [[Occam (programming language)|Occam]], [[Limbo (programming language)|Limbo]] and [[Go (programming language)|Go]]. In contrast, the [[actor model]] uses asynchronous message passing and has been employed in the design of languages such as [[D (programming language)|D]], [[Scala (programming language)|Scala]] and [[SALSA (programming language)|SALSA]].

====Implicit interaction====

Line 49:

| Asynchronous message passing

| Task

| [[D (programming language)|D]], [[Erlang (programming language)|Erlang]], [[Scala (programming language)|Scala]], [[SALSA (programming language)|SALSA]]

|-

| [[Bulk synchronous parallel]]