There are two different memory systems in gem5: classic and ruby. It seems that neither are a complete fit for your case. But I would like to claim that ruby is a better choice. Others might have a different opinion. Comments below are with respect to the ruby memory system.
On Wed, January 23, 2013 7:41 am, preethi pd wrote: > Hi Nilay, > > > Thanks for ur mail. > > No my configuration will be > > 1. Private L1 cashes with shared L2 in bus based clusters with a > write-through read policy. Buses are not supported. But you can build a cluster using a switch. Write through caches are also not supported. You will have to modify the coherence protocols to implement write-through policy. > > 2. Shared L2s distributed in a NoC interconnection manner with Directory > based write-back coherency with memory. This is already in place. There are several different coherence protocols available. Read the documentation available on gem5.org. -- Nilay _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
