DPDK polls. We can't just spin, but we also can't just sleep arbitrarily.
We need to figure out a way of delaying when it makes sense, and not delaying when there are still packets to be processed.
Ideally, we'd have this delay ramp up/down with some sort of history.
The challenge right now is that the "scheduler" is unaware of the fact that we are polling. It also does not understand how many packets have been received, which it needs to in order to be able to ramp up/down
DPDK polls. We can't just spin, but we also can't just sleep arbitrarily.
We need to figure out a way of delaying when it makes sense, and not delaying when there are still packets to be processed.
Ideally, we'd have this delay ramp up/down with some sort of history.
The challenge right now is that the "scheduler" is unaware of the fact that we are polling. It also does not understand how many packets have been received, which it needs to in order to be able to ramp up/down