Network processor architecture
A network processor for processing information elements is described. Each information element is associated with a flow and comprises at least one information element segment. A policy controller stores an information element into at least one information segment storage unit within a memory, and determines whether an information element segment conforms to a predetermined quality of service (“QoS”). A traffic processor selects the information element segment for forwarding based on at least one QoS parameter. A forwarding processor forwards the selected information element segment to an egress port.
1. A system to manage congestion of a plurality of ports, comprising:
a first network processor including a traffic processor;
a second network processor for informing the first network processor whether a logical egress port is available, wherein the traffic processor does not schedule a flow for forwarding from the logical egress port if the first network processor has been informed by the second network processor that the logical egress port is not available;
wherein the logical egress port is associated with a physical egress port and a priority corresponding to the flow.
2. The system of claim 1 , wherein the first network processor and the second network processor operate in simplex mode in opposite directions.
3. The system of claim 2 , wherein the first network processor is an ingress network processor, and the second network processor is an egress network processor.
4. The system of claim 1 , further comprising a backpressure memory for storing a backpressure lookup table, wherein the second network processor indicates egress port availability by setting, in the backpressure lookup table of the backpressure memory, a backpressure indicator corresponding to the logical egress port, wherein the backpressure indicator indicates whether or not the logical egress port is congested.
5. The system of claim 4 , further comprising a per-flow traffic descriptor including designations of the physical egress port and the priority corresponding to the flow, and the traffic processor addresses the backpressure lookup table of the backpressure memory with a logical egress port address formed from a physical egress port address of the physical egress port and from the priority to retrieve the backpressure indicator.
6. A method for managing congestion of a plurality of ports, comprising:
a second network processor informing a first network processor whether a logical egress port is available, wherein the first network processor does not schedule a flow for forwarding from the logical egress port if the first network processor has been informed by the second network processor that the logical egress port is not available;
wherein the logical egress port is associated with a physical egress port and a priority corresponding to the flow.
7. The method of claim 6 , wherein the first network processor and the second network processor operate in simplex mode in opposite directions.
8. The method of claim 7 , wherein the first network processor is an ingress network processor, and the second network processor is an egress network processor.
9. The method of claim 6 , further comprising the second network processor indicating egress port availability by setting, in a backpressure lookup table of a backpressure memory a backpressure indicator corresponding to the logical egress port, wherein the backpressure indicator indicates whether or not the logical egress port is congested.
10. The method of claim 9 , further comprising designating, in a per-flow traffic descriptor, the physical egress port and the priority corresponding to the flow, and addressing the backpressure lookup table of the backpressure memory with a logical egress port address formed from a physical egress port address of the physical egress port and from the priority to retrieve the backpressure indicator.
11. The system of claim 5 , further comprising a plurality of shapers and wherein the priority of the per-flow traffic descriptor indicates the priority of a shaper to which the flow is attached.
12. The system of claim 5 , further comprising at least one shaper and at least one group of shapers and wherein the priority of the per-flow traffic descriptor includes a priority field that is divided into two priorities, one priority that corresponds to a group of shapers and another priority that corresponds to an individual shaper priority.