Method and system for managing memory for software modules

• US 7,146,611 B1
• Filed: 02/24/2003
• Issued: 12/05/2006
• Est. Priority Date: 02/24/2003
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Phillips, Robert Andrew
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US10/373,403
• Time in Patent Office: 1,380 Days
• Field of Search: 717168-171, 717174-178, 717162-163, 717/166
• US Class Current: 717/174
• CPC Class Codes: G06F 9/44594 Unloading
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources

Abstract

The invention provides a method and system for managing memory for software modules in a computer processing environment. According to a first aspect of the invention, a method includes allocating memory for a first software module. The method also includes loading the first software module into the allocated memory. The first software module includes processor executable instructions for loading a second software module into memory. The method further includes registering the first software module for service and loading the second software module. According to a second aspect of the invention, a method is provided for releasing memory allocated according to the first aspect of the invention. Systems and articles of manufacture for managing memory for software modules are also described.

Claims

1. A method for reserving memory for a software module, comprising:

allocating memory for a first software module;

using a first loader to load the first software module into the allocated memory, the first software module having a second loader containing processor executable instructions for loading a second software module into the allocated memory;

registering the first software module for service, thereby reserving the memory allocated to the first software module; and

executing the processor executable instructions of the first software module; and

loading the second software module into the allocated memory.

2. The method of claim 1, wherein registering the first software module includes incrementing a hold count, the hold count indicating whether the first software module should be maintained in memory.

3. The method of claim 1 further comprising dynamically loading the second software module.

4. A method for releasing memory reserved for a software module, comprising:

executing processor executable instructions of a first software module having a first unloader for releasing a second software module from memory, the first software module residing in reserved memory;

releasing the second software module; and

unregistering the first software module for service using a second unloader, thereby releasing the memory reserved for the first software module.

5. The method of claim 4, wherein unregistering the first software module includes decrementing a hold count, the hold count indicating whether the memory reserved for the second software module can be safely released.

6. A software module, comprising:

module registration logic,

module unregistration logic, and

logic to load a second software module,

logic to unload the second software module, and

logic to direct calls to the second software module; and

creating a second software module containing logic for processing calls passed through the first software module.

7. The software module of claim 6, wherein the module registration logic includes an operating system call to external registration logic.

8. The software module of claim 6, wherein the module unregistration logic includes an operating system call to external unregistration logic.

9. A method for utilizing a registration service to dynamically load a software module regardless of the module type, comprising:

using a first loader to load a first software module into a reserved memory, the first software module being of a module type authorized to utilize a registration service;

executing the instructions of the first software module having a second loader to perform the steps of;

loading a second software module,

passing a request received by the first software module to the second software module for processing,

receiving a result from the second software module,

returning the result to a requesting process,

unloading the second software module; and

releasing the memory reserved for the first software module.

10. The method of claim 9, wherein the first software module comprises user programmed code.

11. The method of claim 9, wherein the second software module is of a module type that an operating system fails to recognize as being authorized to employ a registration service, and the operating system automatically utilizes the first software module to dynamically load the second software module.

12. A system for reserving memory for a software module, comprising:

a processor;

a memory connected to the processor for storing processor executable instructions to control the operation of said processor;

the processor executable instructions including;

instructions to register a first software module for service;

the first software module including instructions to allocate memory and load into the allocated memory a second software module associated with the first software module;

instructions to determine whether the first software module is needed for further processing;

instructions to unload the second software module from and release the allocated memory; and

instructions to unregister the first software module for service.

13. The system of claim 12, wherein the processor executable instructions further include:

instructions to allocate memory for a first software module;

instructions to load the first software module into the memory allocated for the first software module;

instructions to unload the first software module from the memory allocate for the first software module; and

instructions to release the memory allocated for the first software module.

14. The system of claim 12, wherein the processor executable instructions further include:

instructions to increment a hold count, the hold count indicating whether the first software module should be maintained in memory.

15. The system of claim 12, wherein the processor executable instructions further include:

instructions to call an operating system routine to update a switch table.

16. The system of claim 12, wherein the processor executable instructions further include:

instructions to dynamically load the second software module.

