KR20000002901A - Method for memory management with memory statistics - Google Patents

Abstract

PURPOSE: A method for memory management with memory statistics is provided to allocate memory according to progress of process status and deallocate memory according to completion of process state automatically. CONSTITUTION: The method comprises the steps of: allocating memory according to progress of process status, making memory statistics for uniting the memory allocation and the memory deallocation when the progress of process status completes, and deallocation the memory automatically. Thereby it is possible to remove case that can not be allocated according to discordance between memory allocation and deallocation.

Description

Memory management method with memory statistics

The present invention relates to a memory management method, and in particular, to provide memory statistics in a memory allocation and deallocation area in order to match memory allocation and release according to a specific process progress in a device using memory shared by one or more processes. It relates to a memory management method.

In the conventional memory management method, when a specific process is in progress in an application program, memory allocation and release according to the progress do not coincide, and thus the memory remains allocated even after the process is finished. If other processes were going on, there could be no more memory allocation. The disadvantage was that memory could not be used efficiently.

Accordingly, an object of the present invention is to automatically allocate memory of each step according to the progress of a step of the process and to automatically allocate the memory allocated to each step of the process after the completion of the step when the specific process proceeds. The present invention provides a memory management method including memory statistics in a memory allocation / release area for decommissioning.

The present invention for achieving the above object has a memory statistics having a memory allocation counter and a memory release counter in the memory allocation and release area according to the progress of a specific process in the memory to automatically match the memory allocation and release, memory statistics If there is an error caused by mismatch of memory allocation and release during execution, the display device may include a function of displaying the error content on the display device and a debugging function of allowing the user to directly correct the error in the display state.

1 is a block diagram schematically illustrating an internal configuration of a computer for performing a function according to an embodiment of the present invention.

2 is a diagram illustrating an example of a program applied to memory statistics according to an embodiment of the present invention.

3 is a flowchart illustrating a memory statistic process related to memory allocation and release according to a specific process in one embodiment of the present invention.

FIG. 4 is a flowchart illustrating a process of allocating and freeing memory areas according to a specific process according to an embodiment of the present invention.

5 is a flowchart illustrating a process of debugging memory statistics according to an embodiment of the present invention.

6 illustrates an example of a memory statistics table according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention will be described, and descriptions of other parts will be omitted so as not to obscure the subject matter of the present invention.

1 is a block diagram illustrating an internal configuration of a computer for performing a function according to an embodiment of the present invention. In particular, FIG. 1 is a block diagram of a computer capable of performing a memory management method having memory statistics for matching memory allocation and release. The internal configuration is shown. Although one embodiment of the present invention describes a computer as an example, the memory management method of the present invention may be applied to an apparatus using a memory shared by one or more processes.

The controller 111 shown in FIG. 1 controls the overall operation of the computer. The controller 111 scans the keyboard 115 at predetermined intervals and searches for a key signal input therefrom. In one embodiment of the present invention, a keyboard is used as an input device, but an input device such as a mouse may also be used. The keyboard 115 transmits a key signal corresponding to a key selected by the user to the controller 111. The controller 111 inputs a signal received from the keyboard 115 and analyzes the signal.

The memory 113 stores basic data on the work performed by the controller 111, and in particular, allocates and releases memory for a specific process in progress by the controller 111, and also stores the memory data in the memory allocation and release area. Memory statistics are provided to match memory allocation and release according to the process execution. The memory 113 stores a command and a display command for knowing the total memory space and the allocated memory space during the process operation.

In addition, when an error occurs in memory allocation and release of the memory statistics, the error content is detected by the controller 111 and the controller 111 transmits the error content to the monitor 119. The monitor 119 displays the received error content and outputs a job execution process and control items by the controller 111.

Therefore, a computer having an internal configuration as shown in FIG. 1 may have a memory management method for automatically matching memory allocations and releases as a process progresses by providing statistics on memory allocations and releases.

FIG. 2 is a diagram illustrating an example of a program applied to memory statistics according to an exemplary embodiment of the present invention. In particular, FIG. 2 illustrates an example of a program according to a specific process, for example, an A process.

