Hello We're currently testing an application based on L2FWD example.
1. The application is located on VM which has 2 VFs from 2 different PFs 2. One core simply polls both RX queues from VFs, makes simple message processing and forwards the messages to appropriate TX queue of different VF (so there is no multiple access to the same port) 3. However sometimes when message is being processed, it results with failure and code needs to send back Failure notification to the port from which the message was received. The issue is that sometimes we see that packets are not being sent back (even though rte_eth_tx_burst() is succesfull... checked with tcpdump on peer ). Instead the core receives next packets and tries to send Failure Indications again until it runs out of memory in mempool. One thing to notice is that our app priority is latency over throughput so it always invokes rte_eth_tx_burst with only 1 packet to send. (we are suspecting this might be an issue here) Has anyone encountered such issue before.? Host Setup: DL380p Gen8 Server Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz Ubuntu 14.04: 3.13.0-24-generic Intel 82599 VM Setup: Ubuntu 14.04: 3.13.0-24-generic 2 VFs (each one from different PF)
