Re: Bandwidth managementFrom: Leandro Neves de Oliveira (firstname.lastname@example.org)
- Previous message: David Rubén Elfi: "Re: Packet filter choice"
- In reply to: jon schatz: "Re: Bandwidth management"
- Next in thread: Alexander Skwar: "Re: Bandwidth management"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Leandro Neves de Oliveira <email@example.com> To: jon schatz <firstname.lastname@example.org>, "Mario R. Pizzolanti" <email@example.com> Date: Thu, 6 Dec 2001 10:57:45 -0200
Traffic shapper is an old module from the linux kernel. The iproute2 features
is better than shaper module. You could use the cbq.init script to control
Em Wednesday 05 December 2001 07:18 pm, jon schatz escreveu:
> you want toe traffic shaper:
>From shaper.c source code:
* This is designed to handle lower speed links ( < 200K/second or so).
* run off a 100-150Hz base clock typically. This gives us a resolution
* 200Kbit/second of about 2Kbit or 256 bytes. Above that our timer
* resolution may start to cause much more burstiness in the traffic. We
* could avoid a lot of that by calling kick_shaper() at the end of the
* tied device transmissions. If you run above about 100K second you
* may need to tune the supposed speed rate for the right values.
* Downing the interface under the shaper before the shaper
* will render your machine defunct. Don't for now shape over
* PPP or SLIP therefore!
-- Leandro Neves - firstname.lastname@example.org "Os pequenos atos que se executam são melhores que todos aqueles grandes que se planejam." George C. Marshall (1880-1959)