+++ This bug was initially created as a clone of Bug #1762725 +++ During TX in netdev-dpdk in OVS, there is a pkt drop counter but there are different reasons why that counter may be incremented: - Drops due to egress policing - Drops due to MTU exceeded - Drops reported from the DPDK PMD Tx function There is a proposed patch upstream [1] that adds the above as more fine grained custom stats for dpdk and vhost ports. This Bz is to help with upstreaming of that patch and possible backport to downstream. [1] https://mail.openvswitch.org/pipermail/ovs-dev/2019-September/362872.html
The RFE has been verified via the validation notes in comment #1: [root@localhost jhsiao]# cat testpmd.sh testpmd -l 0,1,2,3,4 -w 0000:00:03.0 -w 0000:00:09.0 --socket-mem 4096 -- -i --nb-cores=4 --rxq=2 --txq=2 --rxd=10 --txd=1024 [root@localhost jhsiao]# [root@netqe7 jhsiao]# !51 ovs-vsctl get Interface vhost0 statistics:tx_dropped 13027572 [root@netqe7 jhsiao]# ovs-vsctl get Interface vhost0 statistics:tx_dropped 13027572 [root@netqe7 jhsiao]# ovs-vsctl get Interface vhost0 statistics:tx_dropped 19486811 [root@netqe7 jhsiao]# !52 ovs-vsctl get Interface vhost0 statistics:ovs_tx_failure_drops 26114241 [root@netqe7 jhsiao]# ovs-vsctl get Interface vhost0 statistics:ovs_tx_failure_drops 32858448 [root@netqe7 jhsiao]# ovs-vsctl get Interface vhost0 statistics:ovs_tx_failure_drops 32858448 [root@netqe7 jhsiao]# !55 ovs-vsctl set Interface dpdk0 ingress_policing_rate=368000 [root@netqe7 jhsiao]# !56 ovs-vsctl get Interface dpdk0 statistics:ovs_rx_qos_drops 24513625 [root@netqe7 jhsiao]# ovs-vsctl get Interface dpdk0 statistics:ovs_rx_qos_drops 39017784 [root@netqe7 jhsiao]# ovs-vsctl get Interface dpdk0 statistics:ovs_rx_qos_drops 39017784 [root@netqe7 jhsiao]# ovs-vsctl get Interface dpdk0 statistics:ovs_rx_qos_drops 58420721 [root@netqe7 jhsiao]# [root@netqe7 jhsiao]# rpm -q openvswitch2.11 openvswitch2.11-2.11.0-47.el8fdp.x86_64 [root@netqe7 jhsiao]# uname -r 4.18.0-147.el8.x86_64 [root@netqe7 jhsiao]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0743