Fast cancellation of input-output requests

• US 8,671,231 B2
• Filed: 06/06/2011
• Issued: 03/11/2014
• Est. Priority Date: 06/06/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Aslot, Vishal Chittranjan, Hart, Brian W., Kalavakolanu, Anil, Yeung, Evelyn Tingmay
• Primary Examiner(s): Huson, Zachary K
• Application Number:
  US13/154,335
• Publication Number:
  US 20120311202A1
• Time in Patent Office: 1,009 Days
• Field of Search: None
• US Class Current: 710/55
• CPC Class Codes: G06F 13/387 for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system

Abstract

A method, system, and computer program product for fast cancellation of an I/O request in a data processing system are provided in the illustrative embodiments. A first component in a stack comprising a plurality of components determines whether a memory buffer associated with the I/O request is valid, the memory buffer being an addressable area in a memory in the data processing system. The first component, responsive to the memory buffer being valid, creates a first request data structure corresponding to the I/O request, wherein the first request data structure includes a reference to the memory buffer. The first component passes the first request data structure to a second component in the stack.

Claims

1. A method for fast cancellation of an input/output (I/O) request in a data processing system, the method comprising:

a first component, in a stack comprising a set of at least two components, determining whether a memory buffer associated with the I/O request is valid, the memory buffer being an addressable area in a memory in the data processing system, wherein the stack enables the I/O request to be passed using a series of passes between a subset of the set of components to reach a component in the set of components that can access data for an operation being requested in the I/O request, and wherein the memory buffer associated with the I/O request is valid when a reference to the memory buffer is usable to access a portion of the addressable area of the memory;

the first component, responsive to the memory buffer being valid, creating a first request data structure corresponding to the I/O request, wherein the first request data structure is distinct from the memory buffer and includes the reference to the memory buffer; and

the first component passing the first request data structure to a second component in the stack.

2. The method of claim 1, further comprising:

the first component determining whether to cancel the I/O request; and

the first component, responsive to determining to cancel the I/O request, invalidating the memory buffer, thereby performing the fast cancellation of the I/O request.

3. The method of claim 2, wherein the invalidating further comprises:

the first component sending a request to set a flag associated with the memory buffer to an “

invalid”

status, and wherein the determining whether the memory buffer is valid comprises determining whether the flag indicates a “

valid”

status for the associated memory buffer.

4. The method of claim 2, further comprising:

the first component retrying the I/O request without waiting for the second component to receive information about the fast cancellation of the I/O request.

5. The method of claim 4, further comprising:

the second component determining whether the memory buffer is valid; and

the second component, responsive to determining that the memory buffer is invalid, ending a processing of the I/O request at the second component.

6. The method of claim 2, further comprising:

the first component instructing the second component to invalidate the first request data structure at the second component.

7. The method of claim 1, further comprising:

the first component receiving a second request data structure corresponding to the I/O request from a third component, the second request data structure including a reference to the memory buffer, and wherein the reference in the first request data structure is a copy of the reference in the second request data structure.

8. The method of claim 7, wherein the third component is an application executing in the data processing system, and wherein the method further comprises:

the application originating the I/O request, wherein the application, the first component and the third component share access to the memory buffer.

9. The method of claim 1, further comprising:

a memory management program executing in the data processing system receiving an instruction from the first component to invalidate the memory buffer;

the memory management program changing a value of a flag associated with the memory buffer to indicate an “

invalid”

status of the memory buffer;

the memory management program determining whether the memory buffer can be freed for associating with a second I/O request; and

the memory management program, responsive to determining that the memory buffer can be freed, changing the value of the flag to indicate a “

free”

status of the memory buffer.

10. A computer program product comprising one or more computer-readable tangible storage devices and program instructions which are stored on the one or more storage devices and when executed by one or more processors perform the method of claim 1.

11. A computer system comprising one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices and program instructions which are stored on the one or more storage devices for execution by the one or more processors via the one or more memories and when executed by the one or more processors perform the method of claim 1.

12. A computer program product for fast cancellation of an input/output (I/O) request in a data processing system, the computer program product comprising one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices, the program instructions comprising:

first program instructions to determine, at a first component, in a stack comprising a set of at least two components, whether a memory buffer associated with the I/O request is valid, the memory buffer being an addressable area in a memory in the data processing system, wherein the stack enables the I/O request to be passed using a series of passes between subset of the set of components to reach a component in the set of components that can access data for an operation being requested in the I/O request, and wherein the memory buffer associated with the I/O request is valid when a reference to the memory buffer is usable to access a portion of the addressable area of the memory;

