From fc1d2d967924f9e8116d156550786ed0b527d1e3 Mon Sep 17 00:00:00 2001 From: Tushar Krishna Date: Sat, 21 May 2011 00:40:57 -0400 Subject: 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. --- src/mem/ruby/network/garnet/fixed-pipeline/OutputUnit_d.cc | 1 - 1 file changed, 1 deletion(-) (limited to 'src/mem/ruby/network/garnet/fixed-pipeline/OutputUnit_d.cc') diff --git a/src/mem/ruby/network/garnet/fixed-pipeline/OutputUnit_d.cc b/src/mem/ruby/network/garnet/fixed-pipeline/OutputUnit_d.cc index 988e5d37a..c2fba3ffd 100644 --- a/src/mem/ruby/network/garnet/fixed-pipeline/OutputUnit_d.cc +++ b/src/mem/ruby/network/garnet/fixed-pipeline/OutputUnit_d.cc @@ -102,7 +102,6 @@ void OutputUnit_d::update_vc(int vc, int in_port, int in_vc) { m_outvc_state[vc]->setState(ACTIVE_, g_eventQueue_ptr->getTime() + 1); - m_outvc_state[vc]->set_credit_count(); m_outvc_state[vc]->set_inport(in_port); m_outvc_state[vc]->set_invc(in_vc); m_router->update_incredit(in_port, in_vc, -- cgit v1.2.3