Tushar
I am using the network tester in gem5 with GARNET. I am observing a
peculiar behavior when I run the following command --
./build/X86/gem5.fast ./configs/example/ruby_network_test.py --num-cpus=64
--num-dirs=64 --topology=Torus --garnet-network=flexible --mesh-rows=8
--sim-cycles=10000 -i 0.30 --random_seed=1
As you might recall, there three different types of messages generated by
the network tester -- request, forward and response, and these are
generated with ration 1:1:1. In the file ruby.stats, the number of
responses that reach the directory controllers are way less than compared
to the number of requests and forwards, the ratio being
10(request):10(forward):1(response) . It seems that the network interface
at the cache controller is not able to issue most of the response messages
and hence these keep waiting the in the queue at the input port.
Can you look into why this is happening?
Thanks
Nilay
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
