em(4) + ALTQ broken

[Jack Vogel]

So apparently this thing needs no special knowledge in the driver, yet
something in
the new code breaks it, can someone explain tersely how the altq app
actually
"pokes" or "hooks up" to the driver? I am not clear about that and I suspect
if I was
this would all be clearer.

Jack


On Tue, Feb 2, 2010 at 9:37 AM, Pyun YongHyeon <pyunyh at gmail.com> wrote:

> On Tue, Feb 02, 2010 at 09:30:52AM -0800, Nick Rogers wrote:
> > > I guess the problem comes from multi-queue support. The drbr
> > > interface is implemented with inline function so em(4)/igb(4) may
> > > have to define ALTQ to the header. I have not tested the patch(no
> > > time at this moment) but would you give it try?
> > >
> > > I tried the patch and it did not work.
>
> You rebuilt kernel, right? Rebuilding kernel module has no effect.
>