From b48156346e720c11ba5e7d096f7e2c6e455be497 Mon Sep 17 00:00:00 2001 From: Christian Heinrich Date: Thu, 9 Apr 2015 18:42:21 +0200 Subject: [PATCH] Updated section on network equipments (mostly cosmetics). - Added the backbone tag, though --- doc/doxygen/platform.doc | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/doxygen/platform.doc b/doc/doxygen/platform.doc index 0587c4cb6f..d8cbe6f6d9 100644 --- a/doc/doxygen/platform.doc +++ b/doc/doxygen/platform.doc @@ -433,16 +433,16 @@ is completely equivalent to the following declaration: \subsection pf_ne Network equipments: links and routers -There are two tags available to represent network entities: +There are two tags at all times available to represent network entities and +several other tags that are available only in certain contexts. 1. ````: Represents a entity that has a limited bandwidth, a latency, and that can be shared according to TCP way to share this bandwidth. \remark -The concept of links in SimGrid may not be intuitive, as links are not limited -to connecting (exactly) two entities; in fact, you can have more than two equipments -connected to it. (In graph theoretical terms: A link in SimGrid is not an edge, -but a hyperedge) -\endremark + The concept of links in SimGrid may not be intuitive, as links are not limited + to connecting (exactly) two entities; in fact, you can have more than two equipments + connected to it. (In graph theoretical terms: A link in SimGrid is not an edge, + but a hyperedge) 2. ````: Represents an entity that a message can be routed to, but that is unable to execute any code. In SimGrid, routers have also @@ -450,6 +450,9 @@ but a hyperedge) do they increase latency. As a matter of fact, routers are (almost) ignored by the simulator when the simulation has begun. +3. ````: This tag is only available when the containing AS is + used as a cluster (i.e., mode="Cluster") + \remark If you want to represent an entity like a switch, you must use ```` (see section). Routers are used to run some routing algorithm and determine routes (see Section \ref pf_routing for details). -- 2.20.1