INTERCONNECTING NETWORK PROCESSORS WITH HETEROGENEOUS FABRICS

• US 20130177028A1
• Filed: 08/15/2012
• Published: 07/11/2013
• Est. Priority Date: 12/05/2002
• Status: Active Grant

• 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.
• Granted Patent: US 8,705,547 B2
• Time in Patent Office: Days
• US Class Current: 370/466
• 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.

Claims

1-20. -20. (canceled)

21. A method comprising:

receiving a first packet created in accordance with a first protocol;

determining a packet type for the first packet;

selecting a second protocol based on the packet type; and

translating the first packet to at least one second packet in accordance with the second protocol, translating to include;

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

mapping header information and at least a portion of payload information included in the first packet to the at least one second packet; and

mapping any remaining payload information into one or more additional second packets until the payload information has been mapped.

22. The method of claim 21, the first protocol comprises a protocol as defined by an Infiniband specification.

23. The method of claim 22, the packet type comprises one of a congestion control packet, an Infiniband data packet, a multi-protocol label format (MPLF) packet, a SPI-3 packet or a S-RIO packet.

24. The method of claim 23, the second protocol comprises a protocol in accordance with a SPI-4 specification.

25. The method of claim 24, translating comprises:

adding a SPI-4 header to the at least one second packet and to each of the one or more additional second packets.

26. The method of claim 21, the first protocol is a protocol as defined by a SPI-4 specification.

27. The method of claim 26, the packet type comprises one of a congestion control packet, an Infiniband data packet or a multi-protocol label format (MPLF) packet.

28. The method of claim 27, the second protocol comprises a protocol in accordance with an Infiniband specification.

29. The method of claim 28, the first packet is a SPI-4 packet in a sequence of SPI-4 packets, and translating comprises:

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

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

creating the at least one second packet using the header information from the first packet and payload information retrieved from the first packet and retrieved from the additional SP-4 packets in the sequence.

33. The system of claim 23, the second protocol comprises a protocol in accordance with a SPI-4 specification.

34. The system of claim 24, translating comprises the FIC capable of:

adding a SPI-4 header to the at least one second packet and to each of the one or more additional second packets.

30. A system comprising:

a network processor for a network node, the network node capable of coupling to a switch fabric;

a fabric interface chip (FIC) capable of receiving a first packet created in accordance with a first protocol via the switch fabric, selecting a second protocol from among multiple protocols based on a packet type associated with the first packet, translating the first pack to at least one second packet in accordance with the second protocol and forwarding the at least one second packet to the network processor, translating the first packet to include the FIC capable of;

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

mapping header information and at least a portion of payload information included in the first packet to the at least one second packet; and

mapping any remaining payload information into one or more additional second packets until the payload information has been mapped.

31. The system of claim 30, the first protocol comprises a protocol as defined by an Infiniband specification.

32. The system of claim 31, the packet type comprises one of a congestion control packet, an Infiniband data packet, a multi-protocol label format (MPLF) packet, a SPI-3 packet or a S-RIO packet.

35. A system, comprising:

a switching fabric; and

a network node coupled to the switching fabric, the network node having a network processor and a fabric interface chip (FIC), the FIC to translate at least one first packet communicated between the switching fabric and the network processor from a first protocol to a second protocol from among multiple protocols based on a packet type associated with each packet communicated, the at least one first packet having header information and payload information, the FIC to translate by;

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

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

mapping any remaining payload information into additional second packets until the payload information has been mapped.

36. The system of claim 35, the first protocol comprises an Infiniband protocol, the packet type is an IBA data packet, and the second protocol is a SPI-4 protocol.

37. The system of claim 35, the first protocol comprises a SPI-3 protocol, the packet type is a SPI-3 packet, and the second protocol is a SPI-4 protocol.

38. The system of claim 35, the first protocol comprises a S-RIO protocol, the packet type is a S-RIO packet, and the second protocol is a SPI-4 protocol.

39. The system of claim 35, the first protocol comprises a SPI-4 protocol, the packet type is a congestion control packet, and the second protocol is an Infiniband protocol.

40. The system of claim 35, the first protocol comprises a SPI-4 protocol, the packet type is a multi-protocol label format (MPLF) packet, and the second protocol is an Infiniband protocol.

41. The system of claim 35, the first protocol comprises a SPI-4 protocol, the packet type is IBA data packet, and the second protocol is an Infiniband protocol.

42. The system of claim 35, the first protocol comprises a SPI-4 protocol, the packet type is a SPI-3 packet, and the second protocol is a SPI-3 protocol.

44. An article comprising:

a non-transitory storage medium;

the 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, the first packet having header information and payload information, determining a packet type for the first packet, selecting a second protocol from among multiple protocols based on the packet type, and translating the at least one first packet to at least one second packet in accordance with the second protocol, translating is performed by;

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

mapping the header information and at least a portion of the payload information included in the first packet to the at least one second packet; and

mapping any remaining payload information into one or more additional second packets until the payload information has been mapped.

43. The system of claim 45, the first protocol comprises a SPI-4 protocol, the packet type is S-RIO packet, and the second protocol is a S-RIO protocol.

45. The article of claim 44, the first protocol comprises a protocol as defined by an Infiniband specification.

46. The article of claim 45, the packet type comprises one of a congestion control packet, an Infiniband data packet, a multi-protocol label format (MPLF) packet, a SPI-3 packet or a S-RIO packet.

47. The article of claim 46, the second protocol comprises a protocol in accordance with a SPI-4 specification.

48. The article of claim 47, comprising the stored instructions, when executed by a processor, further result in translating by:

adding a SPI-4 header to the at least one second packet and to each of the one or more additional second packets.

49. The article of claim 44, the first protocol is a protocol as defined by a SPI-4 Specification.

50. The article of claim 49, the packet type comprises one of a congestion control packet, an Infiniband data packet or a multi-protocol label format (MPLF) packet.

51. The article of claim 50, the second protocol comprises a protocol in accordance with an Infiniband specification.

52. The article of claim 51, the first packet comprises a SPI-4 packet in a sequence of SPI-4 packets, and the stored instructions, when executed by a processor, further result in translating by:

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

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

creating the at least one second packet using the header information from the first packet and payload information retrieved from the first packet and retrieved from the additional SP-4 packets in the sequence.