Methods and devices for transmitting data between storage area networks

• US 7,738,493 B2
• Filed: 01/23/2003
• Issued: 06/15/2010
• Est. Priority Date: 01/23/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Golshan, Ali, Janakiraman, Venkatesh, Kolli, Madhuri, Mehta, Neelima, Krishnamoorthy, Pags, Ivaturi, Devi Prasad
• Primary Examiner(s): LY, ANH VU H
• Application Number:
  US10/350,574
• Publication Number:
  US 20040146054A1
• Time in Patent Office: 2,700 Days
• Field of Search: 370/395.2
• US Class Current: 370/469
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods and devices are provided for efficient transmission of data between storage area networks. According to some aspects of the invention, a “slim” TCP stack is provided which eliminates the socket layer found in a conventional TCP stack, thereby eliminating socket buffers and the associated buffer-to-buffer copying. Moreover, by eliminating the socket layer, one eliminates the listen state. This condition allows TCP processing in an interrupt context instead of client/server operation with a listen state. Accordingly, some aspects of the invention provide for transmitting data between SANs in an interrupt context.

Claims

1. A computer readable medium having a TCP stack stored therein for controlling data transmitted between storage area networks, the TCP stack comprising:

an application layer for encapsulating outgoing frames from a first storage area network and de-encapsulating incoming frames from a second storage area network;

a TCP layer that receives outgoing frames directly from the application layer;

an IP layer that interacts with the TCP layer; and

a link layer that interacts with the IP layer, wherein the TCP stack does not include a socket layer.

2. The computer readable medium of claim 1, wherein the application layer comprises a Fiber Channel Internet Protocol (“

FCIP”

) layer.

3. The computer readable medium of claim 1, wherein the link layer comprises an Ethernet layer.

4. The computer readable medium of claim 1, wherein the TCP stack performs processing in an interrupt context.

5. A method for controlling data transmitted between storage area networks, comprising:

receiving, at a network device, a first Fiber Channel Internet Protocol (“

FCIP”

) packet;

adding, by a processor, a TCP header to the first FCIP packet; and

transmitting, by a transmitter, the first FCIP packet to the Internet, wherein the receiving, adding and transmitting steps are all performed in an interrupt context and the interrupt context is initiated by receipt of an interrupt, and the interrupt context terminates either when processes included in the interrupt have been completed, the processes comprising the receiving, adding and transmitting steps, or one or more termination related events occurs.

6. The method of claim 5, wherein the interrupt context assigns a higher priority to command packets than to data packets.

7. The method of claim 5, further comprising:

receiving a second FCIP packet; and

determining whether the second FCIP packet may be sent in the interrupt context.

8. The method of claim 7, wherein it is determined that the second FCIP packet may be sent in the interrupt context, further comprising:

adding a TCP header to the second FCIP packet; and

transmitting the second FCIP packet to the Internet, wherein the adding and transmitting steps are performed in the interrupt context.

9. The method of claim 7, wherein the determining step comprises determining whether a maximum time has elapsed during the interrupt context.

10. The method of claim 7, wherein the determining step comprises determining whether a maximum number of FCIP packets has been sent prior to receiving an acknowledgement packet during the interrupt context.

11. The method of claim 7, wherein the determining step comprises determining whether a maximum number of bytes has been sent prior to receiving an acknowledgement packet during the interrupt context.

12. The method of claim 7, wherein the steps of receiving, adding and transmitting comprise a loop and wherein the determining step comprises determining whether a maximum number of loops has occurred during the interrupt context.

13. A computer readable medium having a computer executable program stored therein for controlling data transmitted between storage area networks, the computer executable program including instructions for controlling a network device to perform the following steps:

receiving, at the network device, a first Fiber Channel Internet Protocol (“

FCIP”

) packet;

adding, by a processor, a TCP header to the first FCIP packet;

and transmitting, by a transmitter, the first FCIP packet to the Internet, wherein the receiving, adding and transmitting steps are all performed in an interrupt context and the interrupt context is initiated by receipt of an interrupt, and the interrupt context terminates either when processes included in the interrupt have been completed, the processes comprising the receiving, adding and transmitting steps, or one or more termination related events occurs.

14. The computer readable medium of claim 13, wherein the interrupt context assigns a higher priority to command packets than to data packets.

15. The computer readable medium of claim 13, wherein the computer program further comprises instructions for controlling the network device to perform the following steps:

receiving a second FCIP packet; and

determining whether the second FCIP packet may be sent in the interrupt context.

