MCAPI
≈ 2 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
The Multicore Communications API (MCAPI) is the first specification to be produced by the Multicore Association. MCAPI provides a standardized API for communication and synchronization between closely distributed (multiple cores on a chip and/or chips on a board) embedded systems.
The Multicore Communications API (MCAPI) is the first specification to be produced by the Multicore Association. MCAPI provides a standardized API for communication and synchronization between closely distributed (multiple cores on a chip and/or chips on a board) embedded systems.
Overview
MCAPI is a language-independent, processor and operating system agnostic communications protocol used to program multi-core devices. MCAPI provides three modes of communication: messages, packets, and scalars. MCAPI is a message-passing application programmer interface, together with protocol and semantic specifications for how its features must behave in any implementation. The primary goals for any MCAPI implementation are extremely high performance and low memory footprint. MCAPI traces its heritage to communications APIs such as MPI and Berkeley sockets. Both MPI and sockets were developed primarily with inter-computer communication in mind, while MCAPI is targeted primarily towards inter-core communication in a multicore chip. Accordingly, a principal design goal of MCAPI was to serve as a low-latency interface leveraging efficient on-chip interconnect in a multicore chip. However, because of the more limited scope of multicore communications and its goal of low latency, MCAPI is less flexible than MPI or Sockets.
MCAPI Communication Modes
MCAPI provides three modes of communication: messages – connection-less datagrams. Messages are intended to be flexible with respect to payload, dynamically changing receivers and priorities and configuration effort, although at a slight performance penalty. packets – connection-oriented, arbitrary size, uni-directional, and FIFO streams. Packets are intended to be flexible with respect to payload, providing higher performance than messages at the expense of configuration effort. scalars – connection-oriented, fixed size, uni-directional, and FIFO streams. Scalars are intended to be the highest performance communications mode, albeit at the expense of payload flexibility and configuration effort. Free MCAPI specification download LinkedIn Profile API
Text derived from https://en.wikipedia.org/w/index.php?oldid=1374819760 under CC BY-SA 4.0; modifications have been made.