Active message

<h2 id="distributed-memory-programming">Distributed memory programming</h2>
<p>Active messages are communications primitive for exploiting the full <a href="/facts/Computer_performance/td1qKox4">performance</a> and flexibility of modern computer interconnects. They are often classified as one of the three main types of distributed memory programming, the other two being <a href="/facts/Data_parallel/SkYoL91S">data parallel</a> and <a href="/facts/Message_passing/RYf3hD3J">message passing</a>. The view is that Active Messages are actually a lower-level mechanism that can be used to implement data parallel or message passing efficiently.
</p><p>The basic idea is that each message has a header containing the address or index of a userspace handler to be executed upon message arrival, with the contents of the message passed as an argument to the handler. Early active message systems passed the actual remote code address across the network, however this approach required the initiator to know the address of the remote handler function when composing a message, which can be quite limiting even within the context of a <a href="/facts/SPMD/SEDIrB0l">SPMD</a> programming model (and generally relies upon address space uniformity which is absent in many modern systems). Newer active message interfaces require the client to register a table with the software at initialization time that maps an integer index to the local address of a handler function; in these systems the sender of an active message provides an index into the remote handler table, and upon arrival of the active message the table is used to map this index to the handler address that is invoked to handle the message.
<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a>
</p><p>Other variations of active messages carry the actual code itself, not a pointer to the code. The message typically carries some data.  On arrival at the receiving end, more data is acquired, and the computation in the active message is performed, making use of data in the message as well as data in the receiving node.  This form of active messaging is not restricted to <a href="/facts/SPMD/SEDIrB0l">SPMD</a>, although originator and receiver must share some notions as to what data can be accessed at the receiving node.
</p>
<h2 id="integration-usage-for-micro-services-orchestration-esb-architecture">Integration, usage for micro-services, orchestration, ESB architecture</h2>
<p>A higher level implementation for active messages is also named Swarm communication in the SwarmESB project. The basic model of the active messages is extend with new concepts and JavaScript is used to express the code of the active messages.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Remote_procedure_call/uMMb9CQw">Remote procedure call</a></li></ul>

<h2 id="sources-and-external-links">Sources and external links</h2>
<ul><li><a href="https://web.archive.org/web/20070610055547/http://www.tc.cornell.edu/Services/Education/Topics/Parallel/Distributed/%2B6.3%2BActive%2BMessages.htm">https://web.archive.org/web/20070610055547/http://www.tc.cornell.edu/Services/Education/Topics/Parallel/Distributed/%2B6.3%2BActive%2BMessages.htm</a></li>
<li><a href="https://github.com/salboaie/SwarmESB/">https://github.com/salboaie/SwarmESB/</a></li>
<li><a href="http://gasnet.lbl.gov">GASNet</a> - A communications middleware layer that includes Active Messages and Remote Memory Access (RMA), implemented over a wide variety of network hardware</li>
<li><a href="https://gasnet.lbl.gov/amudp">AMUDP</a> - Active Messages (AM-2) over <a href="/facts/User_Datagram_Protocol/dxLU0D6q">UDP</a> (a standard component of the <a href="/facts/Internet_protocol_suite/KNkxtSpw">TCP/IP protocol stack</a>)</li>
<li><a href="https://gasnet.lbl.gov/ammpi">AMMPI</a> - Active Messages (AM-2) over <a href="/facts/Message_Passing_Interface/BEuBgDpm">MPI</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>"The operational semantics of an active message system", ACM Portal.  Accessed July 20, 2009 <a href="http://portal.acm.org/citation.cfm?id=131261" target="_blank">http://portal.acm.org/citation.cfm?id=131261</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Thorsten von Eicken, David E. Culler, Seth Copen Goldstein, Klaus Erik Schauser, "Active messages: a mechanism for integrated communication and computation", Proceedings of the 19th annual international symposium on Computer architecture (ISCA'92), May 1992, ACM. <a href="//doi.org/10.1145/139669.140382" target="_blank">//doi.org/10.1145/139669.140382</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Alan M. Mainwaring and David E. Culler, "Active Message Applications Programming Interface and Communication Subsystem Organization" (AM-2 Specification), EECS Department, University of California, Berkeley Technical Report No. UCB/CSD-96-918, October 1996. <a href="http://now.cs.berkeley.edu/active.html" target="_blank">http://now.cs.berkeley.edu/active.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>Dan Bonachea and Paul H. Hargrove. "GASNet specification, v1.8.1". Lawrence Berkeley National Laboratory Technical Report LBNL-2001064, August 2017. <a href="https://doi.org/10.2172/1398512" target="_blank">https://doi.org/10.2172/1398512</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
</ol>

Active message open-in-new

Active message