Dispenser determines responses to resource requests for a single respective one of consumable resource using resource management policy

• US 8,584,129 B1
• Filed: 02/20/2004
• Issued: 11/12/2013
• Est. Priority Date: 02/20/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Czajkowski, Grzegorz J., Skinner, Glenn C., Bryce, Ciaran J., Hahn, Stephen C., Soper, Peter James
• Primary Examiner(s): An, Meng
• Assistant Examiner(s): Arcos, Caroline H
• Application Number:
  US10/783,738
• Time in Patent Office: 3,553 Days
• Field of Search: 718/104, 718/100, 718/102, 726/1, 726/2, 726/6, 726/7
• US Class Current: 718/104
• CPC Class Codes: G06F 2209/5014 Reservation
• CPC Class Codes: G06F 2209/504 Resource capping
• CPC Class Codes: G06F 2209/508 Monitor
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Providing an intermediate isolate, referred to as a dispenser, to handle resource requests allows for monitoring and controlling of resource consumption separate from an operating system. Resources are characterized with a set of common attributes, separate from their specific implementation. The dispenser invokes computations that provide policy decisions corresponding to a resource request. The dispenser provides the requesting isolate a response based at least in part on the policy decisions. Separating management of resources from the operating system facilitates implementation of a dispenser in a safe language and management of a broad range of resources by the dispenser.

Claims

1. A system, comprising:

a processor; and

a memory storing program instructions executable by the processor, wherein the program instructions comprise computations that implement a plurality of dispensers, wherein each dispenser is configured to;

monitor resource requests for a single, respective one of a plurality of consumable execution resources, wherein consumable execution resources are measurable entities that computations can consume; and

determine responses to the resource requests for the single, respective resource, wherein determining a response to a resource request comprises determining whether to grant the resource request or determining an amount of the single, respective resource to grant;

wherein the program instructions comprising computations that implement each of the dispensers are distinct from program instructions comprising computations that implement the single, respective resource for which the dispenser monitors and determines responses to resource requests;

wherein the program instructions comprising computations that implement each of the dispensers are distinct from program instructions comprising computations that consume the single, respective resource for which the dispenser monitors and determines responses to resource requests;

wherein each of the dispensers is further configured to invoke one or more computations that impose one or more resource management policies in determining responses to resource requests for the single, respective resource for which the dispenser monitors and determines responses to resource requests; and

wherein each of the dispensers is further configured to receive one or more policy decisions with regard to the resource requests for the single, respective resource for which the dispenser monitors and determines responses to resource requests from the computations that impose the one or more resource management policies.

2. The system of claim 1, wherein each of the dispensers monitors and determines responses to requests based at least in part on a set of common attributes that characterize the single, respective resource for which the dispenser monitors and determines responses to resource requests with respect to consuming or releasing the single, respective resource.

3. The system of claim 2, wherein the set of common attributes is usable to characterize resources with respect to consuming or releasing the resources for a broad array of resource types.

4. The system of claim 2, wherein the common attributes include one or more of:

disposable, revocable, reservable, or bounded.

5. The system of claim 1, wherein each of the dispensers is an instance of a dispenser class defined by program instructions that are distinct from the program instructions comprising computations that implement the single, respective resource for which the dispenser monitors and determines responses to resource requests.

6. The system of claim 5, wherein each of the respective resources is implemented by one or more computations that include one or more of an operating environment, libraries, programming language runtime systems, middleware, or applications classes.

7. The system of claim 1, wherein a computation comprises a process, a thread, an operating environment, or an application.

8. The system of claim 1, wherein each of the dispensers is further configured to provide responses to requesters of the single, respective resource for which the dispenser monitors and determines responses to resource requests based at least in part on the one or more policy decisions received from the computations that impose the one or more resource management policies.

9. The system of claim 8, wherein each of the responses provided is also based at least in part on a merging of two or more policy decisions received from the computations that impose the one or more resource management policies.

10. The system of claim 9, wherein the merging of policy decisions is performed using a programmed method for merging the two or more policy decisions.

11. The system of claim 10, wherein each of the dispensers is further configured to invoke a set of one or more operations that implement the programmable method for merging the two or more policy decisions and that return a merged policy decision.

12. The system of claim 9, wherein the method for merging the two or more policy decisions comprises one or more of:

