Regulating traffic flow in a network device
A token bucket instantiation regulate packets in a traffic flow stream based on a predetermined peak traffic flow rate. The token bucket size is nominally set to zero. An evaluation is made at a device that has received a given packet. The packet is considered conforming and is passed from the device if the token depth of the bucket is zero or greater. The token depth is decreased by the number of byes in the packet that was passed. The token depth is continuously replenished at a predetermined token rate until the predetermined bucket size is attained (the bucket is full). A received packet is deemed nonconforming if the token depth is less than zero; the non-conforming packet is not passed but is processed according to non-conforming criteria. Token bucket instantiations may be implemented in hardware, software or firmware for each traffic flow to regulate traffic to a given user.
1. A system operable to regulate packet flow in a traffic stream at a network device using a token bucket, comprising:
an interface operable to receive a packet of the traffic stream at the network device;
a packet processing module operable to process the packet received by the network device if the current token depth of the token bucket is greater than or equal to zero, even if the current token depth is less than the size of the packet, the processing module being further operable to decrease the current token depth of the token bucket based upon forwarding the packet and to increase the current token depth of the token bucket at a predetermined rate; and
wherein the token bucket is connected in series to another token bucket to further facilitate regulation of the traffic stream.
2. The system of claim 1 , wherein the packet processing module is further operable to delay processing of the packet if the current token depth of the token bucket is less than zero.
3. The system of claim 1 , wherein the packet processing module is further operable to drop the packet if the current token depth of the token bucket is less than zero.
4. The system of claim 1 , wherein the current token depth of the token bucket is decreased by the size of the packet processed.
5. The system of claim 4 , wherein the current token depth of the token bucket is operable to be a negative token depth when the size of the data packet processed is greater than the current token depth.
6. The system of claim 1 , wherein the current token depth of the token bucket is decreased by one for each byte in the packet passed.
7. The system of claim 1 , wherein the packet processing module is operable to initialize the token bucket size prior to processing a first incoming packet.
8. The system of claim 1 , wherein the packet processing module is operable to process the packet according to conforming criteria based upon the token bucket depth classifying the packet as conforming, and the packet processing module being operable to process the packet according to non-conforming criteria based upon the token bucket depth classifying the packet as non-conforming.
9. A method of regulating the flow of packets in a traffic stream at a network device using a token bucket, comprising:
receiving a packet of the stream at the network device;
processing the packet from the network device if the current token depth of the token bucket is greater than or equal to zero, even if the current token depth is less than the size of the packet;
decreasing the current token depth of the token bucket based upon processing the packet;
incrementing the current token depth of the token bucket at a predetermined rate;
wherein the token bucket is connected in series to another token bucket to further facilitate regulation of the traffic stream.
10. The method of claim 9 , further comprising delaying processing of the packet if the current token depth of the token bucket is less than zero.
11. The method of claim 9 , further comprising dropping the packet if the current token depth of the token bucket is less than zero.
12. The method of claim 9 , further comprising decreasing the current token depth of the token bucket by the size of the packet processed, if the packet is processed.
13. The method of claim 12 , wherein the current token depth of the token bucket is operable to be a negative token depth when the size of the data packet processed is greater than the current token depth.
14. The method of claim 9 , further comprising decreasing the current token depth of the token bucket by one for each byte in the packet processed.
15. The method of claim 9 , wherein the packet processing module is operable to initialize the token bucket size prior to processing a first incoming packet.
16. The method of claim 9 , further comprising:
processing the packet according to conforming criteria based upon the token bucket depth classifying the packet as conforming; and
processing the packet according to non-conforming criteria based upon the token bucket depth classifying the packet as non-conforming.
17. One or more computer-readable media having instructions stored thereon, the one or more computer readable media, when executed by a processor, being operable to cause the processor to perform operations comprising:
receiving a packet of the stream at the network device;
processing the packet from the network device if a current token depth of a token bucket is greater than or equal to zero, even if the current token depth is less than the size of the packet;
decreasing the current token depth of the token bucket based upon processing the packet;
incrementing the current token depth of the token bucket at a predetermined rate;
wherein the token bucket is connected in series to another token bucket to further facilitate regulation of the packet of the stream.