second program instructions to, responsive to the memory buffer being valid, create a first request data structure corresponding to the I/O request, wherein the first request data structure is distinct from the memory buffer and includes the reference to the memory buffer; and

third program instructions to pass the first request data structure to a second component in the stack.

13. The computer program product of claim 12, further comprising:

fourth program instructions to determine whether to cancel the I/O request; and

fifth program instructions to, responsive to determining to cancel the I/O request, invalidate the memory buffer, thereby performing the fast cancellation of the I/O request.

14. The computer program product of claim 13, wherein the fifth program instructions to invalidate further comprise:

sixth program instructions to send a request to set a flag associated with the memory buffer to an “

invalid”

status, and wherein the first program instructions to determine whether the memory buffer is valid comprise

seventh program instructions to determine whether the flag indicates a “

valid”

status for the associated memory buffer.

15. The computer program product of claim 13, further comprising:

sixth program instructions to retry the I/O request without waiting for the second component to receive information about the fast cancellation of the I/O request.

16. The computer program product of claim 15, further comprising:

seventh program instructions to, at the second component, determine whether the memory buffer is valid; and

eighth program instructions to, responsive to determining that the memory buffer is invalid, end a processing of the I/O request at the second component.

17. The computer program product of claim 13, further comprising:

sixth program instructions to instruct the second component to invalidate the first request data structure at the second component.

18. The computer program product of claim 12, further comprising:

fourth program instructions to receive a second request data structure corresponding to the I/O request from a third component, the second request data structure including a reference to the memory buffer, and wherein the reference in the first request data structure is a copy of the reference in the second request data structure.

19. The computer program product of claim 18, wherein the third component is an application executing in the data processing system, and wherein the program instructions further comprise:

fifth program instructions to originate the I/O request, wherein the application, the first component, and the third component share access to the memory buffer.

20. The computer program product of claim 12, further comprising:

fourth program instructions to, at a memory management program executing in the data processing system, receive an instruction from the first component to invalidate the memory buffer;

fifth program instructions to change a value of a flag associated with the memory buffer to indicate an “

invalid”

status of the memory buffer;

sixth program instructions to determine whether the memory buffer can be freed for associating with a second I/O request; and

seventh program instructions to, responsive to determining that the memory buffer can be freed, change the value of the flag to indicate a “

free”

status of the memory buffer.

21. The computer program product of claim 12, wherein the first, second, and third program instructions are stored in the one or more computer-readable tangible storage devices of a data processing system, and wherein the first, second, and third program instructions are transferred over a network from a remote data processing system.

22. The computer program product of claim 12, wherein the first, second, and third program instructions are stored in the one or more computer-readable tangible storage devices of a server data processing system, and wherein the first, second, and third program instructions are downloaded over a network to a remote data processing system for use in a computer-readable tangible storage device associated with the remote data processing system.

23. A computer system for fast cancellation of an input/output (I/O) request in a data processing system, the computer system comprising one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, the program instructions comprising:

first program instructions to determine, at a first component, in a stack comprising a set of at least two components, whether a memory buffer associated with the I/O request is valid, the memory buffer being an addressable area in a memory in the data processing system, wherein the stack enables the I/O request to be passed using a series of passes between a subset of the set of components to reach a component in the set of components that can access data for an operation being requested in the I/O request, and wherein the memory buffer associated with the I/O request is valid when a reference to the memory buffer is usable to access a portion of the addressable area of the memory;

second program instructions to, responsive to the memory buffer being valid, create a first request data structure corresponding to the I/O request, wherein the first request data structure is distinct from the memory buffer and includes the reference to the memory buffer; and

third program instructions to pass the first request data structure to a second component in the stack.

24. The computer system of claim 23, further comprising:

fourth program instructions to determine whether to cancel the I/O request; and

fifth program instructions to, responsive to determining to cancel the I/O request, invalidate the memory buffer, thereby performing the fast cancellation of the I/O request.

25. The computer system of claim 24, wherein the fifth program instructions to invalidate further comprise:

sixth program instructions to send a request to set a flag associated with the memory buffer to an “

invalid”

status, and wherein the first program instructions to determine whether the memory buffer is valid comprise seventh program instructions to determine whether the flag indicates a “

valid”

status for the associated memory buffer.