determining a smallest amount of the single, respective resource granted for one of the resource requests by corresponding policy decisions, determining a greatest amount of the single, respective resource granted by corresponding policy decisions, determining an average amount of the single, respective resource granted by the corresponding policy decisions, or selecting one of the policy decisions in accordance with applicable criteria.

13. The system of claim 1, wherein each of the dispensers is further configured to:

determine if one or more triggers are applicable to one of the resource requests for the single, respective resource for which the dispenser monitors and determines responses to resource requests;

resolve any triggers determined to be applicable to the one of the resource requests, wherein one or more policy decision actions are dependent on resolution of the triggers determined to be applicable to the one of the resource requests;

execute one or more of the one or more policy decision actions in accordance with the resolved triggers.

14. The system of claim 13, wherein each of the one or more triggers includes one or more operations to determine existence of a condition for executing a corresponding policy decision action that is dependent on resolution of the trigger.

15. The system of claim 13, wherein executing policy decision actions comprises invoking resource management policy computations that provide policy decisions.

16. The of claim 13, wherein the policy decision actions include pre-decision policy actions and post-decision policy actions.

17. The system of claim 1, wherein the resource comprises a consumable physical resource or a consumable logical resource.

18. The system of claim 17, wherein physical resources include processing time, memory, bus access time, and network bandwidth.

19. The system of claim 17, wherein logical resources include sockets, data structures, and application specific resources.

20. A method, comprising:

processing, by a dispenser, a plurality of requests to consume a given resource or to release a given resource that was being consumed based at least in part on a value of one or more common resource attributes as applied to the given resource, wherein said processing comprises monitoring the plurality of requests, wherein the given resource is a measurable entity that a computation can consume, wherein the common resource attributes are usable to characterize resources with respect to consuming or releasing the resources, wherein the common resource attributes are applicable to resources of the type of the given resource and to resources of types other than the type of the given resource, wherein values of the one or more common resource attributes as applied to the given resource are not unique values specific to the implementation of the given resource, and wherein the one or more common resource attributes comprise one or more of;

disposable, revocable, reservable, or bounded;

determining, by the dispenser, responses for the plurality of requests, wherein determining a response to a request to consume the given resource comprises determining whether to grant the request to consume the given resource or determining an amount of the given resource to grant, and wherein said determining is based at least in part on the values of the one or more common resource attributes as applied to the given resource; and

providing the responses to a set of one or more resource consuming computations from which the requests were received;

wherein the dispenser is one of a plurality of dispensers, each of which processes and determines responses to resource requests for a single, respective one of a plurality of consumable resources;

wherein implementation of the dispenser is distinct from implementation of the one or more resource consuming computations; and

wherein implementation of the dispenser is distinct from implementation of the given resource.

21. The method of claim 20, further comprising characterizing the given resource with the one or more common resource attributes.

22. The method of claim 20, wherein said processing comprises executing one or more policy decision actions that cause imposition of one or more resource management policies.

23. The method of claim 22, wherein the policy decision actions are executed in response to determining that one or more triggers applicable to the requests resolve to true.

24. The method of claim 22, wherein the policy decision actions include pre-decision actions and post-decision actions.

25. The method of claim 24, wherein the pre-decision policy actions include actions that invoke computations that impose resource management usage limit policies and wherein the post-decision policy actions include actions that invoke computations that impose resource management notification policies.

26. The method of claim 22, wherein the provided responses are based at least in part on policy decisions that are dependent on the imposed resource management policies.

27. The method of claim 26, wherein at least one of the provided responses is dependent on a plurality of the policy decisions, and wherein the at least one response grants a merged amount of the given resource, wherein the merged amount of the given resource is an amount of the given resource that is dependent on the plurality of policy decisions.

28. The method of claim 27, wherein the merged amount of the given resource comprises a smallest amount granted by the plurality of decisions, a greatest amount granted by the plurality of decisions, an average amount granted by the plurality of decisions, or an amount that satisfies programmable criteria applied to the plurality of decisions.

29. The method of claim 22, further comprising:

evaluating one or more triggers that are applicable to the requests; and

generating a set of one or more policy decision actions that correspond to those triggers of the one or more triggers that evaluate to true, wherein the set of policy decision actions include at least some of the executed policy decision actions.

30. The method of claim 22, wherein the resource management policies are defined independently of the implementation of the given resource, wherein each of the resource management policies is imposed by one or more computations, and wherein each of the computations is encapsulated and does not share computational state with other computations.

