[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080320194937.GA3193@ami.dom.local>
Date: Thu, 20 Mar 2008 20:49:37 +0100
From: Jarek Poplawski <jarkao2@...il.com>
To: Djalel Chefrour <cdjalel@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: Does HTB traffic shaping happen on leaf classes only or could
it happen at root qdisc
On Thu, Mar 20, 2008 at 03:07:05PM +0100, Djalel Chefrour wrote:
...
> > > # tc -s -d class show dev ppp0
> > > class htb 1:110 parent 1:10 leaf 110: prio 0 quantum 1375 rate 110Kbit
> > > ceil 220Kbit burst 323b/2 mpu 0b overhead 18b atm cburst 392b/2 mpu 0b
> >
> > Are these default quantum, burst and cburst parameters?
> >
> Yes they are. I forget to mention that I am also using tc-atm pacth with:
> atm overhead 18 nohys mtu 256, for 1:10
> atm overhead 18 nohys, for 1:20
I don't know this patch, but if it's about some fine graining, maybe
it's better to get it working with a vanilla version first. Anyway,
you wondered why 1:110 could be treated unfair vs. 1:20, so I wonder,
why it has worse parameters than 1:20 (also by default?).
> > > overhead 18b atm level 0
> > > Sent 3888361 bytes 19368 pkts (dropped 0, overlimits 0)
> > > rate 7160bit 35pps
> > > lended: 19348 borrowed: 20 giants: 50
> >
> > giants (>mtu) means something goes out of band here.
> >
> Hmmm, that could be explained with mtu set to 256
I'm not sure where you set this mtu, or if it's changed by this atm
patch, but HTB gets packets bigger than it can rate, so you probably
should set HTB's mtu parameter higher, until these giants are not
reported.
> > No, HTB root qdisc doesn't even have parameter for shaping.
> > BTW, did you read this fine manual?:
> > http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm
> >
>
> Yes, thats what I read too, but the output shows 0 overlimits for all
> nodes but root !!!
> So how to interpret this?
I'm not sure if HTB uses these overlimits for classes yet. But, I
don't see why should you care about this so much: it only tells
generally how much classes delay sending - not about overloading.
If I don't miss something in your problem, you should check first
if 1:110 class works OK without any traffic in 1:20, and if so, than
limit 1:20 parameters until it doesn't affect 1:110 anymore.
Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists