Replies: 1 comment
-
I was able to trace down to
and despite NIC counters are increasing (confused by rx_unknown_protocol_packets), this function doesn't receive any packets from NIC.
I've captured that packets using mirror port and wireshark on different NIC - they are valid UDP packets. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a loopback setup between two ports of a dual-port Intel XXV710 25G NIC. I run the simplest tests - running the
stl/udp_1pkt_simple.py
profile from one port to another.In HW mode, everything runs perfectly, up to line rate. However, as I use EMU, it should run in software mode. Here I discovered strange behavior which also happens when enabling service mode on the port.
The problem is that the first 4087 packets are received and counted as
ipackets
, and all following packets are counted asierrors (rx_missed_errors)
. The sum ofipackets
andierrors
equals the number of packets sent.This happens only when DPDK is being used. With exactly the same interfaces in Linux mode, everything works perfectly, though the rate is limited to ~4Gbps (expected, no kernel bypass).
I tried to dig through the code and found that
rx_missed_errors
represents the I40E_GLPRT_RDPC register, which, among other things, counts packets discarded because the RX ring is full.Is it possible that in software or service mode, mbufs are not reclaimed back? This would explain why only the first packets are received.
BTW, capture also doesn't work, even with service mode enabled, 0 packets are being captured.
Beta Was this translation helpful? Give feedback.
All reactions