[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

2023-03-25 Thread Srikant Bharadwaj via gem5-users
Change the virtual network for request, forward, and response to a single vnet (0) in the following files and then set the src/mem/ruby/protocol/Garnet_standalone-cache.sm src/mem/ruby/protocol/Garnet_standalone-dir.sm Then restrict the number of vnets to 1 in configs/ruby/Garnet_standalone.py

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

2023-03-25 Thread Karim Soliman via gem5-users
Yes, please can you help me to modify the files into src/mem/ruby/ as I understand till now, inside garnet 3.0 we have 3 types of messages/classes - requests - forward - response. Each one of these classes has its own virtual network separated from the other classes. - requests, and

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

2023-03-25 Thread Srikant Bharadwaj via gem5-users
Hi Karim, The virtual network is the protocol level sub network. The virtual channels indicate the number of parallel buffer streams in each virtual network. To achieve a protocol deadlock you will have to set a single virtual network and then force the different types of messages (request,

[gem5-users] Re: Gem5 - garnet 3.0 - Mesh_XY - Deadlock

2023-03-25 Thread 赵子丰 via gem5-users
hi, The virtual networks are mainly used for avoiding protocol deadlocks, i.e., one message type per vnet. the output 5 virtual channels is because you set vcs-per-vnet=1(i.e., one virtual channel per vnet) and the garnet model has 5 virtual networks (I think so) As for the last problem, it's