Average Network Latency has just been renamed to Average Network Flit Latency since Garnet2.0 also reports the Average Network Packet Latency.
Please take a look at the gem5 wiki for a detailed description of garnet1.0 vs 2.0. http://www.gem5.org/Garnet http://www.gem5.org/Garnet2.0 I’m not sure what validating one against the other means. Garnet2.0 uses a 1-cycle router by default so the network latency is not expected to match that from the original garnet1.0 paper which assumed a 4-cycle router as the default. You can mimic a 4-cycle router in garnet2.0 by setting --router-latency=4 (look at configs/network/Network.py) but it will not match exactly. Cheers, Tushar On May 24, 2017, at 6:11 AM, F. A. Faisal <dipu.7...@gmail.com<mailto:dipu.7...@gmail.com>> wrote: Dear All, I wanted to validate the garnet 2.0 with garnet 1.0. Hence, I like to get the average network latency or the average latency. However, this parameter is missing from the stats.txt file in garnet 2.0. And even I compare the average packet latency of garnet 2.0 (21.487374) with the garnet 1.0 average latency (40.403994) for 8x8 mesh with same configuration as referenced paper of garnet, which is completely different. Please let me know how to validate garnet 2.0 as of garnet 1.0. Thanks in advance. Best regards, F. A. Faisal _______________________________________________ gem5-users mailing list gem5-users@gem5.org<mailto:gem5-users@gem5.org> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
