Memory management configuration

• US 8,713,524 B2
• Filed: 04/06/2005
• Issued: 04/29/2014
• Est. Priority Date: 04/06/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Prakriya, Mahesh, Maffeo, Robin M., Dussud, Patrick H.
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Wang, Ben C
• Application Number:
  US11/099,841
• Publication Number:
  US 20060230387A1
• Time in Patent Office: 3,310 Days
• Field of Search: None
• US Class Current: 717/121
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Dynamic memory management configuration enables certain behavior of an application to be controlled without touching or affecting any executable portion of the application.

Claims

1. A method, comprising:

in an executing runtime execution environment;

loading a module of executable code;

loading a configuration file associated with the module of executable code;

within the executing runtime execution environment, dynamically selecting a memory management module from a plurality of memory management modules based on a comparison of parameters in the configuration file to capabilities of the runtime execution environment when executing the module of executable code including a number of processors simultaneously hosting the runtime execution environment and a throughput capability of the runtime execution environment, the plurality of memory management modules comprising a workstation garbage collector and a server garbage collector.

2. The method according to claim 1, wherein the configuration file is a text file comprising at least one conditional statement relating to at least one of the parameters related to capabilities of the runtime execution environment.

3. The method according to claim 1, wherein the configuration file is attached to the module of executable code.

4. The method according to claim 1, wherein the configuration file is received separately from the module of executable code.

5. The method according to claim 1, wherein the selecting is based on performance parameters specified in the configuration file.

6. The method according to claim 1, wherein the selecting is based on scalability parameters specified in the configuration file.

7. The method according to claim 1, wherein the selecting is based on parameters pertaining to resource availability specified in the configuration file.

8. The method of claim 1, wherein the selecting is based a comparison of parameters pertaining to resource availability specified in the configuration file and parameters related to the executing runtime execution environment.

9. A system, comprising:

a plurality of memory resources comprising a memory;

a loader to load an executable code;

plural management modules to manage the plurality of memory resources during execution of the executable code, the plural of management modules comprising a workstation garbage collector and a server garbage collector; and

an administrative module to, from within an executing runtime execution environment, dynamically select at least one of the management modules based on a comparison of parameters in a configuration file associated with the executable code to capabilities of the runtime execution environment when executing the executable code including a number of processors simultaneously hosting the runtime execution environment and a throughput capability of the runtime execution environment.

10. The system according to claim 9, wherein the system is a managed execution environment.

11. The system according to claim 9, wherein the loader is to further receive the configuration file as an attachment to the executable code.

12. The system according to claim 9, wherein the loader is to further receive the configuration file in an off-line manner separate from the executable code.

13. The system according to claim 9, wherein the plural management modules are garbage collectors.

14. The system according to claim 9, wherein the administrative module is to dynamically select at least one of the management modules when a flag in the configuration file is referenced upon initialization of the executable code.

15. The system according to claim 9, wherein the administrative module is to select at least one of the management modules when a flag in the configuration file indicates that a number of resources capable of interacting with the system exceed default parameters.