Apparatus and method for performing fast fibre channel write operations over relatively high latency networks

• US 7,934,023 B2
• Filed: 12/01/2003
• Issued: 04/26/2011
• Est. Priority Date: 12/01/2003
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Iyengar, Magesh, Ambati, Satish, Edsall, Thomas, Chandrasekaran, Varagur V., Gai, Silvano, Dutt, Dinesh G., Basavaiah, Murali
• Primary Examiner(s): Lee; Chun-Kuan
• Assistant Examiner(s): Unelus; Ernest
• Application Number:
  US10/726,269
• Publication Number:
  US 20050117522A1
• Time in Patent Office: 2,703 Days
• Field of Search: 370/392, 370/252, 710/5, 707/10, 711/114
• US Class Current: 710/5
• CPC Class Codes: G06F 3/0613 in relation to throughput
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• 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]

Abstract

A method and apparatus to improve the performance of a SCSI write over a high latency network. The apparatus includes a first Switch close to the initiator in a first SAN and a second Switch close to the target in a second SAN. In various embodiments, the two Switches are border switches connecting their respective SANs to a relatively high latency network between the two SANs. In addition, the initiator can be either directly connected or indirectly connected to the first Switch in the first SAN. The target can also be either directly or indirectly connected to the second Switch in the second SAN. During operation, the method includes the first Switch sending Transfer Ready (Xfr_rdy) frame(s) based on buffer availability to the initiating Host in response to a SCSI Write command from the Host directed to the target. The first and second Switches then coordinate with one another by sending Transfer Ready commands to each other independent of the target'"'"'s knowledge. The second switch buffers the data received from the Host until the target indicates it is ready to receive the data. Since the Switches send frames to the initiating Host independent of the target, the Switches manipulate the OX_ID and RX_ID fields in the Fiber Channel header of the various commands associated with the SCSI Write. The OX_ID and RX_ID fields are manipulated so as to trap the commands and so that the Switches can keep track of the various commands associated with the SCSI write.

Claims

1. A switch comprising:

a port configured to receive a write command frame, the frame having a header comprising an originator exchange identifier (OX_ID) field and a receiver exchange identifier (RX_ID) field, as well as a Host identifier field and a target identifier field, wherein the Host and the target identifier fields identify Host and target devices, and wherein the OX_ID and the RX_ID exchange identifier fields enable the Host and the target to keep track of various transactions between each other;

a trapping mechanism configured to trap the write command frame; and

a processor configured to process the trapped write command frame by modifying the OX_ID field of the write command frame header to include a new value of an OX_ID exchange identifier before sending the write command frame to the target;

wherein the processor is further configured to generate a transfer ready command frame, initialize a receiver exchange identifier (RX_ID) of the transfer ready command frame by assigning a value to the RX_ID field, the assigned RX_ID corresponding to a write command session,

send the transfer ready command frame to the initiating Host before receiving a transfer ready command frame from the target;

receive a command frame with the assigned RX_ID value; and

use the RX_ID value as a handle for accessing information pertaining to the write command session in a sessions table, the sessions table storing information about one or more sessions or exchanges.

2. The switch of claim 1, wherein the switch is an initiating Switch coupled to the Host in a first SAN.

3. The switch of claim 2, wherein the processor of the initiating Switch is further configured to modify the write command frame before forwarding the write command to the target.

4. The switch of claim 2, wherein the processor of the initiating Switch is further configured to issue a Transfer Ready command to the Host.

5. The switch of claim 2, wherein the initiating Switch is further configured to transfer additional data frames to the target when the initiating Switch receives a Transfer Ready command associated with the write command frame from the target.

6. The switch of claim 1, wherein the switch is further configured to use the assigned RX-ID value as the RX_ID for all communication related to the write command between the switch and the Host.

7. The switch of claim 1, wherein the switch is further configured to use the new OX_ID value as the OX_ID in all communications between the switch and the target.

8. The switch of claim 1, wherein the switch is further configured to use the RX_ID value of trapped write commands to specify the amount of buffer space needed for the write command and use the write command frame to request the needed buffer space.

9. The switch of claim 8, wherein the switch is further configured to use the RX_ID value of trapped write commands to specify the amount of buffer space larger than needed for the write command and use the additional buffer space for subsequent write commands so that the switch need not wait for a Transfer Ready command to transfer data related to the subsequent write command.

10. The switch of claim 1, wherein the switch is further configured to, in the event the switch does not have sufficient buffer space for the write command, to either:

(i) generate a busy status signal to the initiating Host;

(ii) place the write command on a pending wait list;

or (iii) forward the write command to the target.

11. The switch of claim 1, further comprising:

a first SAN including the switch;

a second SAN; and

an inter-SAN network connecting the first SAN and the second SAN.

12. The switch as recited in claim 1, wherein the switch is further configured to determine from the write command an amount of data to be written to the target, to ascertain whether it has sufficient storage space to buffer the amount of data, and to send the generated transfer ready command frame to the initiating Host before receiving a transfer ready command from the target if the switch has determined that it has sufficient storage space to buffer the amount of data.

