Buffer management: remarks

(from Steave Nadas)

The buffering for premium is separate from the buffering for assured/be. So, the buffers reserved for premium are not allocated to assured.

BE and assured share the same pool. If there is only BE traffic, (that is, no other AF streams have been created) then the BE stream can use all the assured buffering. Furthermore, if there are AF streams but the AF sources are inactive for a timeout period (30 sec) their buffers are released and made available to active streams. In order to prevent BE starvation, we allocate some buffer (by default 10%, but this may be configured) for BE; beyond that the allocation comes from the shared portion. Similarily, for control, we allocate some buffer (by default 5%, but this may also be configured); beyond that the allocation comes from the shared portion. In this context, control packets means packets that originate from within the router. These packets are identified by the absence of an ingress net, not by DSCP.

[end]