Method and system for I/O scheduler activations

• US 7,305,537 B1
• Filed: 03/01/2005
• Issued: 12/04/2007
• Est. Priority Date: 03/01/2005
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Bonwick, Jeffrey S., Moore, William H.
• Primary Examiner(s): Bragdon; Reginald
• Assistant Examiner(s): Namazi; Mehdi
• Application Number:
  US11/069,176
• Time in Patent Office: 1,008 Days
• Field of Search: None
• US Class Current: 711/167
• CPC Class Codes: G06F 3/0611 in relation to response time
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

A method for storing data, that includes receiving a request to store data in a storage pool, queuing the request in an Input/Output (I/O) queue, and issuing the request from the I/O queue upon receipt of a completion interrupt from the storage pool.

Claims

1. A method for storing data, comprising:

receiving a request to store data in a storage pool;

queuing the request in an Input/Output (I/O) queue;

issuing the request from the I/O queue;

receiving a completion interrupt associated with the request from the storage pool;

determining a number of subsequent requests to issue to the storage pool upon receipt of the completion interrupt, wherein determining the number of subsequent requests to issue to the storage pool comprises determining whether a pending queue has less than maximum pending requests;

issuing no subsequent requests to the storage pool if the pending queue does not have less than maximum pending requests; and

issuing the number of subsequent requests to the storage pool if there are requests in the I/O queue and the pending queue has less than maximum pending requests, wherein the number of requests issued to the storage pool does not result in the pending queue exceeding maximum pending requests.

2. The method of claim 1,

wherein queuing the request in the I/O queue is performed when the pending queue associated with the storage pool has more than minimum pending I/O requests, and

wherein a subsequent request is issued directly to the storage pool when the pending queue has less than the minimum pending requests.

3. The method of claim 1, wherein queuing the request comprises:

determining a quantized deadline for the request; and

placing the request in the I/O queue using the quantized deadline.

4. The method of claim 3, wherein the I/O queue comprises a plurality of buckets.

5. The method of claim 4, wherein the placing the request in the I/O queue comprises placing the request in one of the plurality of buckets corresponding to the quantized deadline.

6. The method of claim 5, wherein the request is ordered in the one of the plurality of buckets using a logical block address associated with the request.

7. The method of claim 1, wherein the I/O queue is an AVL tree and wherein queuing the request in the I/O queue comprises placing the request in the AVL tree with respect to a quantized deadline and a logical block address.

8. A system for storing data, comprising:

a storage pool configured to store data and issue a completion interrupt when a request to store data is processed by the storage pool;

an I/O queue configured to store the request; and

an I/O scheduler configured to;

issue the request from the I/O queue to the storage pool,

receive the completion interrupt from the storage pool,

determine a number of subsequent requests to issue to the storage pool upon receipt of the completion interrupt, wherein determining the number of subsequent requests comprises determining whether a pending queue has less than maximum pending requests,

issue no subsequent requests to the storage pool if the pending queue does not have less than maximum pending requests, and

issue the number of subsequent requests to the storage pool if there are requests in the I/O queue and the pending queue has less than maximum pending requests, wherein the number of subsequent requests issued to the storage pool does not result in the pending queue exceeding maximum pending requests.

9. The system of claim 8, further comprising:

a file system configured to receive the request, determine a quantized deadline of the request, and place the request in the I/O queue using the quantized deadline of the request and a logical block address of the request.

10. The system of claim 9, wherein

the request is placed in the I/O queue when the pending queue associated with the storage pool has more than minimum pending I/O requests, and

wherein a subsequent request is issued directly to the storage pool when the pending queue has less than the minimum pending requests.

11. The system of claim 8, wherein the I/O queue comprises a plurality of buckets.

12. The system method of claim 11, wherein a file system is configured to place the request in one of the plurality of buckets corresponding to the quantized deadline.

13. The system of claim 12, wherein the request is ordered in the one of the plurality of buckets using a logical block address associated with the request.

14. The system of claim 8, wherein the I/O queue is an AVL tree and wherein the request is placed in the AVL tree with respect to a quantized deadline and a logical block address.

15. A computer readable medium comprising software instructions for enabling a computer system under the control of a processor, to:

receive a request to store data in a storage pool;

queue the request in an Input/Output (I/O) queue;

issue the request from the I/O queue;

receive a completion interrupt associated with the request from the storage pool;

determine a number of subsequent requests to issue to the storage pool upon receipt of the completion interrupt, wherein software instructions for enabling the computer system to determine the number of subsequent requests comprises software instructions for enabling the computer system to determine whether a pending queue has less than maximum pending requests;

issue no subsequent requests to the storage pool if the pending queue does not have less than maximum pending requests; and

issue the number of subsequent requests to the storage pool if there are requests in the I/O queue and the pending queue has less than maximum pending requests, wherein the number of subsequent requests issued to the storage pool does not result in the pending queue exceeding maximum pending requests.

16. The computer readable medium of claim 15, further comprising software instructions for enabling the computer system to:

queue the request in the I/O queue when the pending queue associated with the storage pool has more than minimum pending I/O requests; and

issue a subsequent request directly to the storage pool when the pending queue has less than the minimum pending requests.

17. The computer readable medium of claim 15, wherein software instructions for enabling the computer system to queue the request comprises software instructions for enabling the computer system to:

determine a quantized deadline for the request; and

place the request in the I/O queue using the quantized deadline.

18. A plurality of nodes, comprising:

a storage pool configured to store data and issue a completion interrupt when a request to store data is processed by the storage pool;

an I/O queue configured to store the request; and

an I/O scheduler configured to;

issue the request from the I/O queue to the storage pool,

receive the completion interrupt from the storage pool,

determine a number of subsequent requests to issue to the storage pool upon receipt of the completion interrupt, wherein determining the number of requests comprises determining whether a pending queue has less than maximum pending requests,

issue no subsequent requests to the storage pool if the pending queue does not have less than maximum pending requests, and

issue the number of subsequent requests to the storage pool if there are requests in the I/O queue and the pending queue has less than maximum pending requests, wherein the number of subsequent requests issued to the storage pool does not result in the pending queue exceeding maximum pending requests,

wherein the storage pool is located on at least one of the plurality of nodes,

wherein the I/O queue is located on at least one of the plurality of nodes and

wherein the I/O scheduler is located at least one of the plurality of nodes.

19. The plurality of nodes of claim 18, further comprising:

a file system configured to receive the request, determine a quantized deadline of the request, and place the request in the I/O queue using the quantized deadline of the request and a logical block address of the request,

wherein the file system is located on at least one of the plurality of nodes.

20. The plurality of nodes of claim 19, wherein

the request is placed in the I/O queue when the pending queue associated with the storage pool has more than minimum pending I/O requests, and

wherein a subsequent request is issued directly to the storage pool when the pending queue has less than the minimum pending requests.