The classic M5 cache hierarchy doesn't maintain inclusion, so any request the L2 sees from other L2s or an L3 must be forwarded up so the L1s above it can snoop it too.
On Thu, Mar 10, 2011 at 11:06 AM, Chao Chen <[email protected]> wrote: > Hi, > > The command line of such packet is ReadReq. > The broadcast is on the bus between L1 and L2. > Broadcast source is L2, but destinations are all snooping L1s. > I see in bus.cc, such case is commented as > "// Must be forwarded snoop up from below..." > Could you explain it a little bit in detail? > > Thanks, > Chao > > > > > Quoting Chao Chen <[email protected]>: > > Hi, >> >> I find there are some broadcast packets in M5 interconnect. They have >> the same destinations are their source. I seems that in this case, the >> packets are deleted by source instead of memory or higher level cache. >> I could see a lot of this kinds of packets when simulating PARSEC >> benchmark but not any when running NAS benchmarks. Could anyone help >> explain what are these packets used for? Are they related with PARSEC >> hooks lib? >> >> Thanks, >> Chao >> >> > > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >
_______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
