[dpdk-users] Lcore impact

[Shawn Lewis]

Lots of things...

One just because you have a process running on an lcore, does not mean
thats all that runs on it.  Unless you have told the kernel at boot to NOT
use those specific cores, those cores will be used for many things OS
related.

IRQBlance
System OS operations.
Other Applications.

So by doing file i/o you are generating interrupts, where those interrupts
get serviced is up to IRQBalancer.  So could be any one of your cores.



On Thu, Apr 14, 2016 at 12:31 PM, Alexander Kiselev <kiselev99 at gmail.com>
wrote:

> Could someone give me any hints about what could cause permormance issues
> in a situation where one lcore doing a lot of linux system calls
> (read/write on socket) slow down the other lcore doing packet forwarding?
> In my test the forwarding lcore doesn't share any memory structures with
> the other lcore that sends test data to socket. Both lcores pins to
> different processors cores. So therotically they shouldn't have any impact
> on each other but they do, once one lcore starts sending data to socket the
> other lcore starts dropping packets. Why?
>