# US 2010/0169570 A1 · Providing differentiated I/O services within a hardware storage controller

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

- Number: US 2010/0169570 A1
- Document ID: US20100169570A1
- Status: Published application
- Kind: A1
- Application number: 12/319,012
- Filed: 2008-12-31
- Published: 2010-07-01
- Earliest claimed: 2008-12-31
- Inventors: Michael Mesnier; David Koufaty
- Web page: https://patentgrep.com/patent/US20100169570A1

## CPC

- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/0605: {by facilitating the interaction with a user or administrator}
- G06F 3/061: {Improving I/O performance}
- G06F 3/0644: {Management of space entities, e.g. partitions, extents, pools}
- G06F 3/0685: {Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A device, system, and method are disclosed. In one embodiment device includes routing logic that is capable of receiving an I/O storage request from an operating system. The I/O storage request includes an input/output (I/O) data type tag that specifies a type of I/O data to be stored with the I/O storage request. The routing logic is also capable of determining, based on the I/O data type tag, which of a number of storage pools to send the I/O storage request. Each storage pool has a certain level of associated service.

## Claims

### Claim 1

A storage controller device, comprising:
routing logic to
receive an I/O storage request from an operating system, the I/O storage request including an input/output (I/O) data type tag specifying a type of I/O data to be stored with the I/O storage request;
determine, based on the I/O data type tag, which storage pool of a plurality of storage pools to send the I/O storage request, wherein each of the plurality of storage pools comprises at least one level of service.

### Claim 2 (depends on 1)

The device of claim 1, wherein the routing logic is further operable to:
identify each available storage pool; and
determine the level of service offered by each available storage pool.

### Claim 3 (depends on 2)

The device of claim 2, wherein the routing logic is further operable to:
determine the level of service desired for the I/O data type listed in the I/O data type tag; and
send the I/O storage request to a first storage pool of the plurality of storage pools, the first storage pool offering the determined level of service.

### Claim 4 (depends on 3)

The device of claim 3, wherein the storage controller device comprises a redundant array of independent disks (RAID) controller.

### Claim 5 (depends on 4)

The device of claim 4, wherein the I/O storage request further comprises an operating system generated logical block request.

### Claim 6 (depends on 5)

The device of claim 5, wherein the routing logic is further operable to:
dynamically map the logical block request to a physical storage device within one of the plurality of storage pools, the physical storage device offering the desired level of service corresponding to the I/O data type tag in the I/O storage request.

### Claim 7 (depends on 1)

The device of claim 1, wherein the routing logic is further operable to:
receive a first I/O storage request specifying a first type of I/O data;
receive a second I/O storage request specifying a second type of I/O data, wherein the first type of I/O data desires a higher quality of service than the second type of I/O data;
send the first I/O storage request to a first I/O storage pool; and
send the second I/O storage request to a second I/O storage pool, wherein the first I/O storage pool provides higher quality of I/O storage service than the second I/O storage pool.

### Claim 8 (depends on 1)

The system of claim 1, wherein the I/O data type tag specifies data of one of file data, directory data, and metadata.

### Claim 9 (depends on 1)

The system of claim 1, wherein the routing logic is further operable to:
receive a routing policy for each type of data to store; and
utilize the received routing policy to route each I/O storage request to at least one of the plurality of storage pools.

### Claim 10 (depends on 9)

The system of claim 9, wherein the routing logic is further operable to receive the routing policy in an out-of-band communication channel.

### Claim 11

A system, comprising:
a file system stored in a memory, the file system to provide an input/output (I/O) data type tag specifying a type of I/O data to store with an I/O storage request;
an operating system stored in the memory, the operating system to send the I/O storage request to a storage controller, the I/O storage request including the I/O data type tag as a field in the I/O storage request; and
the storage controller to:
receive the I/O storage request from the operating system;
determine, based on the I/O data type tag, which storage pool of a plurality of storage pools to send the I/O storage request, wherein each of the plurality of storage pools comprises at least one level of service.

### Claim 12 (depends on 11)

The system of claim 11, wherein the storage controller is further operable to:
identify each available storage pool; and
determine the level of service offered by each available storage pool.

### Claim 13 (depends on 12)

The system of claim 12, wherein the storage controller is further operable to:
determine the level of service desired for the I/O data type listed in the I/O data type tag; and
send the I/O storage request to a first storage pool of the plurality of storage pools, the first storage pool offering the determined level of service.

### Claim 14 (depends on 13)

The system of claim 13, wherein the storage controller comprises a redundant array of independent disks (RAID) controller.

### Claim 15 (depends on 14)

The system of claim 14, wherein the operating system is further operable to send the I/O storage request to the storage controller in the form of a logical block request.

### Claim 16 (depends on 15)

The system of claim 15, wherein the storage controller is further operable to:
dynamically map the logical block request to a physical storage device within one of the available storage pools, the physical storage device offering the desired level of service corresponding to the I/O data type tag in the I/O storage request.

### Claim 17 (depends on 11)

The system of claim 11, wherein the storage controller is further operable to:
receive a first I/O storage request specifying a first type of I/O data;
receive a second I/O storage request specifying a second type of I/O data, wherein the first type of I/O data desires a higher quality of service than the second type of I/O data;
send the first I/O storage request to a first I/O storage pool; and
send the second I/O storage request to a second I/O storage pool, wherein the first I/O storage pool provides higher quality of I/O storage service than the second I/O storage pool.

### Claim 18 (depends on 11)

The system of claim 11, wherein the I/O data type tag specifies data of one of file data, directory data, and metadata.

### Claim 19 (depends on 11)

The system of claim 11, wherein the storage controller is further operable to:
receive a routing policy for each type of data to store; and
utilize the received routing policy to route each I/O storage request to at least one of the plurality of storage pools.

### Claim 20 (depends on 19)

The system of claim 19, wherein the storage controller is further operable to receive the routing policy in an out-of-band communication channel.

### Claim 21

A method, comprising:
receiving an input/output (I/O) storage request, the I/O storage request including a tag specifying a type of I/O data to store;
determining, based on the I/O data type tag, which storage pool of a plurality of storage pools to send the I/O storage request, wherein each of the plurality of storage pools comprises a level of service.

### Claim 22 (depends on 21)

The method of claim 21, further comprising:
determining the level of service desired for the I/O data type; and
including a quality of service tag with the I/O storage request based on the determination.

### Claim 23 (depends on 22)

The method of claim 22, further comprising:
including the I/O data type tag in each logical disk request from an operating system block I/O layer.

### Claim 24 (depends on 22)

The method of claim 22, further comprising:
receiving a first I/O storage request specifying a first type of I/O data;
receiving a second I/O storage request specifying a second type of I/O data, wherein the first type of I/O data desires a higher quality of service than the second type of I/O data;
sending the first I/O storage request to a first I/O storage pool; and
sending the second I/O storage request to a second I/O storage pool, wherein the first I/O storage pool provides higher quality of I/O storage service than the second I/O storage pool.
