Tushar Krishna fc1d2d9679 garnet: use vnet_type from protocol to decide buffer depths ... The virtual channels within "response" vnets are made buffers_per_data_vc deep (default=4), while virtual channels within other vnets are made buffers_per_ctrl_vc deep (default = 1). This is for accurate power estimates.		2011-05-21 00:40:57 -04:00
..
fixed-pipeline	garnet: use vnet_type from protocol to decide buffer depths	2011-05-21 00:40:57 -04:00
flexible-pipeline	slicc: added vnet_type field to identify response vnets from others	2011-05-18 03:06:07 -04:00
BaseGarnetNetwork.cc	garnet: rename and rearrange config parameters.	2011-05-18 03:04:14 -04:00
BaseGarnetNetwork.hh	garnet: rename and rearrange config parameters.	2011-05-18 03:04:14 -04:00
BaseGarnetNetwork.py	garnet: rename and rearrange config parameters.	2011-05-18 03:04:14 -04:00
NetworkHeader.hh	garnet: use vnet_type from protocol to decide buffer depths	2011-05-21 00:40:57 -04:00
SConscript	ruby: Converted Garnet to M5 configuration	2010-01-29 20:29:32 -08:00