The vnet_type field is used by the garnet on-chip network to decide whether the message only carries control (= request) information or data (i.e. the cache line) (= response), and size the number of buffers required within each VC appropriately (e.g. vnets carrying control have 1-flit buffers, and vnets carrying data have 4-5 flit buffers).
If your new MessageBuffer is going to carry data, set the vnet_type as "response", else you can name it anything, doesn't matter. - Tushar On Mar 13, 2013, at 5:40 PM, zhengchl wrote: > Hi, > > I want to add a MessageBuffer between L1 and L2 cache which transports > 'MemoryMsg' message. I find many MessageBuffer declaration like: > > MessageBuffer requestFromL1Cache, network="To", virtual_network="0", > ordered="false", vnet_type="request"; > MessageBuffer responseFromL1Cache, network="To", virtual_network="1", > ordered="false", vnet_type="response"; > I have a questions about 'vnet_type'field. Does 'vnet_type' field declare > message type transported? For example 'reqeustFromL1Cache' only transport > RequestMsg because its vnet_type field is set to 'request'. > > So how to declare a MessageBuffer transporting MemoryMsg? > > Thank you! > -- > Chuanlei Zheng > > Department of Computer Science and Technology > Nanjing University > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
