Re: multiple interface input queues

2017-11-14 Thread David Gwynne
> On 14 Nov 2017, at 23:17, Martin Pieuchot wrote: > > On 14/11/17(Tue) 14:42, David Gwynne wrote: >> this replaces the single mbuf_queue and task in struct ifnet with >> a new ifiqueue structure modelled on ifqueues. > > The name is confusing, should we rename ifqueues 'ifoqueue' then? yes.

Re: multiple interface input queues

2017-11-14 Thread Martin Pieuchot
On 14/11/17(Tue) 14:42, David Gwynne wrote: > this replaces the single mbuf_queue and task in struct ifnet with > a new ifiqueue structure modelled on ifqueues. The name is confusing, should we rename ifqueues 'ifoqueue' then? > the main motivation behind this was to show mpsafe input counters.

Re: multiple interface input queues

2017-11-14 Thread David Gwynne
On Tue, Nov 14, 2017 at 02:42:30PM +1000, David Gwynne wrote: > this replaces the single mbuf_queue and task in struct ifnet with > a new ifiqueue structure modelled on ifqueues. > > the main motivation behind this was to show mpsafe input counters. > > ifiqueues, like ifqueues, allow a driver to

Re: multiple interface input queues

2017-11-13 Thread Hrvoje Popovski
On 14.11.2017. 5:42, David Gwynne wrote: > this replaces the single mbuf_queue and task in struct ifnet with > a new ifiqueue structure modelled on ifqueues. i've tested this diff with ix, myx, em and bge with down/up interfaces and everything is working fine ...

multiple interface input queues

2017-11-13 Thread David Gwynne
this replaces the single mbuf_queue and task in struct ifnet with a new ifiqueue structure modelled on ifqueues. the main motivation behind this was to show mpsafe input counters. ifiqueues, like ifqueues, allow a driver to configure multiple queueus. this in turn allows a driver with multiple rx