17. A system for managing memory, comprising:

a processor;

a memory connected to said processor storing;

a first software module;

a second software module associated with the first software module, wherein the first module includes instructions to load the second software module;

a switch table for storing a module hold count; and

processor executable instructions to control operation of the processor;

the processor executable instructions including;

instructions to register the first software module for service;

instructions to unregister the first software module for service; and

instructions to reserve and release memory for the second software module during execution of the first software module.

18. The system for managing memory of claim 17 wherein the processor executable instructions further comprise:

instructions to increment a hold count in the switch table, and

instructions to decrement a hold count in the switch table.

19. A computer-readable storage medium encoded with processing instructions for managing memory, including:

computer readable instructions that allocate memory for a first software module;

computer readable instructions that load the first software module into the allocated memory;

computer readable instructions that register the first software module for service; and

computer readable instructions that load a second software module associated with the first software module into the allocated memory.

20. A system for managing memory comprising:

a processor,

a memory,

a first loader for loading a first software module that is a dynamically loadable kernel module, a second software module that is associated with the first software module, wherein the first software module includes a second loader having instructions to load the second software module,

means for directing the processor to allocate memory for the first and second software modules, and

means for directing the processor to release the memory allocated for the first and second software modules.

21. The system for managing memory of claim 20, wherein the means for directing the processor to allocate memory for the first and second software modules comprises:

instructions to determine whether the first software module is dependent on the second software module,

instructions to allocate memory for the first software module,

instructions to load the first software module into the memory, and

instructions to allocate memory for the second software module if the first software module is dependent on the second software module.

22. The system for managing memory of claim 21, wherein the means for directing the processor to allocate memory for the first and second software modules further comprises:

instructions in the first software module to direct the processor to load the second software module into the memory.

23. The system for managing memory of claim 20, wherein the means for directing the processor to release the memory allocated for the first and second software modules comprises:

instructions to identify a number of dependent modules registered with the first software module,

instructions to unload the first software module from memory if the number of dependent modules registered with the first module equals zero,

instructions to unload the second software module from memory, and

instructions to release the memory allocated to the first and second software modules.

24. The system for managing memory of claim 23, wherein the number of dependent modules registered with the first software module is equal to a value of a hold count.

25. The system for managing memory of claim 24, wherein

the hold count is incremented when a dependent software module is registered, and

the hold count is decremented when a dependent software module is unregistered.

26. A system for managing memory comprising:

a first loader,

a first software module,

a second software module associated with the first software module,

memory, wherein the first software module includes a second loader having instructions for loading the second software module,

means for releasing memory allocated to at least one of the first software module and the second software module.

27. The system for managing memory of claim 26, wherein the means for releasing memory allocated to the first software module comprises:

decrementing the value of at least one of a hold count and a depend count for the first software module;

unloading the first software module from memory if the hold count and the depend count are equal to zero,

releasing memory allocated to the first software module if hold count and the depend count are equal to zero.

28. The system for managing memory of claim 26, wherein the means for releasing memory allocated to the second software module comprises:

decrementing the value of at least one of a hold count and a depend count for the second software module;

unloading the second software module from memory if the hold count and the depend count are equal to zero,

releasing memory allocated to the second software module if hold count and the depend count are equal to zero.

29. A system for dynamically loading a second software module into memory comprising:

a first loader,

a first software module,

a second software module associated with the first software module, wherein the first software module includes a second loader having instructions for loading the second software module, and

means for the first software module to load the second software module into memory,

wherein the second software module is not recognized as a dynamically loadable type software module.

30. The system for loading a second software module into memory of claim 29, wherein the means for the first software module to load the second software module into memory comprises:

instructions to determine that the first software module depends on the second software module,

instructions in the first software module to allocate memory for the second software module, and

instructions to load the second software module into the allocated memory.

31. The system for loading a second software module into memory of claim 30, wherein the means for the first software module to load the second software module into memory further comprises:

instructions to increment a depend count for the second software module,

instructions to increment a hold count for the first software module,

wherein the first software module is held in the memory as long as the hold count is greater than zero, and the second software module is held in memory as long as the depend count is greater than zero.