Hello. I think it depends on the purpose of the table and modeling features.
For example, let's look a cache tag modeling case. BaseTags class (/mem/cache/tags/base.hh), which is a kind of table to store tags, inherits the ClockedObject, because BaseTags needs to model the clock latency. However, Cacheset class (/mem/cache/tags/cacheset.hh), which is used in BaseSetAssoc (it inherits BaseTags class), doesn't inherit any class. Because, Cacheset is just a data structure, which doesn't model clock latency. The latency to access Cacheset (it sounds wired actually, because latency is for tag access and Cacheset is subset of tag model) is modeled in BaseSetAssoc class, which inherits ClockedObject. Haeyoon Cho 2017-10-10 13:17 GMT+09:00 Muhammad Avais <avais.suh...@gmail.com>: > Hi, > > I want to create small table (256 entries) in gem5 that is accessed on > each cache miss and follows LRU replacement policy. > > Can someone guide me how to do it? (Which classes i should use or inherit) > > Many Thanks > > Avais > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users