summaryrefslogtreecommitdiff
path: root/src/mem/protocol/RubySlicc_Defines.sm
diff options
context:
space:
mode:
authorNilay Vaish <nilay@cs.wisc.edu>2014-01-04 00:03:31 -0600
committerNilay Vaish <nilay@cs.wisc.edu>2014-01-04 00:03:31 -0600
commit5b1804e3bdb88aea7a198ff25617bb671cd34769 (patch)
tree38c8644bb17caaa708e6c678f0f495d7db5f74dc /src/mem/protocol/RubySlicc_Defines.sm
parent9853ef6651e76883615595bf76f983ed43234f96 (diff)
downloadgem5-5b1804e3bdb88aea7a198ff25617bb671cd34769.tar.xz
ruby: add support for clusters
A cluster over here means a set of controllers that can be accessed only by a certain set of cores. For example, consider a two level hierarchy. Assume there are 4 L1 controllers (private) and 2 L2 controllers. We can have two different hierarchies here: a. the address space is partitioned between the two L2 controllers. Each L1 controller accesses both the L2 controllers. In this case, each L1 controller is a cluster initself. b. both the L2 controllers can cache any address. An L1 controller has access to only one of the L2 controllers. In this case, each L2 controller along with the L1 controllers that access it, form a cluster. This patch allows for each controller to have a cluster ID, which is 0 by default. By setting the cluster ID properly, one can instantiate hierarchies with clusters. Note that the coherence protocol might have to be changed as well.
Diffstat (limited to 'src/mem/protocol/RubySlicc_Defines.sm')
-rw-r--r--src/mem/protocol/RubySlicc_Defines.sm2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mem/protocol/RubySlicc_Defines.sm b/src/mem/protocol/RubySlicc_Defines.sm
index 011cb7664..f3923eb9f 100644
--- a/src/mem/protocol/RubySlicc_Defines.sm
+++ b/src/mem/protocol/RubySlicc_Defines.sm
@@ -31,4 +31,4 @@
NodeID id;
NodeID version;
MachineID machineID;
-
+NodeID clusterID;