Changes between Version 8 and Version 9 of Component/Mapping Table/Tables Creation

Timestamp:

Jan 26, 2010, 11:59:00 AM (14 years ago)

Author:

Nicolas Pouillon

Comment:

--

Component/Mapping Table/Tables Creation

@@ -48 +48 @@
 we have a 32-bit address:
 
-|| width:|| 8       || 4         || (the rest)      ||
-|| bits: || 31 — 24 ||23 —  20   || 19 — 0          ||
-|| field:|| vgmn    || lc0 & lc1 || rest of address ||
+|| widths:                || 8        || 4        || remaining bits ||
+|| bits:                  || 31 — 24  ||23 —  20  || 19 — 0         ||
+|| locality decision for: || lc0, lc1 ||          ||                ||
+|| routing decision for:  || vgmn     || lc0, lc1 ||                ||
 
 == Creating the routing tables ==
@@ -67 +68 @@
 
 When calling `getRoutingTable( IntTab(1) )`, the resulting routing table
-will only contain information about `seg2`, `seg3`  and `seg4`, which targets `(1, …)`.
+will only contain information about segments which targets `(1, …)`: `seg2`, `seg3`  and `seg4`.
+
 As the 8 first bits of address are assumed already decoded, the table only decodes the next 4 bits:
 
@@ -96 +98 @@
 Locality tables just tell whether an address is local to a subtree of the network or not.
 
-In the above example, locality table creation for local interconnect 0 (`getLocalityTable( IntTab(0) )`) would be:
+In the above example, locality table creation for local interconnect 0 (`getLocalityTable( IntTab(0) )`) would involve:
 
 || Name  ||  Address    || Address![31:24]|| Target cluster ||