For your first question, MARSS doesn't support the MESIF protocol yet (though, it could be added, see: http://spcl.inf.ethz.ch/Publications/.pdf/ramos-hoefler-cc-modeling.pdf). It simulates hierarchies using the MOESI/MESI coherence protocols. The 'F' (forward) state is just an optimization that reduces the amount of traffic on the bus in certain instances (i.e., instead of many node responding, one node can respond).
I don't work with the memory system that much, so I don't know how things are implemented. It should depend on what states the lines are in, your configuration, etc. Maybe somebody else can offer more insight. Tyler > Hi, > > 1.Xeon is using MESIF which F sate shows which core sends shared data when > a new core needs it. This omits any conflict. How is this happening in > MARSS MESI snoopy protocol? Every core who shares the data tries to send > the data? > > 2. In the case that few cores are sharing a data and another core faces > miss, the data can come either from lower memory or the other core. what > exactly happens in MARSS? It should be like this: since all of the cores > and lower memory receive the messages, they understand that another core > is > sending data so they annul that entry from their queue. is this right? > also how is it happening with switch interconnect? > > Thank you > Alireza > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > _______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
