On Tue, Dec 11, 2012 at 1:09 AM, Jack Vogel <jfvo...@gmail.com> wrote: > On Mon, Dec 10, 2012 at 11:58 PM, Gleb Smirnoff <gleb...@freebsd.org> wrote: > >> On Mon, Dec 10, 2012 at 03:31:19PM -0800, Jack Vogel wrote: >> J> UH, maybe asking the owner of the driver would help :) >> J> >> J> ... and no, I've never been aware of doing anything to stop supporting >> altq >> J> so you wouldn't see any commits. If there's something in the altq code >> or >> J> support (which I have nothing to do with) that caused this no-one >> informed >> J> me. >> >> Switching from if_start to if_transmit effectively disables ALTQ support. >> >> AFAIR, there is some magic implemented in other drivers that makes them >> modern (that means using if_transmit), but still capable to switch to >> queueing >> mode if SIOCADDALTQ was casted upon them. >> >> > Oh, hmmm, I'll look into the matter after my vacation. > > Jack
Has there been any progress on resolving this issue? I recently ran into this problem upgrading my servers from 8.3 to 9.1-RELEASE and am wondering what the latest recommendation is. I've used ALTQ and igb successfully for years and it is unfortunate it no longer works. Appreciate any advice. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
