[3411] in linux-net channel archive
Re: shaper or whatever
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Sat Jun 22 17:18:43 1996
Date: Sat, 22 Jun 1996 16:25:11 -0400
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Eric Schenk" <schenk@cs.toronto.edu>
Cc: dennis@etinc.com, linux-net@vger.rutgers.edu
In-Reply-To: Eric Schenk's message of Sat, 22 Jun 1996 14:42:37 -0400,
<96Jun22.144239edt.15395@dvp.cs.toronto.edu>
Date: Sat, 22 Jun 1996 14:42:37 -0400
From: "Eric Schenk" <schenk@cs.toronto.edu>
The traffic shaper would have to drop any packet that crosses the
box that exceeds the bandwidth assigned to the connection.
The contents of the packet (ACK, data whatever) are irrelevant to
the decision to drop. The only knowledge the shaper needs how to
determine if the packet exceeds the bandwidth assigned to the connection.
The connection a packet belongs to would have to be determined from
the addresses in the headers. Note that this approach should work
with a router just as well as a box that is acting as an end point.
There is some information overhead that would not be present on a
standard router. You need to track every active pair of end points
that are sending packets through your router.
You don't necessarily have to track every active pair of end points; a
lot depends on how you are trying to limit the bandwidth. For example,
may be quite sufficient to just calculate the outgoing bandwidth to a
particular destination address, and drop packets based on that. Much
depends on how your requirements are formally stated.
- Ted
