# US 2012/0254484 A1 · Dynamic reassignment for i/o transfer processing

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

- Number: US 2012/0254484 A1
- Document ID: US20120254484A1
- Status: Published application
- Kind: A1
- Application number: 13/075,959
- Filed: 2011-03-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-30
- Assignees: Intel Corporation
- Inventors: JISOO YANG; DAVE B. MINTURN
- Web page: https://patentgrep.com/patent/US20120254484A1

## CPC

- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 2209/548: Queue
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In some embodiments of the present invention, host systems and/or devices are made to be capable of employing asynchronous or synchronous modes. For example, for storage devices capable of finishing I/O requests in a sufficiently small amount of time, e.g., a few microseconds, host system software may perform the storage I/O request synchronously by polling for a completion.

## Claims

### Claim 1

An apparatus, comprising:
a storage drive having a storage drive controller to issue a reassignment ticket to break a CPU polling loop to transition a transfer request to an asynchronous process.

### Claim 2 (depends on 1)

The apparatus of claim 1, in which the reassignment ticket is implemented through a completion queue.

### Claim 3 (depends on 2)

The apparatus of claim 2, in which the reassignment ticket includes a delivery destination of a completion notice for the completion queue.

### Claim 4 (depends on 1)

The apparatus of claim 1, in which the controller determines if the transfer request process should be changed to the asynchronous mode.

### Claim 5 (depends on 4)

The apparatus of claim 4, in which the controller determines if the transfer request process should change based on a time-out event for a transfer task associated with the transfer request.

### Claim 6 (depends on 1)

The apparatus of claim 1, comprising a host CPU to execute a storage driver to initiate a submission queue in a synchronous mode resulting in the polling loop.

### Claim 7 (depends on 6)

The apparatus of claim 6, in which the storage driver is to determine if a task request should be processed in a synchronous or an asynchronous mode.

### Claim 8

A computing system, comprising
a storage device to process I/O requests via an interface comprising queues; and
a CPU to execute a storage driver to submit the I/O requests through the interface, the CPU to switch its mode of operation for an outstanding I/O request from polling to interrupt-driven at runtime in response to a notice in a completion queue.

### Claim 9 (depends on 8)

The computing system of claim 8, in which the storage driver facilitates both polling-based and interrupt-based I/O request completion notifications.

### Claim 10 (depends on 8)

The computing system of claim 8, in which the storage device is to notify the driver with a reassignment ticket when the device decides that a pending request should be completed on a different completion queue other than originally specified, thereby allowing the driver to switch its mode of operation to handle the completion of the request on the different queue.

### Claim 11 (depends on 8)

The system of claim 8, in which the host driver is to submit the I/O request in a submission queue and at least initially wait for the completion in a first completion queue.

### Claim 12 (depends on 11)

The computing system of claim 11, in which the first queue is associated with the submission queue.

### Claim 13 (depends on 12)

The computing system of claim 12, in which the storage driver waits for completion by polling the first completion queue.

### Claim 14 (depends on 11)

The computing system of claim 11, in which the driver is to change its mode of operation upon the receipt of a reassignment ticket from the storage device by waiting for completion on a different completion queue than the first completion queue.

### Claim 15

A memory storage apparatus, comprising:
a storage driver to submit I/O requests through an interface to a storage drive device, the storage driver to switch its mode of operation for an outstanding I/O request from polling to interrupt-driven at runtime if the I/O request results in a transaction of an excessive length.

### Claim 16 (depends on 15)

The storage apparatus of claim 15, in which the storage driver is to switch the operation mode in response to a notice in a completion queue.

### Claim 17 (depends on 15)

The storage apparatus of claim 15, in which the storage driver facilitates both polling-based and interrupt-based I/O request completion notifications.

### Claim 18 (depends on 15)

The storage apparatus of claim 15, in which the storage device is to notify the driver with a reassignment ticket when the device decides that a pending request should be completed on a different completion queue other than originally specified, thereby allowing the driver to switch its mode of operation to handle the completion of the request on the different queue.

### Claim 19 (depends on 15)

The storage apparatus of claim 15, in which the host driver is to submit the I/O request in a submission queue and at least initially wait for the completion in a first completion queue.