3 is a flowchart illustrating a memory statistic process related to memory allocation and deallocation according to a specific process progress in an embodiment of the present invention.

When the computer configured as shown in FIG. 1 is operated, the controller 111 of FIG. 1 performs an initialization operation. In step 311, the control unit 111 scans the keyboard 115 of FIG. 1 and repeatedly checks whether there is a key input related to process selection. If there is a key input for process selection as a result of the test, the control unit 111 proceeds to step 313. In step 313, the controller 111 checks whether the process selection is a specific process, for example, process A of FIG. If the result of the check is not the process A selection, the control unit 111 determines that the key selection is for another process operation, and proceeds to step 314. In step 314, the controller 111 proceeds with the corresponding process according to the corresponding key selection. If the test result A is selected, the controller 111 proceeds to step 315. In step 315, the control unit 111 calls a function malloc () related to memory allocation according to process progression and proceeds to step 317. In step 317, the control unit 111 initializes the counter event_all oc [0] regarding memory allocation of memory statistics to 0 (event_alloc [0] = 0) and proceeds to step 319. In this case, event_alloc [0] is a counter related to process A, and in one embodiment of the present invention, up to 100 counters related to memory allocation may be designated. (BYTE event_alloc [100];) Therefore, if the counter is related to another process, One of event_alloc [1] through event_alloc [99] is used sequentially.

In step 319, the control unit 111 calls the function fr ee () on the allocated memory release and proceeds to step 321. In step 321, the control unit 111 initializes the counter event_free [0] relating to the release of the allocated memory of memory statistics to 0 (step event_free [0] = 0) and proceeds to step 323. In this case, event_free [0] is a counter related to process A, and according to an embodiment of the present invention, up to 100 counters related to memory allocation may be designated. (BYTE event_free [100];) One of event_free [1] through event_free [99] is used sequentially. Here, the number of the memory allocation counter event_alloc [] and the memory free counter event_free [] is equally designated. In step 323, the control unit 111 initializes the variable n regarding the progress of the process A to 1 (n = 1) and proceeds to step 325. Where n is the process in progress of process A divided by n.

In step 325, the control unit 111 starts the nth progression step and proceeds to step 327. In step 327, the controller 111 substitutes the value of event_alloc [0] + 1 into the value of event_alloc [0] (event_alloc [0] = event_alloc [0] + 1) and proceeds to step 329. In step 329, the control unit 111 repeatedly checks whether the n step has been completed. If the n progress step is finished, the control unit 111 proceeds to step 331. In step 331, the control unit 111 substitutes the value of event_free [0] + 1 into the value of event_free [0] (event_free [0] = event_free [0] + 1) and proceeds to step 333. In step 333, the control unit 111 substitutes a value of n + 1 into n (n = n + 1) and proceeds to step 335. In step 335, the control unit 111 checks whether the n progress step of the A process is the last step. If the test result is the last step, the control unit 111 returns. If the n progress step is not the last step, the control unit 111 returns to step 325.

According to the process of FIG. 3, the memory statistic process related to memory allocation and release may automatically match memory allocation and release according to process progress. In particular, by performing steps 327 and 331 of FIG. 3, memory allocation and release may be automatically matched.

FIG. 4 is a flowchart illustrating a process of allocating and releasing memory areas according to a specific process in an embodiment of the present invention.

When the computer configured as shown in FIG. 1 is operated, the controller 111 of FIG. 1 performs an initialization operation. In step 411, the controller 111 scans the keyboard 115 of FIG. 1 to repeatedly check whether there is a key input for starting a specific process, for example, process A. FIG. If there is a key input for starting process A, the controller 111 proceeds to step 413. In step 413, the control unit 111 proceeds to step 415 to allocate a memory when the nth progress step of the process execution is started. In step 417, the control unit 111 checks the nth progression step, and when the nth progression step ends, the control unit 111 proceeds to step 419. In step 419, the controller 111 releases the memory allocated to the n th progress step and proceeds to step 421. In step 421, the controller 111 checks whether the process A has ended. If the process A is finished, the control unit 111 returns. If the process A is not terminated, the control unit 111 returns to step 413.