13. The switch as recited in claim 1, wherein the trapping mechanism is configured to trap the write command frame if the write command frame designates a predetermined Host_ID and a predetermined target_ID.

14. A method comprising:

receiving a write command at a switch, the write command specifying a host identifier corresponding to a host device and a target identifier corresponding to a target device, the write command also including an originator exchange identifier (OX_ID) field with an assigned value and an uninitialized receiver exchange identifier (RX_ID) field with a default value, wherein the OX_ID and the RX_ID fields enable the host and the target to keep track of various transactions between each other;

generating a transfer ready command at the switch;

initializing a receiver exchange identifier (RX_ID) of the transfer ready command by assigning a value to the RX_ID field, the assigned RX_ID value corresponding to a write command session;

sending a transfer ready command including the initialized RX_ID to the host prior to receiving a transfer ready command from the target, wherein sending the transfer ready command to the host allows the switch to operate as a proxy for the target;

modifying the originator exchange identifier (OX_ID) of the write command to generate a modified write command;

forwarding the modified write command to the target;

receiving a command with the assigned RX_ID value; and

using the RX_ID value as a handle for accessing information pertaining to the write command session in a sessions table, the sessions table storing information about one or more sessions or exchanges.

15. The method of claim 14, further comprising configuring the switch to forward data frames associated with the write command received in response to the transfer ready command to the target.

16. The method of claim 15, wherein a second switch between the switch and the target receives data frames associated with the write command and buffers the data frames until a transfer ready command is received from the target.

17. An apparatus comprising:

means for receiving a write command at a switch, the write command specifying a host identifier corresponding to a host device and a target identifier corresponding to a target device, the write command also including an originator exchange identifier (OX_ID) field with an assigned value and an uninitialized receiver exchange identifier (RX_ID) field with a default value, wherein the OX_ID and the RX_ID exchange identifier fields enable the host and the target to keep track of various transactions between each other;

means for generating a transfer ready command;

means for initializing a RX_ID of the transfer ready command by assigning a value to the RX_ID field, the assigned RX_ID value corresponding to a write command session;

means for sending a transfer ready command including the initialized RX_ID to the host prior to receiving a transfer ready command from the target, wherein sending the transfer ready command to the host allows the switch to operate as a proxy for the target;

means for modifying the OX_ID field of the write command to generate a modified write command;

means for forwarding the modified write command to the target;

means for receiving a command with the assigned RX_ID value; and

means for using the RX_ID value as a handle for accessing information pertaining to the write command session in a sessions table, the sessions table storing information about one or more sessions or exchanges.

18. A method comprising:

receiving a write command at a switch, the write command specifying a host identifier corresponding to a host device and a target identifier corresponding to a target device, the write command also including an originator exchange identifier (OX_ID) field and a receiver exchange identifier (RX_ID) field, wherein the OX_ID and the RX_ID exchange identifier fields enable the host and the target to keep track of various transactions between each other;

assigning a new value to the OX_ID field in the write command;

forwarding the write command to the target;

receiving a transfer ready command from the target;

sending the transfer ready command to the host;

receiving a command with the assigned OX_ID value; and

using the OX_ID value as a handle for accessing information pertaining to the write command session in a sessions table, the sessions table storing information about one or more sessions or exchanges.

19. A switch comprising:

an interface;

a processor; and

a memory, at least one of the interface, the processor or the memory being for;

receiving a write command, the write command specifying a host identifier corresponding to a host device and a target identifier corresponding to a target device, the write command also including an originator exchange identifier (OX_ID) field and a receiver exchange identifier (RX_ID) field, wherein the OX_ID and the RX_ID exchange identifier fields enable the host and the target to keep track of various transactions between each other;

assigning a new value to the OX-ID field in the write command;

forwarding the write command to the target;

receiving a transfer ready command from the target;

sending the transfer ready command to the host;

receiving a command with the assigned OX_ID value; and

using the OX_ID value as a handle for accessing information pertaining to the write command session in a sessions table, the sessions table storing information about one or more sessions or exchanges.

20. The switch of claim 19, wherein the switch is a target Switch coupled to the target.

21. The switch of claim 20, wherein the target Switch forwards the write command frame to the target.

22. The switch of claim 21, wherein the target Switch forwards data frames associated with the write command frame to the target after receiving a Transfer Ready command from the target.

23. The switch of claim 22, wherein the target Switch is further configured to buffer the data frames prior to receipt of the Transfer Ready command.

24. The switch of claim 22, wherein the target Switch is further configured to maintain a sessions ID table and to use the OX_ID value of the write command frame as an index to the session corresponding to the write command.

25. The switch of claim 24, wherein the target Switch is further configured to modify the OX_ID value in communications between the target Switch and the target.

26. The switch of claim 20, wherein the target Switch is further configured to modify the RX_ID value for all communication related to the write command frame between the target Switch and the Host.