31. The method of claim 30, wherein the computations do not share objects with other computations.

32. The method of claim 20, wherein the given resource is implemented by one or more of a library, middleware, a programming language runtime system, an operating environment, or an application class.

33. The method of claim 20, embodied as a computer program product encoded in one or more non-transitory machine-readable storage media.

34. The method of claim 20, further comprising validating the requests for the given resource against reservations for the given resource.

35. A method, comprising:

monitoring, by a dispenser, one or more requests to consume a given resource or to release a given resource that was being consumed from one or more resource consuming isolates, wherein the given resource is a measurable entity that a resource consuming isolate can consume; and

governing, by the dispenser, a request to consume the given resource or to release the given resource, wherein the resource request is governed based at least in part on a value of one or more common resource attributes as applied to the given resource, wherein the common resource attributes are usable to characterize resources with respect to consuming or releasing the resources, wherein the common resource attributes are applicable to resources of the type of the given resource and to resources of types other than the type of the given resource, wherein values of the one or more common resource attributes as applied to the given resource are not unique values specific to the implementation of the given resource, and wherein governing a request to consume a given resource comprises determining whether to grant the request to consume the given resource or determining an amount of the given resource to grant; and

providing a response to the request to consume or release the given resource to the resource consuming isolate;

wherein said governing comprises;

invoking one or more computations that impose one or more resource management policies in determining responses to requests to consume the given resource or to release the given resource; and

receiving one or more policy decisions with regard to the request to consume the given resource or to release the given resource from the computations that impose the one or more resource management policies;

wherein the dispenser is one of a plurality of dispensers, each of which monitors and governs requests to consume or release a single, respective one of a plurality of consumable resources;

wherein implementation of the dispenser is distinct from implementation of the resource consuming isolate; and

wherein implementation of the dispenser is distinct from implementation of the given resource.

36. The method of claim 35, wherein the response is based at least in part on the one or more policy decisions, and wherein the one or more policy decisions are based on the one or more resource management policies.

37. The method of claim 36, wherein the one or more computations that impose the one or more resource management policies are policy imposing isolates.

38. The method of claim 35, wherein the response indicates a merged amount of the given resource, wherein the merged amount of the given resource is an amount of the given resource that is dependent on two or more of the one or more policy decisions.

39. The method of claim 38, wherein the merged amount of the given resource is generated by a set of one or more operations that programmatically merge the two or more of the one or more policy decisions.

40. The method of claim 38, wherein the merged amount of the given resource includes a smallest resource amount granted by the two or more of the one or more policy decisions, a largest amount granted by the two or more of the one or more policy decisions, or an average amount granted by the two or more of the one or more policy decisions.

41. The method of claim 35, wherein the resource consuming isolate includes a set of one or more computations, and wherein the resource consuming isolate does not share computational state with other isolates and does not share objects with other isolates.

42. The method of claim 35, further comprising characterizing the given resource with the one or more common resource attributes.

43. The method of claim 35, wherein the one or more common resource attributes include one or more of:

disposable, revocable, reservable, or bounded.

44. The method of claim 35,

wherein said invoking comprises:

determining one or more policy decision actions that are applicable to the request;

executing the one or more determined policy decision actions;

wherein said receiving comprises receiving the one or more policy decisions from execution of the one or more policy decision actions; and

wherein said governing further comprises;

determining the response based at least in part on the received one or more policy decisions.

45. The method of claim 44, further comprising determining that there are one or more reservations for the given resource, wherein said determining the response is further based on the determined reservations.

46. The method of claim 44, wherein at least one of the policy decision actions is associated with a trigger, and wherein the at least one of the policy decision actions is executed in response to the trigger resolving to true and is not executed if the trigger does not resolve to true.

47. The method of claim 46, wherein the trigger functions as a gate to the at least one of the policy decision actions associated with the trigger.

48. The method of claim 35, wherein the resource consuming isolate comprises a process, a thread, an operating environment, or an application.

49. The method of claim 35, embodied as a computer program product encoded in one or more non-transitory machine-readable storage media.

50. A computer program product, encoded on one or more non-transitory machine-readable storage media, the computer program product comprising program instructions executable by one or more computers to implement:

