Method and system for improving bandwidth and reducing idles in fibre channel switches

Abstract

A method for routing fibre channel frames using a fibre channel switch element is provided. The switch element includes, a receiving segment in a fibre channel port for receiving the frames and a transmit segment that transmits the received frames. The method includes requesting an early frame transfer, wherein the transmit segment of a fibre channel port requests an early frame transfer from a receiving segment of the fibre channel port before a frame has arrived at the transmit segment; activating an early frame transfer; determining if there is a need for aborting the early frame transfer request; and selecting a different source port if there is a need for aborting an early frame transfer request.

Description

BACKGROUND

1. Field of the Invention

The present invention relates to fibre channel systems, and more particularly, to improving dead time between frame transmission.

2. Background of the Invention

Fibre channel is a set of American National Standard Institute (ANSI) standards, which provide a serial transmission protocol for storage and network protocols such as HIPPI, SCSI, IP, ATM and others. Fibre channel provides an input/output interface to meet the requirements of both channel and network users.

Fibre channel supports three different topologies: point-to-point, arbitrated loop and fibre channel fabric. The point-to-point topology attaches two devices directly. The arbitrated loop topology attaches devices in a loop. The fibre channel fabric topology attaches host systems directly to a fabric, which are then connected to multiple devices. The fibre channel fabric topology allows several media types to be interconnected.

Fibre channel is a closed system that relies on multiple ports to exchange information on attributes and characteristics to determine if the ports can operate together. If the ports can work together, they define the criteria under which they communicate.

In fibre channel, a path is established between two nodes where the path's primary task is to transport data from one point to another at high speed with low latency, performing only simple error detection in hardware.

Fibre channel fabric devices include a node port or “N_Port” that manages fabric connections. The N_port establishes a connection to a fabric element (e.g., a switch) having a fabric port or F_port. Fabric elements include the intelligence to handle routing, error detection, recovery, and similar management functions.

A fibre channel switch is a multi-port device where each port manages a simple point-to-point connection between itself and its attached system. Each port can be attached to a server, peripheral, I/O subsystem, bridge, hub, router, or even another switch. A switch receives messages from one port and automatically routes it to another port. Multiple calls or data transfers happen concurrently through the multi-port fibre channel switch.

Fibre channel switches use memory buffers to hold frames received (at receive buffers) and sent across (via transmit buffers) a network. Associated with these buffers are credits, which are the number of frames that a buffer can hold per fabric port.

In conventional fibre channel switches there is dead time between transmitted frames. For example, a transmit buffer requests for data after it has transmitted a frame. During this time the receive buffer already has frames waiting. This results in dead time and hence affects the overall efficiency of the switch.

Therefore, what is required is a method and system which allows a receive buffer to send data to transmit buffers earlier and improve bandwidth and reduce idles in fibre channel switches.

SUMMARY OF THE PRESENT INVENTION

In one aspect of the present invention, a method for routing fibre channel frames using a fibre channel switch element is provided. The method includes requesting an early frame transfer, wherein a transmit segment of a fibre channel port requests an early frame transfer from a receiving segment of the fibre channel port before a frame has arrived at the transmit segment; activating an early frame transfer; determining if there is a need for aborting the early frame transfer request; and selecting a different source port if there is a need for aborting an early frame transfer request.

The method further includes, transferring a frame if there is no need to abort the early frame transfer request; and generating a request abort command to abort the early frame transfer request, wherein the transmit segment sends the request abort command to the receiving segment.

A request abort command is generated if a frames status field lacks a destination bit value; if a frame's status indicates that not enough part of a frame has arrived properly; if a frame's status indicates that credit is unavailable for the frame; if the transmit segment does not have sufficient space to hold the frame; if an early frame transfer request was generated before a preference tag is received; or based on other information within the fibre channel switch element.

In another aspect of the present invention, a fibre channel switch element for routing fibre channel frames is provided. The switch element includes, a receiving segment in a fibre channel port for receiving the frames and a transmit segment that transmits the received frames, wherein the transmit segment of the fibre channel port requests an early frame transfer from the receiving segment of the fibre channel port before a frame has arrived at the transmit segment; the receive segment activates an early frame transfer; the transmit segment determines if there is a need for aborting the early frame transfer request; and a different source port is selected if there is a need for aborting an early frame transfer request.

