Re: Introducing if_output()

2015-05-13 Thread Philip Guenther
On Tue, May 12, 2015 at 5:45 AM, Martin Pieuchot wrote: >> I got one positive test report involving carp, gif, vether & bridge but >> nothing else. > > Rafael Zalamena pointed a double if_opackets increment in vlan, diff > below fixes that. This version also left the net80211 bits out because > w

Re: Introducing if_output()

2015-05-12 Thread Martin Pieuchot
On 12/05/15(Tue) 12:15, Martin Pieuchot wrote: > On 07/05/15(Thu) 11:50, Martin Pieuchot wrote: > > This diff is a first step towards removing all pseudo-driver #ifdef > > in ether_output(). As for ether_input() the goal of this work is to > > provide an elegant design to make it easier to turn ps

Re: Introducing if_output()

2015-05-12 Thread Martin Pieuchot
On 07/05/15(Thu) 11:50, Martin Pieuchot wrote: > This diff is a first step towards removing all pseudo-driver #ifdef > in ether_output(). As for ether_input() the goal of this work is to > provide an elegant design to make it easier to turn pseudo-drivers > MP-safe. > > So instead of including so

Introducing if_output()

2015-05-07 Thread Martin Pieuchot
This diff is a first step towards removing all pseudo-driver #ifdef in ether_output(). As for ether_input() the goal of this work is to provide an elegant design to make it easier to turn pseudo-drivers MP-safe. So instead of including some bridge(4), vlan(4) and carp(4) specific code in ether_ou