Device, system and method of managing a resource request

• US 7,958,510 B2
• Filed: 12/30/2005
• Issued: 06/07/2011
• Est. Priority Date: 12/30/2005
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Novakovsky, Larisa, Mandelblat, Julius, Mendelson, Abraham
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): KAWSAR, ABDULLAH AL
• Application Number:
  US11/321,643
• Publication Number:
  US 20070157208A1
• Time in Patent Office: 1,985 Days
• Field of Search: 718/1, 718/100, 718/101, 718/102, 718/103, 718/104, 718/105, 718/106, 718/107, 718/108, 710/22, 710/23, 710/36, 710/37, 710/39, 710/40, 710/200, 710/220, 710/240, 711100-113, 711150-152, 711167-169
• US Class Current: 718/104
• CPC Class Codes: G06F 2209/507 Low-level
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals

Abstract

Embodiments of the present invention provide a resource management mechanism to monitor the availability of resources, detect the cause of a rejection, distinguish between different types of rejections, and manage the different types accordingly. For example, a queue manager in accordance with embodiments of the invention may be able to classify rejected requests, for example, as either a “long reject” or a “short reject” based on the cause of the rejection and the amount of time the rejection conditions are expected to remain valid. A short reject request may be rescheduled in an appropriate service queue, while a long reject request may be suspended in a reject queue. Other features are described and claimed.

Claims

1. A computerized method comprising:

monitoring one or more rejection conditions for a request to access a resource;

classifying a rejection of the request as either a long reject or a short reject based one or more parameters relating to the one or more rejection conditions, wherein classifying a rejection comprises classifying a rejection as a short reject if said one or more rejection conditions include conditions dependent on an internal event and classifying a rejection as a long reject if said one or more rejection conditions include conditions dependent on an external resource;

suspending said request in a reject queue if the request is rejected and classified as a long reject, wherein data relating to the cause of the rejection and the resource to be accessed by said request is to be associated with the request in the reject queue; and

rescheduling said request in a service queue, associated with said resource, to be accessed if the request is rejected and classified as a short reject.

2. The method of claim 1, wherein classifying a rejection of said request based on said one or more parameters comprises classifying based on a cause of the rejection and the amount of time said one or more rejection conditions are expected to remain valid.

3. The method of claim 1, wherein classifying a rejection comprises predicting the amount of time said one or more rejection conditions are expected to remain valid based on the cause of the rejection.

4. The method of claim 1, wherein monitoring said one or more rejection conditions comprises querying one or more resources to determine availability of said one or more resources.

5. The method of claim 1, comprising sending a release event to release said request from said reject queue based on said data and a signal from the resource to be accessed indicating that the resource is available to service the request.

6. The method of claim 1, comprising sending a release event to release said request from said reject queue based on one or more parameters indicative of a change in said one or more rejection conditions.

7. An apparatus comprising:

a resource management hardware mechanism to monitor one or more rejection conditions for a request to access a resource and to classify a rejection of the request as either a long reject or a short reject based one or more parameters relating to the one or more rejection conditions, wherein a rejection is to be classified as a short reject if said one or more rejection conditions include conditions dependent on an internal event and to be classified as a long reject if said one or more rejection conditions include conditions dependent on an external resource,

wherein said request is to be suspended in a reject queue if the request is rejected and classified as a long reject, wherein data relating to the cause of the rejection and the resource to be accessed by said request is to be associated with the request in the reject queue and wherein said request is to be rescheduled in a service queue, associated with said resource, to be accessed if the request is rejected and classified as a short reject.

8. The apparatus of claim 7, wherein said resource management mechanism is to classify a rejection based on a cause of the rejection and the amount of time said one or more rejection conditions are expected to remain valid.

9. The apparatus of claim 7, wherein said resource management mechanism is to predict the amount of time said one or more rejection conditions are expected to remain valid based on the cause of the rejection.

10. The apparatus of claim 7, wherein said resource management mechanism is to query one or more resources to determine availability of said one or more resources.

11. The apparatus of claim 7, wherein said resource management mechanism is to associate with said request that is suspended data relating to the cause of the rejection and the resource to be accessed by said request.

12. The apparatus of claim 11, wherein said resource management mechanism is to release said request that is suspended based on said data and a signal from the resource to be accessed indicating that the resource is available to service the request.

13. The apparatus of claim 7, wherein said resource management mechanism is to release said request that is suspended based on one or more parameters indicative of a change in said one or more rejection conditions.

14. A system comprising:

a processor to monitor one or more rejection conditions for a request to access a resource and to classify a rejection of the request as either a long reject or a short reject based one or more parameters relating to the one or more rejection conditions, wherein a rejection is to be classified as a short reject if said one or more rejection conditions include conditions dependent on an internal event and to be classified as a long reject if said one or more rejection conditions include conditions dependent on an external resource; and

a memory to store one or more queues for management of the request according to whether the request is classified as a long reject or a short reject,

wherein said request is to be suspended in a reject queue if the request is rejected and classified as a long reject, wherein data relating to the cause of the rejection and the resource to be accessed by said request is to be associated with the request in the reject queue and wherein said request is to be rescheduled in a service queue, associated with said resource, to be accessed if the request is rejected and classified as a short reject.

15. The system of claim 14, wherein said processor is to associate with said request in the reject queue data relating to the cause of the rejection and the resource to be accessed by the request, and wherein said memory is to store the data associated with the request.

16. The system of claim 15, wherein said processor is to release said request from the reject queue based on one or more parameters indicative of a change in said one or more rejection conditions.

17. The system of claim 15, wherein said processor is to release said request from the reject queue based on said data and a signal from the resource to be accessed indicating that the resource is available to service the request.

18. The system of claim 14, wherein said processor is to query one or more resources to determine availability of said one or more resources.

19. The system of claim 14, wherein said processor is to classify a rejection based on a cause of the rejection and the amount of time said one or more rejection conditions are expected to remain valid.

20. The system of claim 14, wherein said processor is to predict the amount of time said one or more rejection conditions are expected to remain valid based on the cause of the rejection.