summaryrefslogtreecommitdiff
path: root/src/mem/ruby/network/MessageBuffer.hh
diff options
context:
space:
mode:
authorNilay Vaish <nilay@cs.wisc.edu>2015-04-29 22:35:22 -0500
committerNilay Vaish <nilay@cs.wisc.edu>2015-04-29 22:35:22 -0500
commit43335495754abac71377bbd6df0c668b60b22822 (patch)
tree62ca271baac3fafb041bf24acaaeef14f6ab8e97 /src/mem/ruby/network/MessageBuffer.hh
parent0dbd696aaef47205c1430b53841423c7d25455ed (diff)
downloadgem5-43335495754abac71377bbd6df0c668b60b22822.tar.xz
cpu: o3: replace issueLatency with bool pipelined
Currently, each op class has a parameter issueLat that denotes the cycles after which another op of the same class can be issued. As of now, this latency can either be one cycle (fully pipelined) or same as execution latency of the op (not at all pipelined). The fact that issueLat is a parameter of type Cycles makes one believe that it can be set to any value. To avoid the confusion, the parameter is being renamed as 'pipelined' with type boolean. If set to true, the op would execute in a fully pipelined fashion. Otherwise, it would execute in an unpipelined fashion.
Diffstat (limited to 'src/mem/ruby/network/MessageBuffer.hh')
0 files changed, 0 insertions, 0 deletions