# US 2010/0306420 A1 · Fast path scsi io

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0306420 A1
- Document ID: US20100306420A1
- Status: Published application
- Kind: A1
- Application number: 12/765,027
- Filed: 2010-04-22
- Published: 2010-12-02
- Earliest claimed: 2009-06-01
- Assignees: LSI Corporation
- Inventors: Stephen B. Johnson; Timothy E. Hoglund
- Web page: https://patentgrep.com/patent/US20100306420A1

## CPC

- G06F 13/28: using burst mode transfer, e.g. direct memory access {DMA}, cycle steal (G06F13/32 takes precedence)
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

A hardware automated IO path, comprising a message transport unit for transporting an IO request to a local memory via a DMA operation and determining a LMID for associating with a request descriptor of the IO request; a fastpath engine for validating the request descriptor and creating a fastpath descriptor based on the request descriptor; a data access module for performing an IO operation based on the fastpath descriptor and posting a completion message into the fastpath completion queue upon a successful completion of the IO operation. The fastpath engine is further configured for: receiving the completion message, releasing the IO request stored in the local memory, and providing a reply message based on the completion message. The message transport unit is further configured for providing the reply message in response to the IO request.

## Claims

### Claim 1

A hardware automated input/output (IO) path, comprising:
a message transport unit configured for transporting an IO request to a local memory via a direct memory access (DMA) operation, the message transport unit further configured for determining a local message index descriptor (LMID) for associating with a request descriptor of the IO request;
a fastpath engine communicatively coupled with the message transport unit, the fastpath engine configured for validating the request descriptor and creating a fastpath descriptor based on the request descriptor, the fastpath engine further configured for posting the fastpath descriptor into a fastpath descriptor control queue;
a data access module communicatively coupled with the fastpath descriptor control queue and a fastpath completion queue, the data access module configured for performing an IO operation based on the fastpath descriptor, the data access module further configured for posting a completion message into the fastpath completion queue upon a successful completion of the IO operation;
said fastpath engine further configured for: receiving the completion message from the fastpath completion queue, releasing the IO request stored in the local memory, and providing a reply message based on the completion message; and
said message transport unit further configured for providing the reply message in response to the IO request;
wherein each of said message transport unit, said fastpath engine and said data access module are implemented as a state machine realized utilizing an electronic circuit.

### Claim 2 (depends on 1)

The hardware automated IO path of claim 1, wherein the data access module further configured for redirecting the IO operation to another IO path in an occurrence of exception, the other IO path being different from the hardware automated IO path.

### Claim 3 (depends on 1)

The hardware automated IO path of claim 1, wherein said fastpath descriptor comprises:
a device handle for providing a reference to a physical target end device; and
the LMID associated with the request descriptor.

### Claim 4 (depends on 1)

The hardware automated IO path of claim 1, further comprising an IO context table communicatively coupled with said fastpath engine, wherein said fastpath engine further configured for:
upon validation of the request descriptor, creating an IO context record corresponding to the request descriptor and storing the IO context record in the IO context table; and
upon completion of the IO request, deleting the IO context record from the IO context table.

### Claim 5 (depends on 1)

The hardware automated IO path of claim 1, further comprising a fastpath device table communicatively coupled with said fastpath engine, the fastpath device table configured for storing a list of fastpath enabled devices, and said fastpath engine further configured for maintaining current state information associated with each of the list of fastpath enabled devices.

### Claim 6 (depends on 1)

The hardware automated IO path of claim 1, further comprising a hardware automated trace buffer configured for logging context information associated with the IO request.

### Claim 7 (depends on 1)

The hardware automated IO path of claim 1, further comprising an exception queue configured for storing a validation exception from the fastpath engine.

### Claim 8 (depends on 1)

The hardware automated IO path of claim 1, further comprising a hardware automated timer wheel configured for detecting an occurrence of a time out when handling the IO request.

### Claim 9 (depends on 1)

The hardware automated IO path of claim 1, wherein said messaging unit, said fastpath engine and said data access module are configured for supporting at least one of a Message Passing Interface (MPI) specification and an Intelligent Input/Output (I2O) specification.

### Claim 10 (depends on 1)

The hardware automated IO path of claim 1, wherein said data access module is configured for supporting at least one of: SAS, Fibre Channel, iSCSI, SATA, InfiniBand, FCoE and Flash memory protocol engines.

### Claim 11

A system for handling an input/output (IO) request, comprising:
a message transport unit configured for transporting the IO request to a local memory via a direct memory access (DMA) operation, the message transport unit further configured for determining a local message index descriptor (LMID) for associating with a request descriptor of the IO request;
a fastpath engine communicatively coupled with the message transport unit, the fastpath engine configured for validating the request descriptor and creating a fastpath descriptor based on the request descriptor, the fastpath engine further configured for posting the fastpath descriptor into a fastpath descriptor control queue;
a data access module communicatively coupled with the fastpath descriptor control queue and a fastpath completion queue, the data access module configured for performing an IO operation based on the fastpath descriptor, the data access module further configured for posting a completion message into the fastpath completion queue upon a successful completion of the IO operation;
said fastpath engine further configured for: receiving the completion message from the fastpath completion queue, releasing the IO request stored in the local memory, and providing a reply message based on the completion message; and
said message transport unit further configured for providing the reply message in response to the IO request.

### Claim 12 (depends on 11)

The system of claim 11, wherein the data access module further configured for redirecting the IO operation to another IO path in an occurrence of exception.

### Claim 14 (depends on 11)

The system of claim 11, further comprising an IO context table communicatively coupled with said fastpath engine, wherein said fastpath engine further configured for:
upon validation of the request descriptor, creating an IO context record corresponding to the request descriptor and storing the IO context record in the IO context table; and
upon completion of the IO request, deleting the IO context record from the IO context table.

### Claim 15 (depends on 11)

The system of claim 11, further comprising a fastpath device table communicatively coupled with said fastpath engine, the fastpath device table configured for storing a list of fastpath enabled devices, and said fastpath engine further configured for maintaining current state information associated with each of the list of fastpath enabled devices.

### Claim 16 (depends on 11)

The system of claim 11, further comprising a hardware automated trace buffer configured for logging context information associated with the IO request.

### Claim 18 (depends on 11)

The system of claim 11, further comprising a hardware automated timer wheel configured for detecting an occurrence of a time out when handling the IO request.

### Claim 19

A method for handling an IO request, comprising:
transporting the IO request to a local memory via a direct memory access (DMA) operation;
determining a local message index descriptor (LMID) for associating with a request descriptor of the IO request;
creating a fastpath descriptor based on the request descriptor;
performing an IO operation according to the fastpath descriptor;
providing a completion message upon a successful completion of the IO operation;
releasing the IO request stored in the local memory; and
providing a reply message in response to the IO request, the reply message being provided based on the completion message.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
redirecting the IO operation to another IO path in an occurrence of exception.
