pe_macro(1)
0
0 f
f
ff
r
r
r
t
t
t
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0
0 0 0
Before
After
After
Unused
Unused
MPP_FIG_286
f
c
9
6
3
0
rosend64
rosend64
rfetchc64
rt2c
: Forward Router Send Test — This test asks each PE to make a
router send transfer in the forward direction (to a PE whose address is
higher). This requires 16 operations before all the contentions have been
resolved.
The test starts with each PE making a send to itself (offset = 0). Then,
each PE successively sends data to the PE whose address is offset from
its own by a factor of +1 to +511.
If the test detects an error, it prints an error message giving the router
offset at which the error occurred, the nature of the error, the expected
and actual result.
rt2d
: Forward Router Fetch Test — This test asks each PE to make a
router fetch transfer from the forward direction (from a PE whose address
is higher). This requires 16 operations before all the contentions have
been resolved.
The test starts with each PE making a fetch from itself (offset = 0). Then,
each PE successively fetches data from the PE whose address is offset
from its own by a factor of +1 to +511.
If the test detects an error, it prints an error message giving the router
offset at which the error occurred, the nature of the error, the expected
and actual result.
rt2e
: Reverse Router Send Test — This test asks each PE to make a
router send transfer in the reverse direction (to a PE whose address is
lower). This requires 16 operations before all the contentions have been
resolved.
The test starts with each PE making a send to itself (offset = 0). Then,
each PE successively sends data to the PE whose address is offset from
its own by a factor of –1 to –511.
If the test detects an error, it prints an error message giving the router
offset at which the error occurred, the nature of the error, the expected
and actual result.
rt2f
: Reverse Router Fetch Test — This test asks each PE to make a
router fetch transfer from the reverse direction (from a PE whose address
is lower). This requires 16 operations before all the contentions have been
resolved.
The test starts with each PE making a fetch from itself (offset = 0). Then,
each PE successively fetches data from the PE whose address is offset
from its own by a factor of –1 to –511.
B–50 Data Parallel Unit Reference Pages
