On 14/11/14 10:03, Morten Jagd Christensen wrote: > Hi Marc, > > It turns out that I could successively comment out the setting of cpu flags > in mk/rte.cpuflags, > rebuild dpdk and my application, and then run valgrid until no further error > messages occured. > > But it turns out to be too slow for practical purposes :-(
(Please, do not drop the list, it might be helpful to others) Ok, I am not sure if this can cause you any problem. Perhaps someone in the community can advise you here. valgrind should only be used to do functional testing, not for performance. But for doing so I strongly suggest to do this: > [snip] > One recommendation: once it is working, unless you have a very > powerful machine (which my VM isn't) I recommend to add some usleeps > in the main I/O loops when running valgrind, otherwise due to the > heavyweight emulation valgrind does it slows down application > execution considerably. Let's see if it helps. Marc Best Marc
