Yes, there isn't any back pressure here and there probably/maybeshould be. The reason we've got away with it before is that normally the pressure comes from the cpu itself. The number of outstanding translations is limited by the size of the LSQ. That is why I find this to be strange. there is some code that is executing and must be mis-predicting constantly to fill up the tlb with translations and the get squashed, only to do the exact same thing again. It seems like the second time through the branch should be correct. The fastest way forward is probably to add the ability to squash all pending tlb translations (except maybe the one that is currently going on) as you through those instructions out of the lsq on a mispredict. Make sense?
Ali On May 15, 2012, at 8:48 AM, Gabe Black wrote: > There's a limit on the size of the TLB itself, but there may not be a limit > on the number of translations it's doing at one time. I suspect that's an > important part of the problem. > > Gabe > > _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
