Review Board 2.0.15


slicc: added vnet_type field to identify response vnets from others

Review Request #686 - Created May 8, 2011 and submitted

Information
Tushar Krishna
gem5
default
Reviewers
Default
ali, beckmann, gblack, nate, stever 
slicc: added vnet_type field to identify response vnets from others

Identifying response vnets versus other vnets will allow garnet to
determine which vnets will carry data packets, and which will carry
ctrl packets, and use appropriate buffer sizes (since data packets are larger
than ctrl packets). This in turn allows the orion power model to accurately
estimate buffer power.

   

  


 


 

  

  









  
 


  

 
















 



 

  


 


  



   

   
Tushar Krishna

   
Posted  (May 9, 2011, 9:58 a.m.)


  


  


  

   
Hey Brad,
We will need some way for the total number of virtual networks declared in these protocol files to be reflected in one of the network simobject.py files, so that the config.ini file prints out the correct value for virtual networks. Currently it prints out the default value of 10 from Network.py, though the actual number of active vnets is lower.
Just to let you know while you review this patch since the change for that might be related ...

Thanks



  

   

   
    
    

   
  1. 
    
    
     
    
      
     
    
     
    This is certainly the easiest way to provide this capability and I'm fine with checking it in.  However, as I mentioned to you yesterday, this is just a short-term solution until we figure out how to move these virtual channel details into the protocol python files.  
    
    
    
   
    2.