1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE platform SYSTEM "https://simgrid.org/simgrid.dtd">
<platform version="4.1">
<zone id="world" routing="Full">
<!-- this platform models 3 clusters, interconnected over the Internet
-
- This example intends to be somewhat exhaustive, your platform should probably be simpler.
-
- In particular, the clusters are modeled in very different ways,
- but you should pick the way you prefer, and stick to it.
-->
<!-- Here comes the first cluster, the simplest one.
Every nodes are connected through a private link to a router
(ie a machine that cannot host computations).
node-0.1core.org __[l0]__
\
node-1.1core.org __[l1]__router___(outer world)
... /
node-7.1core.org __[l9]_/
So the route from node-0 to node-1 is {l0.UP, l1.DOWN}
-->
<cluster bw="125MBps" id="simple" lat="50us" prefix="node-" radical="0-7" speed="1Gf" suffix=".1core.org">
<prop id="wattage_per_state" value="0.0:1.0:1.0" />
<prop id="wattage_off" value="0.0" />
</cluster>
<!-- This second cluster has a backbone link, connecting all private links:
node-0.2cores.org __[l0]______+
|
node-1.2cores.org __[l1]__[backbone]__ router __ (outer world)
... |
node-7.2cores.org __[l7]______+
The route from node-0 to node-1 is: l0.UP ; backbone ; l1.DOWN
The route from node-0 to the outer world begins with: l0.UP ; backbone
-->
<cluster bb_bw="2.25GBps" bb_lat="500us" bw="125MBps" core="2" id="backboned" lat="50us" prefix="node-" radical="0-7" speed="1Gf" suffix=".2cores.org">
<prop id="wattage_per_state" value="0.0:0.0:2.0" />
<prop id="wattage_off" value="0.0" />
</cluster>
<!-- This cluster has a backbone link, but no links are splitduplex.
- It means that up and down communications compete as if they
- were using exactly the same resource. If you send and receive
- at the same time, then each get half of the bandwidth.
-
- Also, the hosts have 4 cores.
-->
<cluster bb_bw="2.25GBps" bb_lat="500us" bb_sharing_policy="SHARED" bw="125MBps" core="4" id="halfduplex" lat="50us" prefix="node-" radical="0-7" sharing_policy="SHARED" speed="1Gf" suffix=".4cores.org">
<prop id="wattage_per_state" value="0.0:0.0:4.0" />
<prop id="wattage_off" value="0.0" />
</cluster>
<!-- And now, we create the routes between the clusters, ie inter-zone routes -->
<!-- We have only one outer link, representing the internet
- Its sharing is FATPIPE, meaning that communications have no impact on each others.
- Any given comm can use the full provided bandwidth.
-
- This models the big links constituting the backbone of the internet,
- that users cannot saturate.
- Users' bandwidth is mostly limited by their outgoing connection,
- not by the network backbone.
-->
<link bandwidth="1.25GBps" id="backbone" latency="500us" sharing_policy="FATPIPE" />
<zoneRoute dst="backboned" gw_dst="node-backboned_router.2cores.org" gw_src="node-simple_router.1core.org" src="simple">
<link_ctn id="backbone" />
</zoneRoute>
<zoneRoute dst="halfduplex" gw_dst="node-halfduplex_router.4cores.org" gw_src="node-simple_router.1core.org" src="simple">
<link_ctn id="backbone" />
</zoneRoute>
<zoneRoute dst="halfduplex" gw_dst="node-halfduplex_router.4cores.org" gw_src="node-backboned_router.2cores.org" src="backboned">
<link_ctn id="backbone" />
</zoneRoute>
</zone>
</platform>
|
