netdev
[Top] [All Lists]

Re: 2.6: QoS scheduling not working with IP-over-IP

To: hadi@xxxxxxxxxx
Subject: Re: 2.6: QoS scheduling not working with IP-over-IP
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Sat, 14 Feb 2004 12:49:58 -0800
Cc: kaber@xxxxxxxxx, qnex@xxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, shemminger@xxxxxxxx
In-reply-to: <1076766981.1059.16.camel@jzny.localdomain>
References: <Pine.LNX.4.44.0402101324350.810-100000@atlantis.knm.org.pl> <20040211200549.736fa8b3.davem@redhat.com> <1076561489.1032.65.camel@jzny.localdomain> <1076561998.1035.72.camel@jzny.localdomain> <1076562282.1033.76.camel@jzny.localdomain> <20040211211536.23e97997.davem@redhat.com> <1076563502.1031.85.camel@jzny.localdomain> <1076564638.1033.91.camel@jzny.localdomain> <20040211215142.7f817513.davem@redhat.com> <1076566176.1033.94.camel@jzny.localdomain> <20040211222259.776ad818.davem@redhat.com> <402D54D6.5070708@trash.net> <20040213213606.5a13cc76.davem@redhat.com> <1076762757.1060.4.camel@jzny.localdomain> <1076763997.1059.13.camel@jzny.localdomain> <1076766981.1059.16.camel@jzny.localdomain>
Sender: netdev-bounce@xxxxxxxxxxx
On 14 Feb 2004 08:56:21 -0500
jamal <hadi@xxxxxxxxxx> wrote:

> And the closest to a sane patch in 30 secs that compiles is attached
> to describe the idea.

I don't know how wise this tx_queue_len fiddling is.

With this, if user modifies tx_queue_len himself, on ifdown this configuration
change is lost if user sets it explicitly to '1'.  See?  In fact you could
call it corruption :-)

I think Alexey maybe meant something different, achieving the ends by some other
means than directly fiddling with tx_queue_len.

<Prev in Thread] Current Thread [Next in Thread>