Re: let etherip(4) output directly to the ip stack

2018-12-13 Thread David Gwynne
> On 13 Dec 2018, at 00:03, Martin Pieuchot wrote: > > On 12/12/18(Wed) 12:03, David Gwynne wrote: >> with the previous if_ethersubr.c diff, this allows etherip(4) to output >> directly to the network stack. > > What do you mean with "directly"? > > To my understanding ip{,6}_etherip_output(

Re: let etherip(4) output directly to the ip stack

2018-12-12 Thread Martin Pieuchot
On 12/12/18(Wed) 12:03, David Gwynne wrote: > with the previous if_ethersubr.c diff, this allows etherip(4) to output > directly to the network stack. What do you mean with "directly"? To my understanding ip{,6}_etherip_output() call ip{,6}_send() to enqueue packets. > direct output relies on t

let etherip(4) output directly to the ip stack

2018-12-11 Thread David Gwynne
with the previous if_ethersubr.c diff, this allows etherip(4) to output directly to the network stack. direct output relies on the interface using priq, since hfsc uses the ifq machinery to work. priq implies you dont want to delay packets, so it lets etherip push the packet straight through. i d