Re: general shaping rules

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday, 15 October 2005, at 20:29:20 +0200,
Jorge Sanchez wrote:

> Any router performing a shaping function should be the bottleneck on the 
> link, and should be shaping slightly below the maximum available link 
> bandwidth. This prevents queues from forming in other routers, affording 
> maximum control of packet latency/deferral to the shaping device.
> 
In the Internet, traffic flows through a number of router between source
and destination, routers you can not control. In the router closest to
your network (if using ADSL, the local telephone witching central with
DSLAM adapters) sometimes the ISP or telco applies buffering to each
subscriber. That is, to get tranfer rates up it is very easy to allocate
and indeterminate (but usually large) buffer for incoming traffic.

This way, when you download at full speed you get, well, full speed, but
the telco is getting more data at a rate greater than you can, so it
buffers traffic in excess. So, if the sending box somewhat slows down
(network congestion), your telco still has data to send and keep your line
100% full. So statistics show you get a fantastic service bandwitdh wise,
but not so good with respect to latency.

The only way to prevent those buffer to even start filling is shaping
traffic to/from your network some Kbps bellow your nominal maximun
transfer rate. You have to "be" the bottelneck to be able to control
bandwidth allocation and keep latency to a minumun.

Hope I made an understandable explanation. Greetings,

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.14-rc3-git7)

Attachment: signature.asc
Description: Digital signature

_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux