Hi, all, I try to understand the mechanism Ruby uses to handle the case when a request comes by for the same cacheline to an outstanding request. As I look into the code, Ruby will kind of reject the later request, indicating that "the address is aliased". And the O3CPU gets this response and retries sending the request later. In terms of performance, this implementation is unrealistic for me, since accesses to the same cacheline are serialised, which should be a parallel fashion. For example, if the outstanding request is experiencing a miss (primary miss), then the later one (secondary miss) could be merged into it and gets data simultaneously when the miss completes. Am I missing something? Any help is welcome.
Yuan _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
