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, 9 deletions

diff --git a/src/mem/ruby/network/garnet/fixed-pipeline/OutVcState_d.hh b/src/mem/ruby/network/garnet/fixed-pipeline/OutVcState_d.hh
index 5b1328fcf..237f54340 100644
--- a/src/mem/ruby/network/garnet/fixed-pipeline/OutVcState_d.hh
+++ b/src/mem/ruby/network/garnet/fixed-pipeline/OutVcState_d.hh
@@ -42,15 +42,6 @@ class OutVcState_d
     int get_inport()                { return m_in_port; }
     int get_invc()                  { return m_in_vc; }
     int get_credit_count()          { return m_credit_count; }
-    void
-    set_credit_count()
-    {
-        // only need to initialize credit count for data VCs
-        // constructor sets this to BuffersPerCtrlVC by default
-
-        if (m_network_ptr->get_vnet_type(m_id) == DATA_VNET_)
-            m_credit_count = m_network_ptr->getBuffersPerDataVC();
-    }
 
     void set_inport(int port)       { m_in_port = port; }
     void set_invc(int vc)           { m_in_vc = vc; }