200 cycles or less

Posted Jan 15, 2020 19:00 UTC (Wed) by hkario (subscriber, #94864)
In reply to: 200 cycles or less by ale2018
Parent article: Accelerating netfilter with hardware offload, part 1

remember that those 200 cycles are for processing header only, the length of payload doesn't matter (here it's averaged over typical frame sizes)

it's just like navigation: handling a 20t truck in principle is not different than a 3.5t truck

200 cycles or less

Posted Jan 15, 2020 22:45 UTC (Wed) by leromarinvit (subscriber, #56850) [Link]

I think the 200 cycles number is just meant as a reminder that it's "not much" time per packet. The linked article seems to be talking about a single 3 GHz CPU. Obviously the available cycles vary with average packet length and CPU clock, and processing can be split over multiple cores. That is, of course, no reason not to try making the best use of the available cycles, since latency will suffer if you just rely on parallellism to stem the load.

200 cycles or less

Posted Jan 17, 2020 6:55 UTC (Fri) by ghane (guest, #1805) [Link]

Thanks, I will apply for my licence today :-)