Interconnecting network processors with heterogeneous fabrics

• US 8,254,397 B2
• Filed: 07/08/2009
• Issued: 08/28/2012
• Est. Priority Date: 12/05/2002
• Status: Expired due to Term

• Current Assignee: Tahoe Research Limited (f/k/a Learndale Limited) (Vector Capital Corporation)
• Original Assignee: Intel Corporation
• Inventors: Lebizay, Gerald, Gish, David W., Oliver, Neal C.
• Primary Examiner(s): CHO, HONG SOL
• Application Number:
  US12/499,366
• Publication Number:
  US 20100118875A1
• Time in Patent Office: 1,147 Days
• Field of Search: 370/338, 370/389, 370/392, 370/401, 370/395.6, 370/466
• US Class Current: 370/401
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus to perform protocol translation for a modular system may be described wherein a first packet created in accordance with a first protocol is received, a packet type for the first packet is determined, a second protocol based on the packet type is selected and the first packet is translated to a second packet in accordance with the second protocol. Other embodiments are described and claimed.

Claims

1. A method to translate a protocol, comprising:

receiving at least one first packet created in accordance with a first protocol, said first packet comprises header information and payload information;

determining a packet type for said first packet;

selecting a second protocol suitable for said first protocol from among multiple protocols based on said packet type; and

translating said at least one first packet to at least one second packet in accordance with said second protocol, said translating comprises;

mapping a network address to a destination field of said at least one second packet;

mapping said header information and a portion of said payload information into said at least one second packet;

mapping any remaining payload information into additional packets until said payload information has been mapped; and

adding a header to each of said second packet and said additional packets.

2. The method of claim 1, wherein said first protocol comprises a protocol as defined by an Infiniband Specification.

3. The method of claim 2, wherein said packet type comprises a Backward Event Congestion Notification (BECN) packet.

4. The method of claim 3, wherein said second protocol comprises a protocol in accordance with a CSIX Specification.

5. The method of claim 4, wherein said translating comprises:

retrieving a Local Route Header (LRH) having BECN information in a BECN message field from said first packet;

retrieving said network address and congestion control information from said BECN information, said congestion control information having a first portion and a second portion;

mapping said network address to a CSIX destination address field of said second packet;

mapping said first portion to a CSIX speed field of said second packet; and

mapping said second portion to a CSIX class field of said second packet.

6. The method of claim 2, wherein said packet type comprises an Infiniband data packet.

7. The method of claim 6, wherein said second protocol comprises a protocol in accordance with a SPI-4 Specification.

8. The method of claim 2, wherein said packet type comprises a Multi-Protocol Label Format (MPLF) packet.

9. The method of claim 8, wherein said second protocol comprises a protocol in accordance with a CSIX Specification.

10. The method of claim 9, wherein said first packet comprises Local Route Header (LRH) information, said header information comprises MPLF header information and said header comprises a CSIX header field, and said translating comprises:

mapping at least a portion of said LRH information into each CSIX header field.

11. The method of claim 10, wherein said mapping at least said portion of said LRH information comprises:

retrieving service level information, length information and said network address from said LRH information; and

mapping said service level information to a CSIX class field, said length information to a CSIX length field, a first portion of said network address to a CSIX destination address field, and a second portion of said network address to a CSIX reserved field.

12. The method of claim 1, wherein said first protocol is a protocol as defined by a SPI-4 Specification.

13. The method of claim 12, wherein said packet type comprises one of a Backward Event Congestion Notification (BECN) packet, an Infiniband data packet and a Multi-Protocol Label Format (MPLF) packet.

14. The method of claim 13, wherein said second protocol comprises a protocol in accordance with an Infiniband Specification.

15. The method of claim 14, wherein said first packet is a SPI-4 packet in a sequence of SPI-4 packets, and said translating comprises:

retrieving said header information and a portion of said payload information from said first packet;

retrieving any remaining payload information from additional SPI-4 packets in said sequence; and

creating said at least one second packet using said header information and payload information.

16. The method of claim 1, wherein said first protocol is a protocol as defined by ExB/AS Specification.

17. The method of claim 16, wherein said second protocol is a protocol in accordance with one of a CSIX Specification and SPI-4 Specification.

18. An article comprising:

a non-transitory storage medium;

said storage medium encoded with instructions that, when executed by a processor, result in translating a protocol by receiving at least one first packet created in accordance with a first protocol, said first packet comprising header information and payload information, determining a packet type for said first packet, selecting a second protocol suitable for said first protocol from among multiple protocols based on said packet type, and translating said at least one first packet to at least one second packet in accordance with said second protocol, said translating is performed by mapping a network address to a destination field of said at least one second packet, mapping said header information and a portion of said payload information into said at least one second packet, mapping any remaining payload information into additional packets until said payload information has been mapped, and adding a header to each of said second packet and said additional packets.

19. The article of claim 18, wherein the stored instructions, when executed by a processor, further result in said first protocol comprising a protocol as defined by an Infiniband Specification.

20. The article of claim 19, wherein the stored instructions, when executed by a processor, further result in said packet type comprising a Backward Event Congestion Notification (BECN) packet.

21. The article of claim 20, wherein the stored instructions, when executed by a processor, further result in said second protocol comprising a protocol in accordance with a CSIX Specification.

