Runtime-resource management

• US 7,334,228 B2
• Filed: 07/27/2001
• Issued: 02/19/2008
• Est. Priority Date: 07/27/2001
• Status: Expired due to Term

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Duimovich, John, Gray-Donald, Trent, Sciampacone, Ryan, Shipton, Peter Duncan, Clohessy, Kim, Lebert, Berthold
• Primary Examiner(s): An; Meng-AL T.
• Assistant Examiner(s): Truong; Camquy
• Application Number:
  US09/917,507
• Publication Number:
  US 20030023661A1
• Time in Patent Office: 2,398 Days
• Field of Search: 718103-104, 709/104, 709/203
• 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/5016 the resource being the memory
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A runtime-resource management method, system, and product for managing resources available to application components in a portable device. The method, system, and product provide for loading one or more new application components into a portable device only if maximum runtime resources required by the one or more new application components are available in the portable device assuming loaded application components within the device are using the maximum runtime resources reserved by the loaded application components, reserving maximum runtime resources required by application components when application components are loaded into the portable device, and running loaded application components using only the runtime resources reserved for the loaded application components.

Claims

1. A processor-implemented runtime resource management method for use with a portable device, said method comprising the steps of:

identifying one or more new application components scheduled to be loaded and stored on said portable device, each of said one or more new application components having a resource description list (RDL) associated therewith, said RDL identifying maximum required runtime resources that will be used when the respective application component is running;

determining maximum required runtime resources for said one or more new application components from each said associated RDL;

reserving maximum runtime resources required for running each application component stored in flashed memory of the portable device as defined by said RDL;

wherein said reserving step comprises;

allocating a segment of RAM within the portable device to each of application components stored in flash memory based on RAM requirements in said RDL associated with each of said application components, said allocated segment of RAM being for use by said application component stored in flash memory;

writing thread requirements to a thread table for each of said application component stored in flash memory based on thread requirements in said RDL associated with each said application components stored in flash memory;

writing socket requirement to a socket table for each of said application component stored in flash memory based on socket requirements in said RDL associated with each of said application component stored in flash memory; and

determining a CARSRMAX (Currently Available Runtime System Resources of the portable device assuming all already loaded application components are simultaneously using the respective MAXimum amount of runtime resources reserved for their use) of said portable device;

comparing, using said processor, said maximum required runtime resources for said one or more new application components to said CARSRMAX; and

prohibiting, using said processor, said one or more new application components from being loaded and stored on said portable device if said CARSRMAX is less than said maximum required runtime resources for running said one or more new application components.

2. The method of claim 1, wherein said step of determining said CARSRMAX comprises the steps of:

determining total runtime system resources of said portable device;

determining total maximum reserved runtime resources for application components stored in the flash memory of said portable device; and

calculating said CARSRMAX based on said total runtime system resources and said total maximum reserved runtime resources.

3. The method of claim 2, further comprising the steps of:

removing one or more of said application components stored in the flash memory of said portable device; and

releasing maximum runtime resources reserved for said one or more application components removed from the flash memory of said portable device, thereby increasing said CARSRMAX of said portable device.

4. The method of claim 1, further comprising the step of:

running one or more of said application components stored in flash memory of the portable device using no more than said maximum required runtime resources reserved for each of said one or more loaded application components.

5. The method of claim 4, wherein said running step comprises the steps of:

opening said one or more application components stored in flash memory;

monitoring requests for runtime resources by each of said one or more application components stored in flash memory; and

comparing runtime resources in use plus runtime resources requested to said maximum required runtime resources reserved for each of said one or more application components stored in flash memory.

6. The method of claim 1, further comprising the steps of:

running one or more of said application components stored in flash memory using said allocated segments of RAM;

monitoring RAM use, thread use, and socket use by said one or more application components stored in flash memory; and

preventing each of said one or more application components from using more than said segment of RAM allocated to each of said one or more loaded application components stored in flash memory.

7. A processor-implemented system having processor for managing runtime resources in a portable device, said system comprising:

means for identifying one or more new application components scheduled to be loaded and stored on said portable device, each of said one or more new application components having a resource description list (RDL) associated therewith;

means for determining maximum required runtime resources for said one or more new application components from each said associated RDL;

means for reserving maximum runtime resources required for running each application component stored in flashed memory of the portable device as defined by said RDL;

wherein said reserving step comprises;

means for allocating a segment of RAM within the portable device to each of application components stored in flash memory based on RAM requirements in said RDL associated with each of said application components, said allocated segment of RAM being for use by said application component stored in flash memory;

means for writing thread requirements to a thread table for each of said application component stored in flash memory based on thread requirements in said RDL associated with each said application components stored in flash memory;

