ruby: fix MESI_Three_Level protocol
Review Request #3441 - Created April 4, 2016 and updated
Changeset 11443:34fcc3f9f957 --------------------------- ruby: fix MESI_Three_Level protocol
|This change connects the L0 caches to the network rather than connecting them directly to the L1 caches. Since both ...||Joel Hestness||April 13, 2016, 12:08 p.m.||Open|
Before this patch this protocol was broken? From the changes, it doesn't even look like it would have compiled. Is this true? In one way I'm shocked this happend. In another I'm not surprised at all... :(
I'm not clear how this change fixes the exception noted above. Can you elaborate?
Also, the diff here doesn't apply cleanly to the current mainline head. Is there another patch that needs to be applied before this?
configs/ruby/MESI_Three_Level.py (Diff revision 1)
This change connects the L0 caches to the network rather than connecting them directly to the L1 caches. Since both are private to the connected core, it seems superfluous to run their activity through the network; They only communicate with each other through these MessageBuffers.
Is there a bigger need for this that I'm not seeing?