All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] general shaping rules
@ 2005-10-15 18:29 Jorge Sanchez
  2005-10-15 19:17 ` Jose Luis Domingo Lopez
  0 siblings, 1 reply; 2+ messages in thread
From: Jorge Sanchez @ 2005-10-15 18:29 UTC (permalink / raw)
  To: lartc

Hi,
i dont fully understand this sentence, could someone be so kind to 
expleain me it?

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.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [LARTC] general shaping rules
  2005-10-15 18:29 [LARTC] general shaping rules Jorge Sanchez
@ 2005-10-15 19:17 ` Jose Luis Domingo Lopez
  0 siblings, 0 replies; 2+ messages in thread
From: Jose Luis Domingo Lopez @ 2005-10-15 19:17 UTC (permalink / raw)
  To: lartc


[-- Attachment #1.1: Type: text/plain, Size: 1646 bytes --]

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 #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-10-15 19:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-15 18:29 [LARTC] general shaping rules Jorge Sanchez
2005-10-15 19:17 ` Jose Luis Domingo Lopez

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.