It consumes 100% only if you busy poll (which is the default approach).
Dnia Mon, Feb 22, 2021 at 08:33:35AM -0300, Douglas Fischer napisał(a):
> But IMHO, the questions do not cover the actual reality of DPDK.
> That característic of "100% CPU" depends on several aspects, like:
> - How old are the hardware on DPDK.
> - What type of DPDK Instructions are made(Very Dynamic as Statefull CGNAT,
> ou Static ACLs?)
> - Using or not the measurements of DPDK Input/Drop/Fowarding.
> - CPU Affinity done according to the demand of traffic
> - SR-IOV (sharing resources) on DPDK.
It consumes 100% only if you busy poll (which is the default approach).
One can switch between polling and interrupts (or monitor, if supported),
or introduce halt instructions, in case of low/medium traffic volume.
--
Pawel Malachowski
@pawmal80