gem5 documentation
Development
Building
Using KVM
Sphinx Documentation
Doxygen
gem5 APIs
Full System
Checkpoints
Directed Testers
Debugging
Architecture Support
Power and Thermal Model
Compiling Workloads
Stats Package
Stats API
Develop Branch
v19.0.0.0
v20.0.0.0
v20.0.0.2
v20.0.0.3
v20.1.0.0
v20.1.0.1
v20.1.0.5
v21.0.0.0
v21.0.1.0
v21.1.0.0
v21.1.0.1
v21.1.0.2
v21.2.0.0
v21.2.1.0
v21.2.1.1
v22.0.0.0
v22.0.0.1
v22.1.0.0
v23.0.0.0
v23.0.0.1
gem5 standard library
Standard Library Overview
Hello World Tutorial
X86 Full-System Tutorial
Developing Your Own Components Tutorial
How To Create Your Own Board Using The gem5 Standard Library
How to use local resources and data sources in gem5
gem5 Resources
Creating Disk Images
Devices
m5term
Building Linux ARM Kernel
Building Android Marshmallow
Guest binaries
Memory System
Memory System
gem5 Memory System
Replacement Policies
Indexing Policies
Classic memory system coherence
Classic caches
Ruby Memory System
Ruby
Cache Coherence Protocols
Garnet 2.0
HeteroGarnet
MOESI CMP directory
Garnet Synthetic Traffic
SLICC
MI example
Garnet standalone
Interconnection network
MOESI hammer
MOESI CMP token
MESI two level
CHI
Replacement Policies
CPU Models
GPU Models
M5ops
authors: Jason Lowe-Power
last edited: 2024-12-20 23:08:46 +0000
last edited: 2024-12-20 23:08:46 +0000
MOESI CMP Directory
Protocol Overview
- TODO: cache hierarchy
- In contrast with the MESI protocol, the MOESI protocol introduces an additional Owned state.
- The MOESI protocol also includes many coalescing optimizations not available in the MESI protocol.
Related Files
- src/mem/protocols
- MOESI_CMP_directory-L1cache.sm: L1 cache controller specification
- MOESI_CMP_directory-L2cache.sm: L2 cache controller specification
- MOESI_CMP_directory-dir.sm: directory controller specification
- MOESI_CMP_directory-dma.sm: dma controller specification
- MOESI_CMP_directory-msg.sm: message type specification
- MOESI_CMP_directory.slicc: container file
L1 Cache Controller
Stable States and Invariants
| States | Invariants |
|---|---|
| MM | The cache block is held exclusively by this node and is potentially modified (similar to conventional “M” state). |
| MM_W | The cache block is held exclusively by this node and is potentially modified (similar to conventional “M” state). Replacements and DMA accesses are not allowed in this state. The block automatically transitions to MM state after a timeout. |
| O | The cache block is owned by this node. It has not been modified by this node. No other node holds this block in exclusive mode, but sharers potentially exist. |
| M | The cache block is held in exclusive mode, but not written to (similar to conventional “E” state). No other node holds a copy of this block. Stores are not allowed in this state. |
| M_W | The cache block is held in exclusive mode, but not written to (similar to conventional “E” state). No other node holds a copy of this block. Only loads and stores are allowed. Silent upgrade happens to MM_W state on store. Replacements and DMA accesses are not allowed in this state. The block automatically transitions to M state after a timeout. |
| S | The cache block is held in shared state by 1 or more nodes. Stores are not allowed in this state. |
| I | The cache block is invalid. |
FSM Abstraction
The notation used in the controller FSM diagrams is described here.
Optimizations
| States | Description |
|---|---|
| SM | A GETX has been issued to get exclusive permissions for an impending store to the cache block, but an old copy of the block is still present. Stores and Replacements are not allowed in this state. |
| OM | A GETX has been issued to get exclusive permissions for an impending store to the cache block, the data has been received, but all expected acknowledgments have not yet arrived. Stores and Replacements are not allowed in this state. |
The notation used in the controller FSM diagrams is described here.
L2 Cache Controller
Stable States and Invariants
| Intra-chip Inclusion | Inter-chip Exclusion | States | Description |
|---|---|---|---|
| Not in any L1 or L2 at this chip | May be present at other chips | NP/I | The cache block at this chip is invalid. |
| Not in L2, but in 1 or more L1s at this chip | May be present at other chips | ILS | The cache block is not present at L2 on this chip. It is shared locally by L1 nodes in this chip. |
| ILO | The cache block is not present at L2 on this chip. Some L1 node in this chip is an owner of this cache block. | ||
| ILOS | The cache block is not present at L2 on this chip. Some L1 node in this chip is an owner of this cache block. There are also L1 sharers of this cache block in this chip. | ||
| Not present at any other chip | ILX | The cache block is not present at L2 on this chip. It is held in exclusive mode by some L1 node in this chip. | |
| ILOX | The cache block is not present at L2 on this chip. It is held exclusively by this chip and some L1 node in this chip is an owner of the block. | ||
| ILOSX | The cache block is not present at L2 on this chip. It is held exclusively by this chip. Some L1 node in this chip is an owner of the block. There are also L1 sharers of this cache block in this chip. | ||
| In L2, but not in any L1 at this chip | May be present at other chips | S | The cache block is not present at L1 on this chip. It is held in shared mode at L2 on this chip and is also potentially shared across chips. |
| O | The cache block is not present at L1 on this chip. It is held in owned mode at L2 on this chip. It is also potentially shared across chips. | ||
| Not present at any other chip | M | The cache block is not present at L1 on this chip. It is present at L2 on this chip and is potentially modified. | |
| Both in L2, and 1 or more L1s at this chip | May be present at other chips | SLS | The cache block is present at L2 in shared mode on this chip. There exists local L1 sharers of the block on this chip. It is also potentially shared across chips. |
| OLS | The cache block is present at L2 in owned mode on this chip. There exists local L1 sharers of the block on this chip. It is also potentially shared across chips. | ||
| Not present at any other chip | OLSX | The cache block is present at L2 in owned mode on this chip. There exists local L1 sharers of the block on this chip. It is held exclusively by this chip. |
FSM Abstraction
The controller is described in 2 parts. The first picture shows transitions between all “intra-chip inclusion” categories and within categories 1, 3, 4. Transitions within category 2 (Not in L2, but in 1 or more L1s at this chip) are shown in the second picture.
The notation used in the controller FSM diagrams is described here. Transitions involving other chips are annotated in brown.
The second picture below expands the central hexagonal portion of the above picture to show transitions within category 2 (Not in L2, but in 1 or more L1s at this chip).
The notation used in the controller FSM diagrams is described here. Transitions involving other chips are annotated in brown.
Directory Controller
**Stable States and
Invariants**
| States | Invariants |
|---|---|
| M | The cache block is held in exclusive state by only 1 node (which is also the owner). There are no sharers of this block. The data is potentially different from that in memory. |
| O | The cache block is owned by exactly 1 node. There may be sharers of this block. The data is potentially different from that in memory. |
| S | The cache block is held in shared state by 1 or more nodes. No node has ownership of the block. The data is consistent with that in memory (Check). |
| I | The cache block is invalid. |
FSM Abstraction
The notation used in the controller FSM diagrams is described here.
