ruby: correct network test functionality.
Review Request #2423 - Created Sept. 24, 2014 and discarded
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 10425:b229e72bfcc6 --------------------------- ruby: correct network test functionality. One of the recent change sets altered ruby port to abort when a port already on the retry list is again becomes a candidate for addition. The network tester was failing because of this assert() since it issues requests for same addresse in a rapid succession. Since the network test should issue requests at the rate at which it is configured, the code is being changed so that the are chosen randomly over the available address space. Other changes are being made to conform the network test protocol with some of the recent changes to the ruby memory system. Some unused code in the sequencer is being removed as well.
Issue Summary
2
2
0
0
| Description | From | Last Updated | Status |
|---|---|---|---|
| I know we've had this discussion before, but should this be Addr rather than Uint64? | Andreas Hansson | Sept. 25, 2014, 12:12 a.m. | Open |
| I guess this is an intended change? Could you elaborate on the logic behind it? Also, size - 1 | Andreas Hansson | Sept. 25, 2014, 12:12 a.m. | Open |
-
src/cpu/testers/networktest/NetworkTest.py (Diff revision 1) -
I know we've had this discussion before, but should this be Addr rather than Uint64?
-
src/cpu/testers/networktest/networktest.cc (Diff revision 1) -
I guess this is an intended change? Could you elaborate on the logic behind it? Also, size - 1
Some small things and request for comments