| .. | ||
| CMakeLists.txt | ||
| fairmq-start-ex-multiple-transports.sh.in | ||
| README.md | ||
| runSampler1.cxx | ||
| runSampler2.cxx | ||
| runSink.cxx | ||
| Sampler1.cxx | ||
| Sampler1.h | ||
| Sampler2.cxx | ||
| Sampler2.h | ||
| Sink.cxx | ||
| Sink.h | ||
| test-ex-multiple-transports.sh.in | ||
Multiple Transports example
This example demonstrates use of multiple transports (zeromq/shmem) within the same topology and/or device. It is a simple topology consisting of two samplers and a sink. The devices are connected via 3 channels:
Each device has main transport that it uses. By default it is ZeroMQ, and can be overriden via the --transport cmd option. The device will initialize additional transports if any of the channels have them configured (e.g. as an option to --channel-config).
In this example sampler1 and sink are started with --transport shmem, making shared memory their main transport, sampler2 with --transport zeromq. Additionally, the ack channel is configured to use zeromq as its transport.
The main two things that a transport does is transfer of data and allocation of memory for the messages. By default, new messages are created via the main device transport. If a message has been created with one transport and is to be transferred with another, it has to be copied into a new message of the target transport. This happens automatically behind the scenes. To avoid this copy the device can create messages via NewMessageFor(const string& channelName, int subChannelIndex, ...) method, that creates the messages via the transport of the given channel (check sampler1 and sink for an example) or as the channel directly to create a message.