16. The computer readable medium of claim 15, wherein the network device determines that the second FCIP packet may be sent in the interrupt context and wherein the computer program further comprises instructions for controlling the network device to perform the following steps:

adding a TCP header to the second FCIP packet; and

transmitting the second FCIP packet to the Internet, wherein the adding and transmitting steps are performed in the interrupt context.

17. The computer readable medium of claim 15, wherein the determining step comprises determining whether a maximum time has elapsed during the interrupt context.

18. The computer readable medium of claim 15, wherein the determining step comprises determining whether a maximum number of FCIP packets has been sent prior to receiving an acknowledgement packet during the interrupt context.

19. The computer readable medium of claim 15, wherein the determining step comprises determining whether a maximum number of bytes has been sent prior to receiving an acknowledgement packet during the interrupt context.

20. The computer readable medium of claim 15, wherein the steps of receiving, adding and transmitting comprise a loop and wherein the determining step comprises determining whether a maximum number of loops has occurred during the interrupt context.

21. An apparatus for controlling data transmitted between storage area networks, the apparatus comprising:

means for receiving a first Fiber Channel Internet Protocol (“

FCIP”

) packet;

means for adding a TCP header to the first FCIP packet; and

means for transmitting the first FCIP packet to the Internet, wherein the receiving, adding and transmitting means are all configured to operate in an interrupt context and the interrupt context is initiated by receipt of an interrupt, and the interrupt context terminates either when processes included in the interrupt have been completed, the processes comprising the receiving, adding and transmitting steps, or one or more termination related events occurs.

22. The apparatus of claim 21, wherein the interrupt context comprises assigning a higher priority to command packets than to data packets.

23. The apparatus of claim 21, wherein the apparatus further comprises:

means for receiving a second FCIP packet; and

means for determining whether the second FCIP packet may be sent in the interrupt context.

24. The apparatus of claim 21, wherein the apparatus comprises a router.

25. The apparatus of claim 21, wherein the apparatus comprises a switch.

26. The apparatus of claim 21, wherein the apparatus comprises a fiber channel port adapter card.

27. The apparatus of claim 23, wherein it is determined that the second FCIP packet may be sent in the interrupt context, further comprising:

means for adding a TCP header to the second FCIP packet; and

means for transmitting the second FCIP packet to the Internet, wherein the adding and transmitting are performed in the interrupt context.

28. The apparatus of claim 23, wherein the determining means comprises means for determining whether a maximum time has elapsed during the interrupt context.

29. The apparatus of claim 23, wherein the determining means comprises means for determining whether a maximum number of FCIP packets has been sent prior to receiving an acknowledgement packet during the interrupt context.

30. The apparatus of claim 23, wherein the determining means comprises means for determining whether a maximum number of bytes has been sent prior to receiving an acknowledgement packet during the interrupt context.

31. The apparatus of claim 23, wherein the receiving, adding and transmitting means comprise a loop and wherein the determining means comprises means for determining whether a maximum number of loops has occurred during the interrupt context.

32. A method for controlling data transmitted between a first network device and a second network device, comprising:

receiving a first Fiber Channel Internet Protocol (“

FCIP”

) packet from a storage area network (“

SAN”

) at the first network device;

adding, by a processor, a TCP header to the first FCIP packet; and

transmitting, by a transmitter, the first FCIP packet from the first network device to the second network device via the Internet, wherein the receiving, adding and transmitting steps are all performed in an interrupt context and the interrupt context is initiated by receipt of an interrupt, and the interrupt context terminates either when processes included in the interrupt have been completed, the processes comprising the receiving, adding and transmitting steps, or one or more termination related events occurs.

33. The method of claim 32, wherein neither the first network device nor the second network device listens for connection requests under TCP.

34. The method of claim 32, wherein the first network device and the second network device are in the condition of simultaneous open.

35. A network device for controlling data transmitted between storage area networks, the network device comprising:

a first interface configured to receive a first Fiber Channel Internet Protocol (“

FCIP”

) packet;

a processor configured to add a TCP header to the first FCIP packet to cause the first FCIP packet to be transmitted to the Internet, wherein the receiving of the first FCIP packet, the adding of the TCP header and the transmitting of the first FCIP packet are all performed in an interrupt context and the interrupt context is initiated by receipt of an interrupt, and the interrupt context terminates either when processes included in the interrupt have been completed, the processes comprising the receiving, adding and transmitting steps, or one or more termination related events occurs.

36. The network device of claim 35, wherein the network device comprises a line card and wherein the processor is associated with the line card.