means for writing socket requirements to a socket table for each of said application component stored in flash memory based on socket requirements in said RDL associated with each of said application component stored in flash memory; and

means for determining a CARSRMAX (Currently Available Runtime System Resources of the portable device assuming already loaded application components are using the MAXimum amount of runtime resources reserved for their use) of said portable device;

processing means for comparing said maximum required runtime resources for said one or more new application components to said CARSRMAX; and

processing means for prohibiting said one or more new application components from being loaded and stored on said portable device if said CARSRMAX is less than said maximum required runtime resources.

8. The system of claim 7, wherein said means for determining said CARSRMAX comprises:

means for determining total runtime system resources of said portable device;

means for determining total maximum reserved runtime resources for application components stored in the flash memory of said portable device; and

means for calculating said CARSRMAX based on said total runtime system resources and said total maximum reserved runtime resources.

9. The system of claim 8, further comprising:

means for removing one or more of said application components stored in the flash memory of said portable device; and

means for releasing maximum runtime resources reserved for said one or more application components removed from the flash memory of said portable device, thereby increasing said CARSRMAX of said portable device.

10. The system of claim 7, further comprising:

means for running one or more of said application components stored in flash memory of the portable device using no more than said maximum required runtime resources reserved for each of said one or more loaded application components.

11. The system of claim 10, wherein said means for running comprises:

means for opening said one or more application components stored in flash memory;

means for monitoring requests for runtime resources by each of said one or more application components stored in flash memory; and

means for comparing runtime resources in use plus runtime resources requested to said maximum required runtime resources reserved for each of said one or more application components stored in flash memory.

12. A processor-implemented computer program product for managing system resources in a portable device, said computer program product comprising:

computer readable program code embodied in a computer readable medium, the computer readable program code comprising at least;

computer readable program code for identifying one or more new application components scheduled to be loaded and stored on said portable device, each of said one or more new application components having a resource description list (RDL) associated therewith;

computer readable program code for determining maximum required runtime resources for said one or more new application components from each said associated RDL;

computer readable program code for reserving maximum runtime resources required for running each application component stored in flashed memory of the portable device as defined by said RDL;

wherein said reserving step comprises;

computer readable program code for allocating a segment of RAM within the portable device to each of application components stored in flash memory based on RAM requirements in said RDL associated with each of said application components, said allocated segment of RAM being for use by said application component stored in flash memory;

computer readable program for writing thread requirements to a thread table for each of said application component stored in flash memory based on thread requirements in said RDL associated with each said application components stored in flash memory;

computer readable program code for writing socket requirements to a socket table for each of said application component stored in flash memory based on socket requirements in said RDL associated with each of said application component stored in flash memory; and

computer readable program code for determining a CARSRMAX (Currently Available Runtime System Resources of the portable device assuming already loaded application components are using the MAXimum amount of runtime resources reserved for their use) of said portable device;

computer readable program code for comparing, using said processor, said maximum required runtime resources for said one or more new application components to said CARSRMAX; and

computer readable program code for prohibiting, using said processor, said one or more new application components from being loaded and stored on said portable device if said CARS RMAX is less than said maximum required runtime resources.

13. The product of claim 12, wherein said computer readable program code for determining said CARSRMAX comprises:

computer readable program code for determining total runtime system resources of said portable device;

computer readable program code for determining total maximum reserved runtime resources for application components stored in the flash memory of said portable device; and

computer readable program code for calculating said CARSRMAX based on said total runtime system resources and said total maximum reserved runtime resources.

14. The product of claim 13, wherein said computer readable program code embodied in a computer readable medium further comprises:

computer readable program code for removing one or more of said application components stored in the flash memory of said portable device; and

computer readable program code for releasing maximum runtime resources reserved for said one or more application components removed from the flash memory of said portable device, thereby increasing said CARSRMAX of said portable device.

15. The product of claim 12, wherein said computer readable program code embodied in a computer readable medium further comprises:

computer readable program code for running one or more of said application components stored in flash memory of the portable device using no more than said maximum required runtime resources reserved for each of said one or more application components stored in flash memory.

16. The product of claim 15, wherein said computer readable program code for running comprises:

computer readable program code for opening said one or more application components stored in flash memory;

computer readable program code for monitoring requests for runtime resources by each of said one or more application components stored in flash memory;

computer readable program code for comparing runtime resources in use plus runtime resources requested to said maximum required runtime resources reserved for each of said one or more application components stored in flash memory; and

computer readable program code for preventing each of said one or more application components stored in flash memory from using more than said maximum required runtime resources reserved for each of said one or more application components stored in flash memory.