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.

1 files changed, 0 insertions, 6 deletions

diff --git a/src/mem/ruby/network/garnet/fixed-pipeline/NetworkInterface_d.cc b/src/mem/ruby/network/garnet/fixed-pipeline/NetworkInterface_d.cc
index 558352253..4adc8d98c 100644
--- a/src/mem/ruby/network/garnet/fixed-pipeline/NetworkInterface_d.cc
+++ b/src/mem/ruby/network/garnet/fixed-pipeline/NetworkInterface_d.cc
@@ -164,12 +164,6 @@ NetworkInterface_d::flitisizeMessage(MsgPtr msg_ptr, int vnet)
             // flitisized and an output vc is acquired
             net_msg_ptr->getInternalDestination().removeNetDest(personal_dest);
         }
-        if (num_flits > 1) { // data packet
-            // defining ctrl vnet to be 1-flit packets
-            // and data vnet to be > 1 flit packets
-            m_net_ptr->set_vnet_type(vc, DATA_VNET_);
-            m_out_vc_state[vc]->set_credit_count();
-        }
 
         for (int i = 0; i < num_flits; i++) {
             m_net_ptr->increment_injected_flits();