On 8.1.2018. 2:13, David Gwynne wrote: > this is tx mitigation again, ie, defer calling an interfaces start > routine until at least 4 packets are queued, or a task fires. > > the task firing is a problem for things like gif or vxlan that encap > a packet in ip and send it through the ip stack again. the ip stack > expects NET_RLOCK to be held. that is implicitly true when sending > out of the network stack, but not when the bundle task fires. > > this has the bundle tasks take the network read lock on behalf of > the start routines, like the stack does. this avoids having to patch > every driver to cope with this. > > tests?
with this diff i'm having same performance boost as with older versions.. from 1.1Mpps to 1.3Mpps on box with 12 x Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz, 2400.00 MHz