Re: Another attempt to bypass ifqs on interfaces

2019-01-01 Thread David Gwynne
On Sun, Dec 23, 2018 at 01:53:48PM -0200, Martin Pieuchot wrote: > On 20/12/18(Thu) 11:35, David Gwynne wrote: > > My last attempt in "let etherip(4) output directly to the ip stack" > > didn't go so well. This one at least doesn't break bridge(4) on > > Ethernet. > > It breaks it on mpw(4). I

Re: Another attempt to bypass ifqs on interfaces

2018-12-23 Thread Martin Pieuchot
On 20/12/18(Thu) 11:35, David Gwynne wrote: > My last attempt in "let etherip(4) output directly to the ip stack" > didn't go so well. This one at least doesn't break bridge(4) on > Ethernet. It breaks it on mpw(4). > This diff effectively turns if_enqueue into a per interface function >

Another attempt to bypass ifqs on interfaces

2018-12-19 Thread David Gwynne
My last attempt in "let etherip(4) output directly to the ip stack" didn't go so well. This one at least doesn't break bridge(4) on Ethernet. This diff effectively turns if_enqueue into a per interface function pointer. Things still call if_enqueue(), which does some pf stuff, and then it calls