This brief summary has been provided so that the nature of the invention may be understood quickly. A more complete understanding of the invention can be obtained by reference to the following detailed description of the preferred embodiments thereof concerning the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing features and other features of the present invention will now be described with reference to the drawings of a preferred embodiment. In the drawings, the same components have the same reference numerals. The illustrated embodiment is intended to illustrate, but not to limit the invention. The drawings include the following Figures:

FIG. 1A shows an example of a Fibre Channel network system;

FIG. 1B shows an example of a Fibre Channel switch element, according to one aspect of the present invention;

FIG. 1C shows a block diagram of a 20-channel switch chassis, according to one aspect of the present invention;

FIG. 1D shows a block diagram of a Fibre Channel switch element with sixteen GL_Ports and four 10 G ports, according to one aspect of the present invention;

FIGS. 1E-1/1E-2 (jointly referred to as FIG. 1E) show another block diagram of a Fibre Channel switch element with sixteen GL_Ports and four 10 G ports, according to one aspect of the present invention;

FIG. 2 shows a flow diagram for using an “early frame request”, according to one aspect of the present invention;

FIGS. 3A/3B (jointly referred to as FIG. 3) show a block diagram of a GL_Port, according to one aspect of the present invention; and

FIGS. 4A/4B (jointly referred to as FIG. 3) show a block diagram of XG_Port (10 G) port, according to one aspect of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Definitions

The following definitions are provided as they are typically (but not exclusively) used in the fibre channel environment, implementing the various adaptive aspects of the present invention.

“EOF”: End of Frame

“E-Port”: A fabric expansion port that attaches to another Interconnect port to create an Inter-Switch Link.

“F_Port”: A port to which non-loop N_Ports are attached to a fabric and does not include FL_ports.

“Fibre channel ANSI Standard”: The standard (incorporated herein by reference in its entirety) describes the physical interface, transmission and signaling protocol of a high performance serial link for support of other high level protocols associated with IPI, SCSI, IP, ATM and others.

“FC-1”: Fibre channel transmission protocol, which includes serial encoding, decoding and error control.

“FC-2”: Fibre channel signaling protocol that includes frame structure and byte sequences.

“FC-3”: Defines a set of fibre channel services that are common across plural ports of a node.

“FC-4”: Provides mapping between lower levels of fibre channel, IPI and SCSI command sets, HIPPI data framing, IP and other upper level protocols.

“Fabric”: The structure or organization of a group of switches, target and host devices (NL_Port, N_ports etc.).

“Fabric Topology”: This is a topology where a device is directly attached to a fibre channel fabric that uses destination identifiers embedded in frame headers to route frames through a fibre channel fabric to a desired destination.

“FL_Port”: A L_Port that is able to perform the function of a F_Port, attached via a link to one or more NL_Ports in an Arbitrated Loop topology.

“Inter-Switch Link”: A Link directly connecting the E_port of one switch to the E_port of another switch.

Port: A general reference to N. Sub.--Port or F. Sub.--Port.

“L_Port”: A port that contains Arbitrated Loop functions associated with the Arbitrated Loop topology.

“N-Port”: A direct fabric attached port.

“NL_Port”: A L_Port that can perform the function of a N_Port.

“SOF”: Start of Frame

“Switch”: A fabric element conforming to the Fibre Channel Switch standards.

Fibre Channel System:

To facilitate an understanding of the preferred embodiment, the general architecture and operation of a fibre channel system will be described. The specific architecture and operation of the preferred embodiment will then be described with reference to the general architecture of the fibre channel system.

FIG. 1A is a block diagram of a fibre channel system 100 implementing the methods and systems in accordance with the adaptive aspects of the present invention. System 100 includes plural devices that are interconnected. Each device includes one or more ports, classified as node ports (N_Ports), fabric ports (F_Ports), and expansion ports (E_Ports). Node ports may be located in a node device, e.g. server 103, disk array 105 and storage device 104. Fabric ports are located in fabric devices such as switch 101 and 102. Arbitrated loop 106 may be operationally coupled to switch 101 using arbitrated loop ports (FL_Ports).

The devices of FIG. 1A are operationally coupled via “links” or “paths”. A path may be established between two N_ports, e.g. between server 103 and storage 104. A packet-switched path may be established using multiple links, e.g. an N-Port in server 103 may establish a path with disk array 105 through switch 102.

Fabric Switch Element