a dispenser class that defines an interface to expose a single, respective one of a plurality of consumable execution resources to computations that consume resources and to monitor and determine responses to requests for the single, respective resource, wherein consumable execution resources are measurable entities that computations can consume, wherein the dispenser class is instantiable to create a plurality of instances of the dispenser class, each of which is configured to monitor and determine responses to requests for a single, respective one of the plurality of consumable execution resources, and wherein determining a response to a resource request comprises determining whether to grant the resource request or determining an amount of the single, respective resource to grant; and

a resource request action class that defines an action to invoke an instance of the dispenser class;

wherein each of the plurality of resources is implemented by one or more computations that include one or more of;

an operating environment, libraries, programming language runtime systems, middleware, or applications classes;

wherein the program instructions that are executable to implement the dispenser class are distinct from program instructions comprising the one or more computations that implement each of the plurality of resources; and

wherein the program instructions that are executable to implement the dispenser class are distinct from program instructions comprising the computations that consume the plurality of resources.

51. The computer program product of claim 50, wherein the program instructions are further executable by the one or more computers to implement:

a resource attribute class that defines common resource attributes usable for characterizing resources of a broad range of resource types to be managed by instances of the dispenser class, wherein the common resource attributes characterize the resources with respect to consuming or releasing the resources, and wherein values of the common resource attributes as applied to any given resource are not unique values specific to the implementation of the given resource.

52. The computer program product of claim 51, wherein the common resource attributes comprise one or more of:

disposable, revocable, reservable, or bounded.

53. The computer program product of claim 52, wherein the common attributes further comprise a granularity attribute that indicates an indivisible unit of a resource that is manageable by instances of the dispenser class.

54. The computer program product of claim 52, wherein the common attributes further comprise a measurement delay attribute that indicates a maximum delay time between consuming a given resource and updating usage information of the given resource.

55. The computer program product of claim 52, wherein the common resource attributes further comprise an explicit attribute that indicates whether it is possible to identify a point at which the resource is consumed.

56. The computer program product of claim 50, wherein the program instructions are further executable by the one or more computers to implement a trigger class that defines a method for imposing a condition on invocation of one or more computations that impose a resource management policy for managing resource requests.

57. The computer program product of claim 56, wherein an instance of the trigger class utilizes current usage of a resource and requested usage of the resource to determine whether one or more associated policy decision actions should be executed.

58. The computer program product of claim 50, wherein an instance of the dispenser class provides a response to a resource consumer based at least in part on one or more resource management policy decisions.

59. The computer program product of claim 50, wherein an instance of the dispenser class provides a response to a resource consumer based at least in part on absence of a resource management policy decision.

60. The computer program product of claim 50, wherein the dispenser class is instantiable as a global dispenser or a local dispenser, wherein global dispenser instances of the dispenser class are used to monitor and determine responses to requests for resources with a single source of production and local dispenser instances of the dispenser class are used to monitor and determine responses to requests for resources that may be independently produced by multiple sources.

61. The computer program product of claim 50, wherein the program instructions are further executable by the one or more computers to implement a routine to determine a total amount of a single, respective resource to be managed by a single dispenser instance.

62. The computer program product of claim 50, wherein the program instructions are further executable by the one or more computers to implement a resource domain class that defines an entity that represents an association of a resource management policy with a given resource.

63. The computer program product of claim 50, wherein the program instructions are implemented in a safe language that is platform independent and application independent.

64. The computer program product of claim 63, wherein the safe language includes one or more of Java®

programming language, TeleScript, or Tcl.

65. A computer program product, encoded on one or more non-transitory machine-readable storage media, the computer program product comprising program instructions executable by one or more computers to implement:

a common resource attribute class that defines common resource attributes for characterizing resources with respect to consuming or releasing the resources, wherein the common resource attributes are applicable to resources of different types, wherein values of the one or more common resource attributes as applied to any given resource are not unique values specific to the implementation of the given resource, and wherein the one or more common resource attributes comprise one or more of;

disposable, revocable, reservable, or bounded; and

a dispenser class that defines a posting facility to monitor and process posted resource requests for a single, respective resource of a plurality of consumable execution resources based at least in part on abstractions of resources utilizing the common resource attribute class, wherein consumable execution resources are measurable entities that computations can consume, wherein the dispenser class is instantiable to create a plurality of instances of the dispenser class, each of which is configured to monitor and process requests for a single, respective one of the plurality of consumable execution resources, and wherein processing a posted resource request comprises determining whether to grant the posted resource request or determining an amount of the single, respective resource to grant;

