configs, gpu-compute: Add configurable L1 access latencies

Previously the L1 request and response latencies were not configurable
in the GPU config scripts. As a result, the simulations used the default
values from GPU.py. This commits adds support to change this value as an
input parameter. The parameters to use are "--mem-req-latency" followed
by the value and "--mem-resp-latency" followed by the value. The default
values are the same as those in GPU.py (which is 50). These new
parameters should be set instead of changing the mandatory queue latency when configuring the L1 cache.

Change-Id: I812d77758ea12530899953f308c91f4c8b05866d
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/63971
Reviewed-by: Matt Sinclair <mattdsinclair@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Maintainer: Matt Sinclair <mattdsinclair@gmail.com>
This commit is contained in:
vramadas95
2022-09-29 13:39:30 -05:00
committed by VISHNU RAMADAS
parent 4662e18981
commit a3842f877a

View File

@@ -263,6 +263,18 @@ parser.add_argument(
default=1,
help="Latency while accessing shared memory",
)
parser.add_argument(
"--mem-req-latency",
type=int,
default=50,
help="Latency for requests from the cu to ruby.",
)
parser.add_argument(
"--mem-resp-latency",
type=int,
default=50,
help="Latency for responses from ruby to the cu.",
)
parser.add_argument(
"--TLB-prefetch", type=int, help="prefetch depth for" "TLBs"
)
@@ -449,6 +461,8 @@ for i in range(n_cu):
countPages=args.countPages,
max_cu_tokens=args.max_cu_tokens,
vrf_lm_bus_latency=args.vrf_lm_bus_latency,
mem_req_latency=args.mem_req_latency,
mem_resp_latency=args.mem_resp_latency,
localDataStore=LdsState(
banks=args.numLdsBanks,
bankConflictPenalty=args.ldsBankConflictPenalty,