Dequeuing is done in bulk (that's what shows as CPU consuming, as
well). Enqueuing is not due to some constraint we have.
It seemed likely that the dequeue function is falsely blamed for
taking up CPU, but in my tests there are constant incoming packets so
I don't see when it will poll and receive
I have an app which captures packets on a single core and then passes
to multiple workers on different lcores, using the ring queues.
While I manage to capture packets at 10Gbps, when I send it to the
processing lcores there is substantial packet loss. At first I figured
it's the processing I do o
On Mon, 6 Apr 2015 15:18:21 +0300
Dor Green wrote:
> I have an app which captures packets on a single core and then passes
> to multiple workers on different lcores, using the ring queues.
>
> While I manage to capture packets at 10Gbps, when I send it to the
> processing lcores there is substan
3 matches
Mail list logo