In the same manner as in FIG. 4, memory regions may be allocated and released according to the progress of each step of the process.

FIG. 5 is a flowchart illustrating a process of debugging memory statistics according to an embodiment of the present invention. In particular, FIG. 5 is a diagram illustrating a process of debugging when a statistical value regarding memory allocation does not coincide with a statistical value regarding memory release in memory statistics. will be.

FIG. 5 will be described below with reference to the memory statistics process of FIG. 3.

In step 511, the control unit 111 of FIG. 1 checks whether the value of eve nt_alloc [0] and the value of event_free [0] performed in the memory statistics process match. If the result of the check ent_alloc [0] and the value of event_free [0] match, the control unit 111 returns. If the value of event_alloc [0] does not match the value of event_free [0], the controller 111 proceeds to step 513. In step 513, the control unit 111 outputs an error message previously stored in the memory 113 of FIG. 1 through the monitor 119 of FIG. 1 and proceeds to step 515. In step 515, the control unit 111 searches the keyboard 115 of FIG. 1 to check whether there is an input of a command for displaying the memory statistics. If there is no input of the test result, the control unit 111 returns. If there is an input of a test result command, the controller 111 proceeds to step 517. The control unit 111 outputs the memory statistics table through the monitor 119 in step 517 and proceeds to step 519. In step 519, the fraud control unit 111 searches for the keyboard 115 and checks whether there is a key input to correct the error. If there is no correction content input, the control unit 111 returns. If there is a correction result input, the controller 111 proceeds to step 521. In step 521, the control unit 111 stores the correction contents in the memory 113 and returns them.

Accordingly, the debugging operation process as shown in FIG. 5 enables the user to debug the error contents when an error occurs in memory statistics regarding memory allocation and release according to process progress.

FIG. 6 is a diagram illustrating an example of a memory statistics table according to an embodiment of the present invention, in which an index is assigned to each process so that an initial value of a corresponding event_alloc [] counter and event_free [] and an increase value according to the process progress are provided. Save it.

On the other hand, in the detailed description of the present invention has been described with respect to specific embodiments, various modifications are of course possible without departing from the scope of the invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

As described above, the present invention includes memory statistics regarding memory allocation and memory releasing as a process progresses, so that memory is continuously allocated because memory allocation and releasing according to a specific process progressing do not match. This has the advantage of eliminating cases where it cannot be allocated.

Claims (5)

And a memory device for allocating and releasing memory of a device using a memory shared by one or more processes, including a display device for displaying memory statistics and an input device for inputting an output to the display device. In the memory management method, Allocating a predetermined memory during each step of the process; Performing memory statistics to match memory allocation and release during the process at the end of each step of the process after the memory allocation; And automatically releasing a predetermined memory allocation allocated according to each step of the process after performing the memory statistics. The method of claim 1, And the memory statistics match memory allocation and release using a memory allocation and release counter equally designated by a predetermined number. The method of claim 1, The process of performing memory statistics, A first step of calling a memory allocation function for allocating memory according to a specific process; A second step of initializing a memory allocation counter of memory statistics after the call of the memory allocation function; A third process of calling an allocation memory releasing function for releasing memory according to the process after performing the initialization process of the memory allocation counter; A fourth step of initializing a memory release counter of the memory statistics after the allocation memory release function call; A fifth step of increasing the value of the memory allocation counter by adding a predetermined value as the process proceeds after the initialization of the memory release counter; A sixth step of increasing the value of the memory release counter by adding a predetermined value when the process is terminated after the increase of the memory allocation counter value; And a seventh process of repeatedly performing the fifth and sixth processes until all the steps of the process are completed. The method of claim 1, And if the memory allocation counter value and the memory release counter value of the memory statistics do not coincide with each other, debugging the memory. The method of claim 4, wherein The memory debugging process, Comparing a memory allocation counter value and a memory release counter value of the memory statistics; Outputting an error message through a display device when the counter value does not match as a result of the comparison; Receiving a command for monitoring the memory statistics table after outputting the error message; Outputting the memory statistics table to the display device after receiving the command; Receiving corrections from an operator after outputting the memory statistics table; And receiving the corrected contents and storing the contents in the memory statistics table.