wherein the program instructions that are executable to implement the dispenser class are distinct from program instructions comprising computations that implement each of the plurality of resources; and

wherein the program instructions that are executable to implement the dispenser class are distinct from program instructions comprising computations that consume the plurality of resources.

66. The computer program product of claim 65, wherein the common attributes further comprise a granularity attribute that indicates an indivisible unit of a resource that is manageable by instances of the dispenser class.

67. The computer program product of claim 65, wherein the common attributes further comprise a measurement delay attribute that indicates a maximum delay time between consuming a given resource and updating usage information of the given resource.

68. The computer program product of claim 65, wherein the common resource attributes further comprise an explicit attribute that indicates whether it is possible to identify a point at which the resource is consumed.

69. The computer program product of claim 65, wherein the program instructions are further executable by the one or more computers to implement a trigger class to gate imposition of one or more resource management policies.

70. The computer program product of claim 69, wherein the one or more resource management policies include one or more of:

usage limit policies, reservation policies, or notification policies.

71. The computer program product of claim 69, wherein an instance of the trigger class utilizes current usage of a resource and requested usage to determine whether corresponding policy decision actions should be executed.

72. A computer program product, encoded on one or more non-transitory machine-readable storage media, the computer program product comprising program instructions executable by one or more computers to implement:

characterizing a given resource with respect to consuming or releasing the given resource using one or more common resource attributes to separate the given resource from its implementation, wherein the given resource is a measurable entity that a resource consuming computation can consume, wherein the common resource attributes are applicable to characterize resources of different types, and wherein values of the one or more common resource attributes as applied to the given resource are not unique values specific to the implementation of the given resource;

managing requests for the given resource, wherein the program instructions executable by the one or more computers to implement managing requests for the given resource are distinct from program instructions comprising computations that implement the given resource, wherein the program instructions executable by the one or more computers to implement managing requests for the given resource are distinct from program instructions comprising resource consuming computations, wherein managing requests for the given resource comprises monitoring requests for the given resource and determining responses to the requests for the given resource, and wherein determining a response to a request for the given resource comprises determining whether to grant the request or determining an amount of the given resource to grant; and

hiding the computations that implement the given resource from the resource consuming computations;

wherein the program instructions executable by the one or more computers to implement managing requests for the given resource are configured to manage resource requests for a single, respective one of a plurality of consumable resources and are separate from program instructions executable by the one or more computers to implement managing requests for other ones of the plurality of consumable resources;

wherein said determining responses to resource requests for the given resource comprises;

invoking one or more computations that impose one or more resource management policies in determining responses to resource requests for the given resource; and

receiving one or more policy decisions with regard to the resource requests for the given resource from the computations that impose the one or more resource management policies.

73. The computer program product of claim 72, wherein the computations that implement the resource comprise an operating system, middleware, a library, a virtual machine, a programming language runtime system, or an application class.

74. The computer program product of claim 72, wherein the resource consuming computations are implemented as isolates, wherein an isolate is a set of one or more computations that does not share computational state with other isolates and does not share objects with other isolates.

75. An apparatus, comprising:

system memory;

means for separating implementation of a given resource from implementation of mechanisms for monitoring and determining responses to requests to consume or release the given resource that are posted by first computations, wherein the first computations are encapsulated to prevent sharing of computational state with other computations;

means for separating implementation of the mechanisms for monitoring and determining responses from implementation of the first computations; and

means for characterizing the given resource with respect to consuming or releasing the given resource using one or more common resource attributes, wherein the given resource is a measurable entity that a resource consuming computation can consume, wherein the common resource attributes are applicable to characterize resources of different types, wherein values of the one or more common resource attributes as applied to the given resource are not unique values specific to the implementation of the given resource, wherein the one or more common resource attributes comprise one or more of;

disposable, revocable, reservable, or bounded, wherein the monitoring and determining responses to consume or release requests for the given resource is based at least in part on the values of the one or more common resource attributes as applied to the given resource, and wherein determining a response to a consume request comprises determining whether to grant the consume request or determining an amount of the given resource to grant;

wherein the mechanisms for monitoring and determining responses are configured to monitor and determine responses to resource requests for a single, respective one of a plurality of consumable resources and are separate from mechanisms for monitoring and determining responses to requests to consume or release other ones of the plurality of consumable resources.

76. The apparatus of claim 75, further comprising a non-transitory machine-readable storage media that embodies said means.