Re: bridge(4) output w/o KERNEL_LOCK()

2019-04-23 Thread Martin Pieuchot
On 21/04/19(Sun) 16:45, Martin Pieuchot wrote: > Diff below removes the KERNEL_LOCK() from bridge(4)'s output fast-path. > > To do so, it redefines the ifp <-> bridge relationship. Currently every > interface in a bridge(4) contains a pointer to that bridge's port. This > relationship is

Re: bridge(4) output w/o KERNEL_LOCK()

2019-04-23 Thread David Gwynne
> On 22 Apr 2019, at 5:45 am, Martin Pieuchot wrote: > > Diff below removes the KERNEL_LOCK() from bridge(4)'s output fast-path. > > To do so, it redefines the ifp <-> bridge relationship. Currently every > interface in a bridge(4) contains a pointer to that bridge's port. This >

Re: bridge(4) output w/o KERNEL_LOCK()

2019-04-21 Thread Sigi Rudzio
Hi, tried it on a router with three bridges (etherip/vether over IPSec and vxlan/vlan) and it works, if you want dmesg/ifconfig output I'll send it to you. Regards, S. Rudzio Am So., 21. Apr. 2019 um 21:47 Uhr schrieb Martin Pieuchot : > > Diff below removes the KERNEL_LOCK() from bridge(4)'s

bridge(4) output w/o KERNEL_LOCK()

2019-04-21 Thread Martin Pieuchot
Diff below removes the KERNEL_LOCK() from bridge(4)'s output fast-path. To do so, it redefines the ifp <-> bridge relationship. Currently every interface in a bridge(4) contains a pointer to that bridge's port. This relationship is guaranteed to be valid as long as the KERNEL_LOCK() is held.