Logo AND Algorithmique Numérique Distribuée

Public GIT Repository
use SPLITDUPLEX internally instead of FULLDUPLEX
authorMartin Quinson <martin.quinson@loria.fr>
Fri, 16 Feb 2018 20:50:47 +0000 (21:50 +0100)
committerMartin Quinson <martin.quinson@loria.fr>
Sun, 18 Feb 2018 13:12:43 +0000 (14:12 +0100)
commit1bf71617c94b4c2ff15ac076992a24a0fdbaa897
treed2ad700de0fa03456df038dc281e6f7fefeb518b
parentafa70f683ba4eb6ea7ad7308babeed4596ceb78f
use SPLITDUPLEX internally instead of FULLDUPLEX

We will s/FULLDUPLEX/SPLITDUPLEX/ everywhere in SimGrid. Rational:

That sharing mode is modeled by spliting every link between two links:
one uplink used when traversing the link in a direction, and the
downlink when we traverse the same link in the other direction.

With SHARED links, the bandwidth is shared between all flows without
taking the flow direction into account.

So, SPLITDUPLEX is the way we model fullduplex links, but at the end,
each of the SimGrid link in a SPLITDUPLEX (either the up or down link)
can be used in one direction only. That's the right model, but using
FULLDUPLEX for the situation where you have 2 links was rather
disturbing.

And yes, users will soon notice, when they will try to use network
energy models.
include/simgrid/forward.h
src/bindings/lua/lua_platf.cpp
src/kernel/routing/ClusterZone.cpp
src/kernel/routing/DragonflyZone.cpp
src/kernel/routing/FatTreeZone.cpp
src/kernel/routing/TorusZone.cpp
src/surf/sg_platf.cpp
src/surf/xml/surfxml_sax_cb.cpp