On 7/25/23 07:06, Pureewat Kaewpoi via discuss wrote:
Hi Community
According to ovs-dpctl documentation.
The "lookups" row displays three stats related to flow lookup triggered by
processing incoming packets in the datapath.
"hit" displays number of packets matches existing flows.
"missed" displays the number of packets not matching any existing flow and
require user space processing.
"lost" displays number of packets destined for user space process but
subsequently dropped before reaching userspace.
The sum of "hit" and "miss" equals to the total number of packets datapath
processed.
I just curious “lost” statistics. Which scenario or case will packet dropped
before reaching userspace ?
A relatively common situation that may cause this is when ovs-vswitchd is busy
(maybe given very little cpu time) and it's not able to dequeue packets from the
netlink sockets fast enough. In such situation, the netlink socket buffer
overflows and an upcall is dropped. ovs-vswitchd will also log and increase a
coverage counter (netlink_overflow) to indicate this problem.
Thanks.
--
Adrián Moreno
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