FIG. 1B is a block diagram of a 20-port ASIC fabric element according to one aspect of the present invention. FIG. 1B provides the general architecture of a 20-channel switch chassis using the 20-port fabric element. Fabric element includes ASIC 20 with non-blocking fibre channel class 2 (connectionless, acknowledged) and class 3 (connectionless, unacknowledged) service between any ports. It is noteworthy that ASIC 20 may also be designed for class 1 (connection-oriented) service, within the scope and operation of the present invention as described herein.

The fabric element of the present invention is presently implemented as a single CMOS ASIC, and for this reason the term “fabric element” and ASIC are used interchangeably to refer to the preferred embodiments in this specification. Although FIG. 1B shows 20 ports, the present invention is not limited to any particular number of ports.

ASIC 20 has 20 ports numbered in FIG. 1B as GL0 through GL19. These ports are generic to common Fibre Channel port types, for example, F_Port, FL_Port and E-Port. In other words, depending upon what it is attached to, each GL port can function as any type of port. Also, the GL port may function as a special port useful in fabric element linking, as described below.

For illustration purposes only, all GL ports are drawn on the same side of ASIC 20 in FIG. 1B. However, the ports may be located on both sides of ASIC 20 as shown in other figures. This does not imply any difference in port or ASIC design. Actual physical layout of the ports will depend on the physical layout of the ASIC.

Each port GL0-GL19 has transmit and receive connections to switch crossbar 50. One connection is through receive buffer 52, which functions to receive and temporarily hold a frame during a routing operation. The other connection is through a transmit buffer 54.

Switch crossbar 50 includes a number of switch crossbars for handling specific types of data and data flow control information. For illustration purposes only, switch crossbar 50 is shown as a single crossbar. Switch crossbar 50 is a connectionless crossbar (packet switch) of known conventional design, sized to connect 21×21 paths. This is to accommodate 20 GL ports plus a port for connection to a fabric controller, which may be external to ASIC 20.

In the preferred embodiments of switch chassis described herein, the fabric controller is a firmware-programmed microprocessor, also referred to as the input/out processor (“IOP”). IOP 66 is shown in FIG. 1C as a part of a switch chassis utilizing one or more of ASIC 20. As seen in FIG. 1B, bi-directional connection to IOP 66 is routed through port 67, which connects internally to a control bus 60. Transmit buffer 56, receive buffer 58, control register 62 and Status register 64 connect to bus 60. Transmit buffer 56 and receive buffer 58 connect the internal connectionless switch crossbar 50 to IOP 66 so that it can source or sink frames.

Control register 62 receives and holds control information from IOP 66, so that IOP 66 can change characteristics or operating configuration of ASIC 20 by placing certain control words in register 62. IOP 66 can read status of ASIC 20 by monitoring various codes that are placed in status register 64 by monitoring circuits (not shown).

FIG. 1C shows a 20-channel switch chassis S2 using ASIC 20 and IOP 66. S2 will also include other elements, for example, a power supply (not shown). The 20 GL ports correspond to channel C0-C19. Each GL port has a serial/deserializer (SERDES) designated as S0-S19. Ideally, the SERDES functions are implemented on ASIC 20 for efficiency, but may alternatively be external to each GL port.

Each GL port has an optical-electric converter, designated as OE0-OE19 connected with its SERDES through serial lines, for providing fibre optic input/output connections, as is well known in the high performance switch design. The converters connect to switch channels C0-C19. It is noteworthy that the ports can connect through copper paths or other means instead of optical-electric converters.

FIG. 1D shows a block diagram of ASIC 20 with sixteen GL ports and four 10G (Gigabyte) port control modules designated as XG0-XG3 for four 10G ports designated as XGP0-XGP3. ASIC 20 include a control port 62A that is coupled to IOP 66 through a PCI connection 66A.

FIG. 1E-1/1E-2 (jointly referred to as FIG. 1E) show yet another block diagram of ASIC 20 with sixteen GL and four XG port control modules. Each GL port control module has a Receive port (RPORT) 69 with a receive buffer (RBUF) 69A and a transmit port 70 with a transmit buffer (TBUF) 70A, as described below in detail. GL and XG port control modules are coupled to physical media devices (“PMD”) 76 and 75 respectively.

Control port module 62A includes control buffers 62B and 62D for transmit and receive sides, respectively. Module 62A also includes a PCI interface module 62C that allows interface with IOP 66 via a PCI bus 66A.

XG_Port (for example 74B) includes RPORT 72 with RBUF 71 similar to RPORT 69 and RBUF 69A and a TBUF and TPORT similar to TBUF 70A and TPORT 70. Protocol module 73 interfaces with SERDES to handle protocol based functionality.

