mem: Move crossbar default latencies to subclasses
This patch introduces a few subclasses to the CoherentXBar and NoncoherentXBar to distinguish the different uses in the system. We use the crossbar in a wide range of places: interfacing cores to the L2, as a system interconnect, connecting I/O and peripherals, etc. Needless to say, these crossbars have very different performance, and the clock frequency alone is not enough to distinguish these scenarios. Instead of trying to capture every possible case, this patch introduces dedicated subclasses for the three primary use-cases: L2XBar, SystemXBar and IOXbar. More can be added if needed, and the defaults can be overridden.
This commit is contained in:
@@ -243,7 +243,7 @@ def make_cache_level(ncaches, prototypes, level, next_cache):
|
||||
if level != 0:
|
||||
# Create a crossbar and add it to the subsystem, note that
|
||||
# we do this even with a single element on this level
|
||||
xbar = CoherentXBar(width = 32)
|
||||
xbar = L2XBar(width = 32)
|
||||
subsys.xbar = xbar
|
||||
if next_cache:
|
||||
xbar.master = next_cache.cpu_side
|
||||
@@ -269,7 +269,7 @@ def make_cache_level(ncaches, prototypes, level, next_cache):
|
||||
|
||||
if ntesters > 1:
|
||||
# Create a crossbar and add it to the subsystem
|
||||
xbar = CoherentXBar(width = 32)
|
||||
xbar = L2XBar(width = 32)
|
||||
subsys.xbar = xbar
|
||||
xbar.master = next_cache.cpu_side
|
||||
for tester, checker in zip(testers, checkers):
|
||||
|
||||
Reference in New Issue
Block a user