Configuring ns-3
^^^^^^^^^^^^^^^^
-**Option** ``ns3/TcpModel`` **Default:** "default" (ns-3 default)
+**Option** ``ns3/NetworkModel`` **Default:** "default" (ns-3 default TCP)
-When using ns-3, there is an extra item ``ns3/TcpModel``, corresponding
-to the ``ns3::TcpL4Protocol::SocketType`` configuration item in
-ns-3. The only valid values (enforced on the SimGrid side) are
-'default' (no change to the ns-3 configuration), 'NewReno' or 'Reno' or
-'Tahoe'.
+When using ns-3, the item ``ns3/NetworkModel`` can be used to switch between TCP or UDP, and switch the used TCP variante. If
+the item is left unchanged, ns-3 uses the default TCP implementation. With a value of "UDP", ns-3 is set to use UDP instead.
+With the value of either 'NewReno' or 'Cubic', the ``ns3::TcpL4Protocol::SocketType`` configuration item in ns-3 is set to the
+corresponding protocol.
**Option** ``ns3/seed`` **Default:** "" (don't set the seed in ns-3)
- if (size < :ref:`smpi/async-small-thresh <cfg=smpi/async-small-thresh>`) then
MPI_Send returns immediately, and the message is sent even if the
- corresponding receive has not be issued yet.
+ corresponding receive has not be issued yet. This is known as the eager mode.
- if (:ref:`smpi/async-small-thresh <cfg=smpi/async-small-thresh>` < size <
:ref:`smpi/send-is-detached-thresh <cfg=smpi/send-is-detached-thresh>`) then
MPI_Send also returns immediately, but SMPI waits for the corresponding
- receive to be posted, in order to perform the communication operation. This is
- known as the eager mode.
+ receive to be posted, in order to perform the communication operation.
- if (:ref:`smpi/send-is-detached-thresh <cfg=smpi/send-is-detached-thresh>` < size) then
MPI_Send returns only when the message has actually been sent over the network. This is known as the rendez-vous mode.