I could not pass tagged traffic through the l2fwd program running inside a
CentOS VM. The l2fwd program reported sending out all the packets received
from one port to the other port. But the outside Spirent tester could not
receive a packet at all. I am wondering maybe the tagged packets are
droppe
Hello MIchael,
I suggest you to check average burst sizes on receive queues. Looks like
I stumbled upon a similar issue several times. If you are calling
rte_eth_rx_burst too frequently, NIC begins losing packets no matter how
many CPU horse power you have (more you have, more it loses, actuall
Does your NIC connect directly to your Socket?
If not, the packet might go through QPI, which will cause additional
latency.
Check your motherboard.
Wang, Shawn
On 1/22/14, 6:52 AM, "Dmitry Vyal" wrote:
>Hello MIchael,
>
>I suggest you to check average burst sizes on receive queues. Looks li
Hi Michael,
> What can I do to trace down this problem?
May I suggest that you try to be more selective in the core masks on the
command line. The test app may choose some cores from "other" CPU sockets.
Only enable cores of the one socket to which the NIC is attached.
> It seems very similar t
Hi,
Currently we are using run-to-complete model with multiple workers in
our project. there is also a KNI running with a fixed ip address. However,
a packet with a destination IP of the KNI may go to any worker that owns a
rxq of the physical NIC(without Flow Director). So all the workers have
5 matches
Mail list logo
