On Fri, 2011-12-23 at 12:35 -0500, John A. Sullivan III wrote:

On Fri, 2011-12-23 at 12:33 -0500, John A. Sullivan III wrote:

quoted

On Fri, 2011-12-23 at 18:17 +0100, Eric Dumazet wrote:

quoted

Le vendredi 23 décembre 2011 à 18:06 +0100, Eric Dumazet a écrit :

quoted

Maybe I was not clear :

netem currently uses a fifo queue, you cant change this, without
patching kernel.

An other way would be to patch sch_tbf, adding delay, if its all you
want to do.

(Or adding delay capability to ifb)

<grin> that's just a little outside by skill set ;) - John

<snip>
And I should mention seriously, that we are viewing our learning curve
as something we will use in production so we'd like to accomplish our
goals using stock distribution code.  Thanks, though - John

<snip>
Should I guess that, from the flood of subsequent emails about patching
netem that it is not currently possible to do netem and hfsc/sfq on
ingress traffic using the currently available tools? 

It's definitely netem on the ingress.  When I run it on egress and
disable it on ingress, I do not have the problem.  But, I see no what of
getting the netem traffic into or out of SFQ.  Thanks - John