Fwiw, not VPP-specific, but just based on a previous experience: when observing
the drops at anomalously low PPS levels too early in the processing of the
packet, I would check the interframe gap on the traffic generator set for that
test to ensure you are not generating dense bursts of traffic.
Sorry, I take back my word on “most likely it’s not related to VPP itself”.
Since VPP fetch vectors from the NIC’s RX ring, it’d be possible that the NIC
run out of space before VPP could poll enough vectors out.
But it’s still strange in this case, as 8 vectors/Call means that VPP is not
working
[mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of ??
Sent: Friday, July 14, 2017 11:12 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Why VPP drop packets while the average vectors per node is
still low
Hi, guys
Last week I did some performance test on VPP with Spirent testcenter. Below I
give
Hi, guys
Last week I did some performance test on VPP with Spirent testcenter. Below I
give two groups of running data in two different situation using the 'show run'
command . Inboth situationVPP drop packets ( from the 'rx-miss' output in 'show
int' command). In my opinion, when VPP begins to
Hi Xiang,
My best guess is that the rx-miss field comes from DPDK, quote from their
datasheet:
Packets are missed when the receive FIFO has insufficient space to
store the incoming packet. This might be caused due to insufficient
buffers allocated, or because there is insufficient bandwidth o
Hi, guys
Last week I did some performance test on VPP with Spirent testcenter. Below I
give two groups of running data in two different situation using the 'show run'
command . Inboth situationVPP drop packets ( from the 'rx-miss' output in 'show
int' command). In my opinion, when VPP begins to
