vmxnet3: interface rx counter not increment correctly 30/21730/1
authorSteven Luong <sluong@cisco.com>
Fri, 30 Aug 2019 18:22:13 +0000 (11:22 -0700)
committersteven luong <sluong@cisco.com>
Tue, 3 Sep 2019 18:23:06 +0000 (18:23 +0000)
vlib_increment_combined_counter takes sw_if_index, not hw_if_index. Using
hw_if_index may work as long as there is no subinterface created to cause
hw_if_index and sw_if_index to differ.

Type: fix
Ticket: VPP-1760

Signed-off-by: Steven Luong <sluong@cisco.com>
Change-Id: If50412dc1e84c4f1f5b977b58d0e1aeb5ab8ebe6
(cherry picked from commit ddf625d6035d9e472bcb1a2b0197f6fd30278583)

src/plugins/vmxnet3/input.c

index 6d30f19..cb456b1 100644 (file)
@@ -437,7 +437,7 @@ vmxnet3_device_input_inline (vlib_main_t * vm, vlib_node_runtime_t * node,
       vlib_increment_combined_counter
        (vnm->interface_main.combined_sw_if_counters +
         VNET_INTERFACE_COUNTER_RX, thread_index,
-        vd->hw_if_index, n_rx_packets, n_rx_bytes);
+        vd->sw_if_index, n_rx_packets, n_rx_bytes);
     }
 
   error = vmxnet3_rxq_refill_ring0 (vm, vd, rxq);