I stumbled upon this Github DPAA ethernet link. https://github.com/opencomputeproject/o ... rnet.patch
In this link i found a piece of text that looked a bit like the issues the X5000 is having with the DPAA adapter.
+ hex "Egress congestion threshold on 1G ports"
+ range 0x1000 0x10000000
+ default "0x06000000"
+ The size in bytes of the egress Congestion State notification threshold on 1G ports.
+ The 1G dTSECs can quite easily be flooded by cores doing Tx in a tight loop
(Traffic that stops)
+ (e.g. by sending UDP datagrams at "while(1) speed"),
+ and the larger the frame size, the more acute the problem.
+ So we have to find a balance between these factors:
+ - avoiding the device staying congested for a prolonged time (risking
+ the netdev watchdog to fire - see also the tx_timeout module param);
+ - affecting performance of protocols such as TCP, which otherwise
+ behave well under the congestion notification mechanism;
+ - preventing the Tx cores from tightly-looping (as if the congestion
+ threshold was too low to be effective);
+ - running out of memory if the CS threshold is set too high
. (out of bufferspace ??? )
Here a link to a video i made a while ago where you can see the traffic die.. https://drive.google.com/file/d/15I5TDQ ... 3e7S7LWlOE
Unfortunatly i dont have the skills to fix this... if its related ..