The Multicore Communications API is the first specification to be produced by the Multicore Association. MCAPI provides a standardized API for communication and synchronization between closely distributed embedded systems.
Overview
MCAPI is a language-independent, processor and operating system agnostic communications protocol used to program multi-coredevices. MCAPI provides three modes of communication: messages, packets, and scalars. MCAPI is a message-passingapplication 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.
MCAPI Compared to MPI
MCAPI is focused purely on embedded communications, and adds the ideas of messages, packets, and scalars + connected channels. This allows MCAPI to support various quality of service, where connected channels may exploit underlying embedded hardware. Furthermore MCAPI supports various kinds of priorities, messages can have a per message priority and channels can be treated as having different priorities as well, allowing implementations to map some or all channels to dedicated hardware. MCAPI can also support zero-copy via assigning attributes to connected channels. Other big differences include:
MCAPI has no language binding for FORTRAN since this is not commonly found in embedded systems.
MCAPI does not support collective communications as in MPI. This allows MCAPIv to have a smaller implementation.
MCAPI does not have the concepts of groups.
MCAPI does not have any synchronization methods as in MPI, no barriers, no fences, no locks.
MCAPI has no file objects or any functions associated with them.
MCAPI has no model for creation or management of processes.
