Date: Thu, 21 Aug 2014 15:37:09 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Peter Lai <cowbert@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: How do I ALTQ hostap interface? Message-ID: <CAJ-VmokqguvHtjw3VAAhEse8Ankwnqv7PRN1aHkD6SbCxufsRw@mail.gmail.com> In-Reply-To: <CACPAC31nxgpY1zscqn4=8QG56=bBpngte3dODZ2r1DiLxpwhbg@mail.gmail.com> References: <CACPAC30jw0EB5SGBFf0C%2Brg9Hhg8W4z0dCsvZQg2m768GcvyAA@mail.gmail.com> <CAJ-Vmom7mimn838vkhZ9dOMhxFSD66SMKamea4qjtWSDswgQkw@mail.gmail.com> <CACPAC324bq=dDU5Pdnd2-mQD14_M2qLtAXa8fLVNjG=pAEGuCg@mail.gmail.com> <CAJ-VmomO=fCLVM69YLq=CH7wV0VcHL%2BUshi-s=AiVp_o1XkKUA@mail.gmail.com> <CACPAC31nxgpY1zscqn4=8QG56=bBpngte3dODZ2r1DiLxpwhbg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 August 2014 14:13, Peter Lai <cowbert@gmail.com> wrote: > Looking on the freebsd-net list it seems like a "we don't know how to > hack altq to work with multiqueues" problem, but supposedly it's been > solved with em(4) (since it works fine with altq) , (but not > necessarily with igb)? It's a solvable problem. It's just not solvable with the kinds of hacks that stuck ALTQ in there the way it is in the first place. For em, igb, etc they solved it by having a legacy "hey implement the old network transmit interface" thing stick around. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokqguvHtjw3VAAhEse8Ankwnqv7PRN1aHkD6SbCxufsRw>