On Sun, Nov 15, 2015 at 07:58:27PM -0300, Ariel Rodriguez wrote: > Hi Bruce, im going to list the results after the test?s. > > I will start with the second hint you proposed: > > 2) I upgrade our custom dpdk application with the latest dpdk code (2.1.0) > and the issue still there. > > 1) I test the load balancer app with the latest dpdk code (2.1.0) with the nic > 82599ES 10-Gigabit SFI/SFP+ with tapped traffic and the results are: > > a) Work fine after 6 hours of running. (For timing issues i cant wait > longer but the issue always happend before 5 hours of running so i supposed > we are fine in this test). > > b) I made a change to load balancer code to behave as our dpdk > application in the workers code. This change is just for giving the > workers code enough load (load in terms of core frecuency) that made the rx > core drop several packet because ring between workers and rx core is full. > (Our application drop several packets because the workers code are not fast > enough). > > In the last test, the segmentation fault arise , just in the same > line that i previously report. > What is the workload you are putting into the worker core? Can you provide a diff for the load balancer app that reproduces this issue, since from your description the problem may be in the extra code added in.
/Bruce
