Escali 4.4 manual Inlining protocol, Eagerbuffering protocol, Transporter protocol

Section: 2.3 Communication protocols on DAT-devices

Figure 2-4:Resources and communication concepts in Scali MPI Connect

2.3.2 Inlining protocol

With the in-lining protocol the application’s data is included in the message header. The in- lining protocol utilizes one or more channel ringbuffer entries.

2.3.3 Eagerbuffering protocol

The eagerbuffering protocol is used when medium-sized messages are to be transferred. The protocol uses a scheme where the buffer resources which are allocated by the sender are released by the receiver, without any explicit communication between the two communicating partners.

The eagerbuffering protocol uses one channel ringbuffer entry for the message header, and one eagerbuffer for the application data being sent.

2.3.4 Transporter protocol

The transporter protocol is used when large messages are to be transferred. The transporter protocol utilizes one channel ringbuffer entry for the message header, and transporter buffers for the application data being sent. The protocol takes care of fragmentation and reassembly of large messages, such as those whose size is larger than the size of the transporter ringbuffer-entry (transporter_size).

Scali MPI Connect Release 4.4 Users Guide 17