CREDIT FLOW CONTROL FOR ETHERNET

• US 20150009823A1
• Filed: 06/24/2014
• Published: 01/08/2015
• Est. Priority Date: 07/02/2013
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Ganga, Ilango, Vasudevan, Anil, Perlman, Radia, Regnier, Greg, Wilkinson, Hugh, Gravel, Alain
• Granted Patent: US 9,674,098 B2
• Time in Patent Office: Days
• US Class Current: 370/235
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: Y02D 30/00 Reducing energy consumption in communication networks

Abstract

One embodiment provides a method for enabling class-based credit flow control for a network node in communication with a link partner using an Ethernet communications protocol. The method includes receiving a control frame from the link partner. The control frame includes at least one field for specifying credit for at least one traffic class and the credit is based on available space in a receive buffer associated with the at least one traffic class. The method further includes sending data packets to the link partner based on the credit, the data packets associated with the at least one traffic class.

Claims

1. A network controller to communicate with a link partner, the network controller comprising:

a receiver circuit to receive a control frame from the link partner, wherein the control frame includes at least one field for specifying credit for at least one traffic class, wherein the credit is based on available space in a receive buffer associated with the at least one traffic class; and

a transmit scheduler module to send data packets to the link partner based on the credit, the data packets associated with the at least one traffic class.

2. The network controller of claim 1, wherein the receiver circuit is further to receive a data frame from the link partner, wherein the data frame includes at least one field for specifying credit flow control operations for at least one traffic class.

3. The network controller of claim 2, wherein the data frame and the control frame are compatible with the Ethernet communications.

4. The network controller of claim 1, wherein the control frame is received periodically based on, at least in part, the size of the receive buffer associated with the at least one traffic class.

5. The network controller of claim 1, further to generate a configuration frame that includes at least one field for defining at least one parameter related to credit flow control;

wherein the configuration frame is exchanged between the network controller and the link partner when a link between the network controller and the link partner is initialized and/or when there is a configuration change at the network controller or the link partner.

6. The network controller of claim 5, wherein the configuration frame is a Link Layer Discovery Protocol (LLDP) frame with a Type Length Value (TLV) format.

7. The network controller of claim 1, further to track the credits available at the link partner for at least one traffic class based on the control frame received from the link partner.

8. The network controller of claim 7, further to suspend sending packets to the link partner if a frame size of the packet exceeds a threshold, the threshold based on the tracked credits, the suspended packets associated with the traffic class for which the threshold has been exceeded.

9. The network controller of claim 2, wherein the data frame includes a field for specifying credit flow control operations for up to 32 traffic classes.

10. The network controller of claim 1, wherein the network controller is incorporated in a network node element.

11. A method for enabling class-based credit flow control for a network controller in communication with a link partner, comprising:

receiving a control frame from the link partner, wherein the control frame includes at least one field for specifying credit for at least one traffic class, wherein the credit is based on available space in a receive buffer associated with the at least one traffic class; and

sending data packets to the link partner based on the credit, the data packets associated with the at least one traffic class.

12. The method of claim 11, further comprising receiving a data frame from the link partner, wherein the data frame includes at least one field for specifying credit flow control operations for at least one traffic class.

13. The method of claim 12, wherein the data frame and the control frame are compatible with the Ethernet communications.

14. The method of claim 11, further comprising receiving the control frame periodically based on, at least in part, the size of the receive buffer associated with the at least one traffic class.

15. The method of claim 11, further comprising generating a configuration frame that includes at least one field for defining at least one parameter related to credit flow control;

wherein the configuration frame is exchanged between the network controller and the link partner when a link between the network controller and the link partner is initialized and/or when there is a configuration change at the network controller or the link partner.

16. The method of claim 15, wherein the configuration frame is a Link Layer Discovery Protocol (LLDP) frame with a Type Length Value (TLV) format.

17. The method of claim 11, further comprising tracking the credits available at the link partner for at least one traffic class based on the control frame received from the link partner.

18. The method of claim 17, further comprising suspending sending packets to the link partner if a frame size of the packet exceeds a threshold, the threshold based on the tracked credits, the suspended packets associated with the traffic class for which the threshold has been exceeded.

19. At least one computer-readable storage medium having instructions stored thereon which when executed by a processor result in the following operations for enabling class-based credit flow control for a network controller in communication with a link partner, comprising:

receiving a control frame from the link partner, wherein the control frame includes at least one field for specifying credit for at least one traffic class, wherein the credit is based on available space in a receive buffer associated with the at least one traffic class; and

sending data packets to the link partner based on the credit, the data packets associated with the at least one traffic class.

20. The computer-readable storage medium of claim 19, further comprising the operation of receiving a data frame from the link partner, wherein the data frame includes at least one field for specifying credit flow control operations for at least one traffic class.

21. The computer-readable storage medium of claim 20, wherein the data frame and the control frame are compatible with Ethernet communications.

22. The computer-readable storage medium of claim 19, further comprising the operation of receiving the control frame periodically based on, at least in part, the size of the receive buffer associated with the at least one traffic class.

23. The computer-readable storage medium of claim 19, further comprising the operation of generating a configuration frame that includes at least one field for defining at least one parameter related to credit flow control;

wherein the configuration frame is exchanged between the network controller and the link partner when a link between the network controller and the link partner is initialized and/or when there is a configuration change at the network controller or the link partner.

24. The computer-readable storage medium of claim 23, wherein the configuration frame is a Link Layer Discovery Protocol (LLDP) frame with a Type Length Value (TLV) format.

25. The computer-readable storage medium of claim 23, further comprising the operation of tracking the credits available at the link partner for at least one traffic class based on the control frame received from the link partner.

26. The computer-readable storage medium of claim 25, further comprising the operation of suspending sending packets to the link partner if a frame size of the packet exceeds a threshold, the threshold based on the tracked credits, the suspended packets associated with the traffic class for which the threshold has been exceeded.

27. The computer-readable storage medium of claim 20, wherein the data frame includes a field for specifying credit flow control operations for up to 32 traffic classes.

28. A system for enabling class-based credit flow control for a network controller in communication with a link partner, comprising:

means for receiving a control frame from the link partner, wherein the control frame includes at least one field for specifying credit for at least one traffic class, wherein the credit is based on available space in a receive buffer associated with the at least one traffic class; and

means for sending data packets to the link partner based on the credit, the data packets associated with the at least one traffic class.

29. The system of claim 28, further comprising means for receiving a data frame from the link partner, wherein the data frame includes at least one field for specifying credit flow control operations for at least one traffic class.