Closed udaymallappa closed 2 years ago
sorry, but the most common use-case we imagined for table traffic is explicitly experimenting with different traffic flows with different rates... so with this assumption in mind for us this was the most comfortable way to do that. PIR = packet/cycle/node
Sure got it. Just a slightly unrelated follow-up question. I also looked at your "table-based custom routing" syntax. Is there an easy way to provide static VC assignments in each line of the custom routing-table file ?
I think no, because VC have been added after the development of that part of code. But it's opensource, you can modify by yourself when it's not natively suppported....
In table-based traffic, pir of 0.0005 is just packet injection rate. The pir 0.0005 ==> 1 packet for every 2000 cycles ? Sweeping the injection rate demands for modifying the file. This is so unintuitive. It should have been a fixed packet as the third argument and "pir" should be controlled using the command line argument instead of changing this text file.
The node label is from 0 to n-1 I assume.
64 255 0.0005 3 103 0.0007