GL Port:

FIGS. 3A-3B (referred to as FIG. 3) show a detailed block diagram of a GL port as used in ASIC 20. GL port 300 is shown in three segments, namely, receive segment (RPORT) 310, transmit segment (TPORT) 312 and common segment 311.

Receive Segment of GL Port:

Frames enter through link 301 and SERDES 302 converts data into 10-bit parallel data to fibre channel characters, which are then sent to receive pipe (“Rpipe” may also be referred to as “Rpipe1” or “Rpipe2”) 303A via a de-multiplexer (DEMUX) 303. Rpipe 303A includes, parity module 305 and decoder 304. Decoder 304 decodes 10B data to 8B and parity module 305 adds a parity bit. Rpipe 303A also performs various Fibre Channel standard functions such as detecting a start of frame (SOF), end-of frame (EOF), Idles, R_RDYs (fibre channel standard primitive) and the like, which are not described since they are standard functions.

Rpipe 303A connects to smoothing FIFO (SMF) module 306 that performs smoothing functions to accommodate clock frequency variations between remote transmitting and local receiving devices.

Frames received by RPORT 310 are stored in receive buffer (RBUF) 69A, (except for certain Fibre Channel Arbitrated Loop (AL) frames). Path 309 shows the frame entry path, and all frames entering path 309 are written to RBUF 69A as opposed to the AL path 308.

Cyclic redundancy code (CRC) module 313 further processes frames that enter GL port 300 by checking CRC and processing errors according to FC_PH rules. The frames are subsequently passed to RBUF 69A where they are steered to an appropriate output link. RBUF 69A is a link receive buffer and can hold multiple frames.

Reading from and writing to RBUF 69A are controlled by RBUF read control logic (“RRD”) 319 and RBUF write control logic (“RWT”) 307, respectively. RWT 307 specifies which empty RBUF 69A slot will be written into when a frame arrives through the data link via multiplexer 313B, CRC generate module 313A and EF (external proprietary format) module 314. EF module 314 encodes proprietary (i.e. non-standard) format frames to standard Fibre Channel 8B codes. Mux 313B receives input from Rx Spoof module 314A, which encodes frames to a proprietary format (if enabled). RWT 307 controls RBUF 69A write addresses and provide the slot number to tag writer (“TWT”) 317.

RRD 319 processes frame transfer requests from RBUF 69A. Frames may be read out in any order and multiple destinations may get copies of the frames.

Steering state machine (SSM) 316 receives frames and determines the destination for forwarding the frame. SSM 316 produces a destination mask, where there is one bit for each destination. Any bit set to a certain value, for example, 1, specifies a legal destination, and there can be multiple bits set, if there are multiple destinations for the same frame (multicast or broadcast).

SSM 316 makes this determination using information from alias cache 315, steering registers 316A, control register 326 values and frame contents. IOP 66 writes all tables so that correct exit path is selected for the intended destination port addresses.

The destination mask from SSM 316 is sent to TWT 317 and a RBUF tag register (RTAG) 318. TWT 317 writes tags to all destinations specified in the destination mask from SSM 316. Each tag identifies its corresponding frame by containing an RBUF 69A slot number where the frame resides, and an indication that the tag is valid.

Each slot in RBUF 69A has an associated set of tags, which are used to control the availability of the slot. The primary tags are a copy of the destination mask generated by SSM 316. As each destination receives a copy of the frame, the destination mask in RTAG 318 is cleared. When all the mask bits are cleared, it indicates that all destinations have received a copy of the frame and that the corresponding frame slot in RBUF 69A is empty and available for a new frame.

RTAG 318 also has frame content information that is passed to a requesting destination to pre-condition the destination for the frame transfer. These tags are transferred to the destination via a read multiplexer (RMUX) (not shown).

Transmit Segment of GL Port:

