Hi Nilay, Thanks for throwing light on this. I want to arbitrate request packets originated the core (requiring off-chip memory access) at the router. Do you think this is possible in Gem5? My understanding was that both the memory request flits as well as network flits are routed via interconnection networks. So, I modified the SWallocator_d code. But now I am confused, if the memory request flits don't travel through the GARNET network towards the main memory, what path do the take to access main memory? I would really appreciate if you could elaborate more on this. Thanks!
On Thu, Oct 4, 2012 at 9:46 AM, Nilay Vaish <ni...@cs.wisc.edu> wrote: > On Tue, 2 Oct 2012, tejasi pimpalkhute wrote: > > Hi Tushar, >> >> Thanks for looking into the code, I tried running the Network_test >> protocol >> and got this error: >> >> Global frequency set at 1000000000 ticks per second >> info: Entering event queue @ 0. Starting simulation... >> gem5.debug: >> build/ALPHA_SE_Network_test/**mem/ruby/network/garnet/fixed-** >> pipeline/InputUnit_d.cc:78: >> virtual void InputUnit_d::wakeup(): Assertion `m_vcs[vc]->get_state() == >> IDLE_' failed. >> Program aborted at cycle 30 >> Aborted >> >> >> I used this command to run the test- >> ./build/ALPHA_SE_Network_test/**gem5.debug >> configs/example/ruby_network_**test.py --num-cpus=16 --num-dirs=16 >> --topology=Mesh --mesh-rows=4 --sim-cycles=1000 --injectionrate=0.01 >> --synthetic=0 --fixed-pkts --maxpackets=1000 --garnet-network=fixed >> >> >> On a side note, I also wanted to ask you if Ruby_random_test and >> Ruby_mem_test do inject any memory flits in the network. Because, I tried >> to dynamic cast the msgptr of these flits to MemoryMessage msgptr so that >> I >> can extract the information about its memory address and type, but it >> fails. Do you see any reason why it could be failing? I want to deal with >> both network packets and off-chip memory packets in the network. Can you >> please guide me which test will be appropriate for the same? >> >> > First, the Network test protocol does not access memory. Second, even > other protocols do not send messages to the memory via the network that you > are trying to modify. There are dedicated links between the directory > controllers and the memory controllers. > > The test to be used depends on what you want to test for. > > -- > Nilay > -- Tejasi
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
