>. If we really wanted to go fast in this case we'd come up with a > new memory interface that didn't use packets at all and just went straight > to PhysicalMemory, but we haven't felt the need to do that. If you dont mind, can you briefly elaborate on pros/cons of using a packet-interface instead of the alternative? I'm kind of mixed up in my understanding of what's going on there now that you brought that to my attention (Another "blackbox" that M5 has let me get away with abstracting the details from!)
This little tidbit from the wiki hints at the issue I believe: "A Packet is used to encapsulate a transfer between two objects in the memory system (e.g., the L1 and L2 cache). This is in contrast to a Request where a single Request travels all the way from the requester to the ultimate destination and back, possibly being conveyed by several different Packets along the way." Of course, this isn't time-sensitive, but it would be nice for me to better wrap my head around the design decision that happened there... -- - Korey _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
