The assertion is that the message reached a destination it was not
meant to. The change in routing algorithm, if correct, should not cause
this.
Can you print out the message and the destination to check whether the
request actually reached a destination it was not intended too?
-Niket
Zhang Yu wrote:
Hi,
I modified the routing algorithm of the garnet-fixed network, however,
when I run the simulation with this new routing algorithm, I countered
this problem:
Runtime Error at ../protocols/MOESI_CMP_directory-L2cache.sm:659, Ruby
Time: 750953: assert failure, PID: 25881
Does anybody have any idea how this happen? The new routing algorithm I
implemented may detour from the source to the destination, which means
the traverse path may not be the shortest one, could this be the
problem?
Thanks,
Yu
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
|
|