22. The article of claim 21, wherein the stored instructions, when executed by a processor, further result in said translating by retrieving a Local Route Header (LRH) having BECN information in a BECN message field from said first packet, retrieving said network address and congestion control information from said BECN information, said congestion control information having a first portion and a second portion, mapping said network address to a CSIX destination address field of said second packet, mapping said first portion to a CSIX speed field of said second packet, and mapping said second portion to a CSIX class field of said second packet.

23. The article of claim 18, wherein the stored instructions, when executed by a processor, further result in said packet type comprising an Infiniband data packet.

24. The article of claim 23, wherein the stored instructions, when executed by a processor, further result in said second protocol comprising a protocol in accordance with a SPI-4 Specification.

25. The article of claim 18, wherein the stored instructions, when executed by a processor, further result in said packet type comprising a Multi-Protocol Label Format (MPLF) packet.

26. The article of claim 25, wherein the stored instructions, when executed by a processor, further result in said second protocol comprising a protocol in accordance with a CSIX Specification.

27. The article of claim 26, wherein the stored instructions, when executed by a processor, further result in said first packet comprising Local Route Header (LRH) information, said header information comprising MPLF header information and said header comprising a CSIX header field, and said translating is performed by mapping at least a portion of said LRH information into each CSIX header field.

28. The article of claim 27, wherein the stored instructions, when executed by a processor, further result in said mapping at least said portion of said LRH information by retrieving service level information, length information and said network address from said LRH information, and mapping said service level information to a CSIX class field, said length information to a CSIX length field, a first portion of said network address to a CSIX destination address field, and a second portion of said network address to a CSIX reserved field.

29. The article of claim 18, wherein the stored instructions, when executed by a processor, further result in said first protocol being a protocol as defined by a SPI-4 Specification.

30. The article of claim 29, wherein the stored instructions, when executed by a processor, further result in said packet type comprising one of a Backward Event Congestion Notification (BECN) packet, an Infiniband data packet and a Multi-Protocol Label Format (MPLF) packet.

31. The article of claim 30, wherein the stored instructions, when executed by a processor, further result in said second protocol comprising a protocol in accordance with an Infiniband Specification.

32. The article of claim 31, wherein the stored instructions, when executed by a processor, further result in said first packet being a SPI-4 packet in a sequence of SPI-4 packets, and said translating is performed by retrieving said header information and a portion of said payload information from said first packet, retrieving any remaining payload information from additional SPI-4 packets in said sequence, and creating said at least one second packet using said header information and payload information.

33. The article of claim 32, wherein the stored instructions, when executed by a processor, further result in said first protocol being a protocol as defined by ExB/AS Specification.

34. The article of claim 33, wherein the stored instructions, when executed by a processor, further result in said second protocol being a protocol in accordance with one of a CSIX Specification and SPI-4 Specification.

35. A system, comprising:

a switching fabric; and

at least one network node connected to said switching fabric, said network node comprising a network processor and, a Fabric Interface Chip (FIC), wherein said FIC translates at least one first packet communicated between said switching fabric and said network processor from a first protocol to a second protocol, suitable for said first protocol, selected from among varying protocols based on a packet type associated with each packet, said first packet comprising header information and payload information, and

said FIC translates by mapping a network address to a destination field of at least one second packet, mapping said header information and a portion of said payload information into said at least one second packet, mapping any remaining payload information into additional packets until said payload information has been mapped, and adding a header to each of said second packet and said additional packets.

36. The system of claim 35, wherein said network node further comprises an ingress port and an adjunct port, and said FIC translates at least one first packet communicated between said network processor and said ports from a first protocol to a second protocol based on said packet type.

37. The system of claim 36, wherein said first protocol is an Infiniband protocol, said packet type is a Backward Event Congestion Notification (BECN) packet, and said second protocol is a CSIX protocol.

38. The system of claim 36, wherein said first protocol is an Infiniband protocol, said packet type is a Multi-Protocol Label Format (MPLF) packet, and said second protocol is a CSIX protocol.

39. The system of claim 36, wherein said first protocol is an Infiniband protocol, said packet type is an IBA data packet, and said second protocol is a SPI-4 protocol.

40. The system of claim 36, wherein said first protocol is SPI-3 protocol, said packet type is a SPI-3 packet, and said second protocol is a SPI-4 protocol.

41. The system of claim 36, wherein said first protocol is a S-RIO protocol, said packet type is a S-RIO packet, and said second protocol is a SPI-4 protocol.

42. The system of claim 36, wherein said first protocol is a ExB/AS protocol, said packet type is a ExB/AS packet, and said second protocol is a SPI-4 protocol.

43. The system of claim 36, wherein said first protocol is a SPI-4 protocol, said packet type is BECN packet, and said second protocol is an Infiniband protocol.

44. The system of claim 36, wherein said first protocol is a SPI-4 protocol, said packet type is MPLF packet, and said second protocol is an Infiniband protocol.

45. The system of claim 36, wherein said first protocol is a SPI-4 protocol, said packet type is IBA data packet, and said second protocol is an Infiniband protocol.

46. The system of claim 36, wherein said first protocol is a SPI-4 protocol, said packet type is a SPI-3 packet, and said second protocol is a SPI-3 protocol.

47. The system of claim 36, wherein said first protocol is a SPI-4 protocol, said packet type is S-RIO packet, and said second protocol is a S-RIO protocol.

48. The system of claim 36, wherein said first protocol is a SPI-4 protocol, said packet type is ExB/AS packet, and said second protocol is a ExB/AS protocol.