Transmit segment (“TPORT” 312 performs various transmit functions. Transmit tag register (TTAG) 330 provides a list of all frames that are to be transmitted. Tag Writer 317 or common segment 311 write TTAG 330 information. The frames are provided to arbitration module (“transmit arbiter” (“TARB”)) 331, which is then free to choose which source to process and which frame from that source to be processed next.

TTAG 330 includes a collection of buffers (for example, buffers based on a first-in first out (“FIFO”) scheme) for each frame source. TTAG 330 writes a tag for a source and TARB 331 then reads the tag. For any given source, there are as many entries in TTAG 330 as there are credits in RBUF 69A.

TARB 331 is activated anytime there are one or more valid frame tags in TTAG 330. TARB 331 preconditions its controls for a frame and then waits for the frame to be written into TBUF 70A. After the transfer is complete, TARB 331 may request another frame from the same source or choose to service another source.

TBUF 70A is the path to the link transmitter. Typically, frames don't land in TBUF 70A in their entirety. Mostly, frames simply pass through TBUF 70A to reach output pins, if there is a clear path.

Switch Mux 332 is also provided to receive output from crossbar 50. Switch Mux 332 receives input from plural RBUFs (shown as RBUF 00 to RBUF 19), and input from CPORT 62A shown as CBUF 1 frame/status. TARB 331 determines the frame source that is selected and the selected source provides the appropriate slot number. The output from Switch Mux 332 is sent to ALUT 323 for S_ID spoofing and the result is fed into TBUF Tags 333.

TMUX (“TxMUX”) 339 chooses which data path to connect to the transmitter. The sources are: primitive sequences specified by IOP 66 via control registers 326 (shown as primitive 339A), and signals as specified by Transmit state machine (“TSM”) 346, frames following the loop path, or steered frames exiting the fabric via TBUF 70A.

TSM 346 chooses the data to be sent to the link transmitter, and enforces all fibre Channel rules for transmission. TSM 346 receives requests to transmit from loop state machine 320, TBUF 70A (shown as TARB request 346A) and from various other IOP 66 functions via control registers 326 (shown as IBUF Request 345A). TSM 346 also handles all credit management functions, so that Fibre Channel connectionless frames are transmitted only when there is link credit to do so.

Loop state machine (“LPSM”) 320 controls transmit and receive functions when GL_Port is in a loop mode. LPSM 320 operates to support loop functions as specified by FC-AL-2.

IOP buffer (“IBUF”) 345 provides IOP 66 the means for transmitting frames for special purposes.

Frame multiplexer (“Frame Mux” or “Mux”) 336 chooses the frame source, while logic (TX spoof 334) converts D_ID and S_ID from public to private addresses. Mux 336 receives input from Tx Spoof module 334, TBUF tags 333, and Mux 335 to select a frame source for transmission.

EF (external proprietary format) module 338 encodes proprietary (i.e. non-standard) format frames to standard Fibre Channel 8B codes and CRC module 337 generates CRC data for the outgoing frames.

Modules 340-343 put a selected transmission source into proper format for transmission on an output link 344. Parity 340 checks for parity errors, when frames are encoded from 8B to 10B by encoder 341, marking frames “invalid”, according to Fibre Channel rules, if there was a parity error. Phase FIFO 342A receives frames from encode module 341 and the frame is selected by Mux 342 and passed to SERDES 343. SERDES 343 converts parallel transmission data to serial before passing the data to the link media. SERDES 343 may be internal or external to ASIC 20.

Common Segment of GL Port:

As discussed above, ASIC 20 include common segment 311 comprising of various modules. LPSM 320 has been described above and controls the general behavior of TPORT 312 and RPORT 310.

A loop look up table (“LLUT”) 322 and an address look up table (“ALUT”) 323 is used for private loop proxy addressing and hard zoning managed by firmware.

Common segment 311 also includes control register 326 that controls bits associated with a GL_Port, status register 324 that contains status bits that can be used to trigger interrupts, and interrupt mask register 325 that contains masks to determine the status bits that will generate an interrupt to IOP 66. Common segment 311 also includes AL control and status register 328 and statistics register 327 that provide accounting information for FC management information base (“MIB”).

Output from status register 324 may be used to generate a Fp Peek function. This allows a status register 324 bit to be viewed and sent to the CPORT.

Output from control register 326, statistics register 327 and register 328 (as well as 328A for an X_Port, shown in FIG. 4) is sent to Mux 329 that generates an output signal (FP Port Reg Out).

Output from Interrupt register 325 and status register 324 is sent to logic 335 to generate a port interrupt signal (FP Port Interrupt).

BIST module 321 is used for conducting embedded memory testing.

XG Port

FIGS. 4A-4B (referred to as FIG. 4) show a block diagram of a 10 G Fibre Channel port control module (XG FPORT) 400 used in ASIC 20. Various components of XG FPORT 400 are similar to GL port control module 300 that are described above. For example, RPORT 310 and 310A, Common Port 311 and 311A, and TPORT 312 and 312A have common modules as shown in FIGS. 3 and 4 with similar functionality.

RPORT 310A can receive frames from links (or lanes) 301A-301D and transmit frames to lanes 344A-344D. Each link has a SERDES (302A-302D), a de-skew module, a decode module (303B-303E) and parity module (304A-304D). Each lane also has a smoothing FIFO (SMF) module 305A-305D that performs smoothing functions to accommodate clock frequency variations. Parity errors are checked by module 403, while CRC errors are checked by module 404.

RPORT 310A uses a virtual lane (“VL”) cache 402 that stores plural vector values that are used for virtual lane assignment. In one aspect of the present invention, VL Cache 402 may have 32 entries and two vectors per entry. IOP 66 is able to read or write VL cache 402 entries during frame traffic. State machine 401 controls credit that is received. On the transmit side, credit state machine 347 controls frame transmission based on credit availability. State machine 347 interfaces with credit counters 328A.

Also on the transmit side, modules 340-343 are used for each lane 344A-344D, i.e., each lane can have its own module 340-343. Parity module 340 checks for parity errors and encode module 341 encodes 8-bit data to 10 bit data. Mux 342B sends the 10-bit data to a smoothing (“TxSMF”) module 342 that handles clock variation on the transmit side. SERDES 343 then sends the data out to the link.

The Request Abort Feature:

To reduce dead time between transmitted frames, a “request-abort” (also referred to as “RA”) feature is used in RBUF 69A. The RA feature allows TBUF 70A to request a frame from RBUF 69A before TBUF 70A completes the status check on a frame. If the status check is good, then RBUF 69A continues frame transmission. If the status check fails, then TBUF 70A aborts a current request and re-arbitrates, and RBUF 69A aborts the current frame transmission that was requested by TBUF 70A.

When RBUF 69A gets a request from a Transmit Port (TBUF70A), it sets a “read-active” bit that identifies the memory requested and the port that requested it. Upon receipt of a request-abort, RBUF 69A clear the bit. This will clear a read mask valid bit, which will cause the frame being transmitted to the particular Transmit Port to become invalid. If the Transmit Port has received any valid data before this action takes place, then the Transmit Port discards any received valid data.

For a multicast frame, the above action is the only action that takes place, as all other non-aborted requests for the same slot are honored. However, if RBUF 69A detects that this is the only transmission from that slot, then RBUF 69A clears the read window, the read address counter controlling that slot and the frame valid bit (signal).

It is noteworthy that RBUF 69A does not clear the active slot or the destination mask pointing to the aborting Transmit Port. This allows RBUF 69A to hold the slot for that Transmit Port and allows that Transmit Port to re-request the slot at a later time. Hence, a Transmit port may request, then abort a slot as many times as necessary until the status check for that slot passes.

Firmware for ASIC 20 enables or disables the “request-abort” feature. When enabled, TARB 331 is in a mode where frame transfer requests to RBUF 69A are activated earlier. The earlier activation of these requests starts frame transfer from RBUF 69A to TBUF 70A to occur earlier. These earlier transfers reduce dead time (“Idles”) between transmitted frames. The early transfer requests are activated before all information about the transfer is known. If information is obtained later that this requested transfer should not occur, it is aborted.

Conditions for Sending Request-Abort:

As stated above, TBUF 70A completes status check on the frames. TBUF 70A looks at several fields in the frame status field, in order to determine whether to abort the requested transfer. Some of the fields that can trigger aborts are as follows:

The lack of the “DEST” bit in the status field indicates that the frame is no longer in RBUF 69A. Therefore, any early request for a non-existent frame is aborted. A “request-abort” is issued and TARB 331 then selects a different source port, or different frame from the same source to attempt another transfer.

The lack of a “CUT” bit in the frame status indicates that not enough of the frame has landed to transfer the frame properly. A “request abort” is issued and TARB 331 selects another frame to transfer.

The “VL_ID” field in the frame status is used to determine if the virtual lane assigned to the frame in the RBUF 69A has credit. If there is no credit for the frame, then the transfer to TBUF 70A does not happen. Again, a “request-abort” is issued and TARB 331 selects another frame to transfer.

There are other conditions not associated with frame status that can trigger the activation of a “request-abort”. Some of these conditions are as follows:

A request-abort is issued if an early request is made without TBUF 70A having enough space, since space is needed for a frame in TBUF 70A before the next frame can be brought in. The early request to RBUF 69A is activated before TBUF 70A can predict if it has or will have space. In a later clock period, when TBUF 70A knows that it does not have space, then the request-abort is issued. If a previous frame read from TBUF 70A was delayed, the early request to the RBUF 69A is aborted.

Transmission of numerous “R_RDY's” or “VC_RDYs” can also delay the read of the previous frame in TBUF 70A. This can also trigger a “request-abort” command/signal.

If a preference frame tag is received, then TARB 331 cannot prevent the reordering of frame tags. In this case a non-preference tag that has been selected by TARB 331 will have to be selected again at a later time. Hence, any early (before the preference tag is received) frame transfer requests to RBUF 69A for a non-preference frame will be issued a “request-abort”.

Firmware can also interrupt a early frame transfer request to RBUF 69A. If this interrupt occurs, a “request-abort” is issued. Firmware can set a control signal (via control register 326) that halts frame flow. Firmware can also activate a TTAG 330 Flush state for a different source port, which blocks TTAG 330 valid for a source port, which has been requested.

FIG. 2 shows a process flow diagram for using an early frame transfer request, according to one aspect of the present invention.

In step S200, TBUF 70A sends an “early” frame transfer request. TBUF 70A can send this request even before it has completed checking frame status.

In step S201, RBUF 69A activates early frame transfer.

In step S202, a request for frames is received from TBUF 70A and RBUF 69A sets a “read-active” bit, in step S203.

In step S204, the process determines if any conditions are met for sending a “request-abort”. Some of those conditions have been described above.

In step S205, the process continues to transfer frames if the conditions are not met.

If the conditions are met, then in step S206, a “request-abort” signal is sent to RBUF 69A where the “read-active” bit is cleared (in step S207) and TARB 331 selects a different source port.

In one aspect of the present invention, because frames can be transferred early, it prevents dead time between transmitted frames, and hence improves overall efficiency and bandwidth.

Although the present invention has been described with reference to specific embodiments, these embodiments are illustrative only and not limiting. Many other applications and embodiments of the present invention will be apparent in light of this disclosure and the following claims.

Claims

1. A method for routing fibre channel frames using a fibre channel switch element having a plurality of ports, where each port includes a receive segment for receiving fibre channel frames and a transmit segment for transmitting fibre channel frames; comprising: (a) requesting an early frame transfer of a fibre channel frame from a memory location of the receive segment of a fibre channel port to the transmit segment of the fibre channel port, before the transmit segment completes a status check, wherein the transmit segment sends a request to the receive segment for the early frame transfer;(b) activating an early frame transfer; wherein the early frame transfer is activated at the receive segment;(c) after completing the status check, determining if there is a need for aborting the early frame transfer request sent to the receive segment in step (a);wherein the transmit segment determines if there is a need for aborting the early frame transfer request and if there is a need, generates a request-abort command to abort the early frame transfer request and sends the request abort command to the receive segment; and(e) after aborting the early frame transfer, selecting another frame from a different source port while continuing to have the memory location in step (a) available for the transmit segment to re-request the frame transfer from the same memory location.

2. The method of claim 1, further comprising: transferring the fibre channel frame if there is no need to abort the early frame transfer request gene rated by the transmit segment.

3. The method of claim 1, wherein firmware executed by the fibre channel switch element enables a request-abort feature permitting the transmit segment to send the early frame transfer request and aborting the early frame transfer request if the status check fails.

4. The method of claim 1, wherein the request-abort command is generated if a frame's status field lacks a destination bit value.

5. The method of claim 1, wherein the request-abort command is generated if a frame's status indicates that not enough of the frame has arrived properly at the receive segment.

6. The method of claim 1, wherein the request abort command is generated if a frame's status information used to determine that credit is unavailable for the frame.

7. The method of claim 1, wherein the request abort command is generated if the transmit segment does not have sufficient space to hold the frame.

8. The method of claim 1, wherein a request-abort command is generated if a plurality of R_RDYs, a primitive indicating available credit at the receive segment of the port, are transmitted by the transmit segment to another port.

9. The method of claim 1, wherein the request abort command is generated by firmware and used by the fibre channel switch element.

10. A fibre channel switch element for routing fibre channel frames, comprising: a receive segment in a fibre channel port of the fibre channel switch element for receiving the fibre channel frames and a transmit segment that transmits the received fibre channel frames;wherein the transmit segment of the fibre channel port requests an early frame transfer of a fibre channel frame from a memory location of the receive segment of the fibre channel port to the transmit segment, before the transmit segment completes a status check; and in response to the earl; frame transfer request, the receive segment activates an early frame transfer; andwherein, after completing the status check, the transmit segment determines if there is a need for aborting the early frame transfer request; generates a request abort command to abort the early frame transfer request if there is a need for aborting the early frame transfer request and sends the request abort command to the receive segment; andwherein after the early frame transfer request is aborted, another frame from a different source port is selected while the receive segment continues to have the memory location available for the transmit segment to re-request the frame transfer from the same memory location.

11. The fibre channel switch element of claim 10, wherein the transmit segment transfers the fibre channel frame if there is no need to abort the early frame transfer request.

12. The fibre channel switch element of claim 10, wherein firmware executed by the fibre channel switch element enables a request-abort feature permitting the transmit segment to send the early frame transfer request and aborting the early frame transfer request if the status check fails.

13. The fibre channel switch element of claim 10, wherein the request abort command is generated if the frame's status field lacks a destination bit value.

14. The fibre channel switch element of claim 10, wherein the request abort command is generated if the frame's status indicates that not enough of a frame has arrived properly.

15. The fibre channel switch element of claim 10, wherein the request abort command is generated if the frame's status information used to determine that credit is unavailable for the frame.

16. The fibre channel switch element of claim 10, wherein the request abort command is generated if the transmit segment does not have sufficient space to hold the frame.

17. The fibre channel switch element of claim 10, wherein the request abort command is generated if a plurality of R_RDYs, a primitive indicating available credit at the receive segment of the port, are transmitted by the transmit segment to another port.

18. The fibre channel switch element of claim 10, wherein the request abort command is generated by firmware used by the fibre channel switch element.

19. A switch element, comprising: a receive segment of a port for receiving a frame; anda transmit segment of the port for transmitting a frame; andbefore the transmit segment completes a status check; the transmit segment sends a request for an early frame transfer to the receive segment to transfer the frame from a memory location of the receive segment to the transmit segment; and in response to the early frame transfer request, the receive segment activates an early frame transfer;wherein, after completing the status check, the transmit segment determines if there is a need for aborting the early frame transfer request; and if there is a need, generates a request to abort the early frame transfer request and sends the request to the receive segment so that the early frame transfer is aborted; andwherein after the early frame transfer is aborted the receive segment continues to have the memory location available for the transmit segment to re-request the frame transfer from the same memory location.

20. The switch element of claim 19, wherein the transmit segment generates a request-abort command to abort the early frame transfer request.

21. The switch element of claim 20; wherein the request-abort command to abort the early frame transfer is generated based on one or more of the following: (a) the frame's status field lacks a destination bit value; (b) the frame's status indicates that not enough of a frame has arrived properly; (c) the frame's status indicates that credit is unavailable for the frame; (d) if the transmit segment does not have sufficient space to hold the frame; (e) if a plurality of R_RDYs a primitive indicating available credit at the receive segment, are transmitted; and (f) if firmware of the switch element generates the request-abort command.

22. A method for a switch element having a plurality of ports, each port having a receive segment for receiving frames and a transmit segment for transmitting frames; comprising: a. before the transmit segment completes a status check, requesting an early frame transfer of a frame from a memory location of the receive segment of a port to the transmit segment of the port; wherein the transmit segment sends a request to the receive segment for the early frame transfer;b. activating an early frame transfer; wherein the early frame transfer is activated at the receive segment;c. after completing the status check, determining if there is a need for abortingthe early frame transfer request sent to the receive segment in step (a); wherein the transmit segment determines if there is a need for aborting the early frame transfer request and if there is a need, generates a request-abort command to abort the early frame transfer request and sends the request abort command to the receive segment; and(d) after aborting the early frame transfer, selecting another frame while continuing to have the memory location in step (a) available for the transmit segment to re-request transfer of the frame from the same memory location of step (a).

23. The method of claim 22, wherein the request-abort command to abort the early frame transfer is generated based on one or more of the following: (a) the frame's status field lacks a destination bit value; (b) the frame's status indicates that not enough of a frame has arrived properly; (c) the frame's status indicates that credit is unavailable for the frame: (d) if the transmit segment does not have sufficient spice to hold the frame; and (E) if firmware of the switch element generates the request-abort command.