JP2007188244A - Process-sharing memory management system, process- sharing memory management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent occurrence of problems due to omission in stopping of a process and omission in releasing of a shared memory in a computer system which controls the shared memory by the plurality of processes, and to improve fault tolerance of the system. <P>SOLUTION: A process-sharing memory situation confirming means 40 confirms whether or not any process in startup state remains in a process startup situation management means 20 and whether or not the shared memory in acquisition state remains in a shared memory acquisition situation management means 30 due to any fault at ending of the system and when the process in startup state or the shared memory in acquisition state remains, it is forcedly stopped or released. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a process shared memory management method, a process shared memory management method, and a program. In particular, in a computer system that performs a process for controlling a shared memory by a plurality of processes, problems that cause a process stop leak or a shared memory release leak have occurred. The present invention relates to a management method for preventing the problem.

  In general, in a computer system, a shared memory is prepared in order to share data among a plurality of programs. In the conventional shared memory management system, management relating to securing, releasing, referencing, and updating of each memory area in the shared memory is performed independently in each process.

  However, the conventional shared memory management method described above has a problem that a memory area that is no longer necessary after being secured remains in the shared memory as it is, and the shared memory cannot be efficiently managed. This is because a plurality of memory areas of the shared memory are normally secured in units of processes, and it is left to each process to determine whether or not all memory areas secured at the end of processing are available.

  Further, in the conventional shared memory management method, regarding the memory area release processing, all the memory areas are unconditionally released when the process explicitly instructs the release or at the end of the process.

On the other hand, for example, in Patent Document 1, a memory management method for holding or releasing a memory or a buffer as needed without explicitly specifying the release of the memory at the end of a process or task that uses the memory Is disclosed.
JP-A-6-12314

  FIG. 4 shows an example of a conventional multi-process / shared memory control system. In the conventional specifications, as described above, the shared memory is managed individually by each process, so that the process and shared memory are not required when the system malfunctions and the process / shared memory control processing does not operate normally. Sometimes left behind. In other words, in the startup process, if there is a problem in the process start and stop processing, the process may remain illegally, and if there is a problem in the memory acquisition and release processing in the shared memory, the shared memory remains illegally There was a possibility.

  In addition, the memory management method disclosed in Patent Document 1 performs memory release and memory holding as needed without an explicit instruction for memory release by a process. It is a condition, and memory is not released when the process remains without being terminated due to a malfunction.

  In a computer system in which each process acquires and releases shared memory, if one process leaks the release of shared memory and the shared memory is exhausted as a result of this, other processes cannot use the shared memory. This can cause serious system failure.

  SUMMARY OF THE INVENTION Therefore, the present invention provides a computer system that performs processing for controlling a shared memory by a plurality of processes, thereby preventing problems caused by process stop leaks and shared memory release leaks and improving the fault tolerance of the system. With the goal.

  In order to achieve this object, the present invention provides a process shared memory management method for a computer system in which a plurality of processes are executed and a process for controlling a shared memory is performed by the process, in response to an activation request from the process. A process starting unit for starting, a process stopping unit for stopping a process in response to a stop request from the process, a process starting state managing unit for managing a process starting state started by the process starting unit, and the process starting A shared memory acquisition means for acquiring a corresponding shared memory in response to an acquisition request from a process started by the means, and a release request from the process acquired by the shared memory acquisition means for releasing the shared memory The shared memory releasing means and the shared memory acquiring means Shared memory acquisition status management means for managing the obtained shared memory acquisition status, and process shared memory status confirmation means for finally checking the process activation status and the shared memory acquisition status, and the process shared memory status confirmation Means confirms the process activation status management means and the shared memory acquisition status management means at the time of system termination, and forcibly stops the process in the activated state and releases the shared memory in the acquired state; To do.

  In the present invention, the process activation status is managed by registering the activated process and deleting the stopped process from the registration. Further, the shared memory acquisition status management means registers the acquired shared memory and manages the shared memory acquisition status by deleting the released shared memory from the registration. Then, the process shared memory status checking means, which is the main configuration, checks whether there is a process that is still in the active state due to some trouble etc. in the process startup status management means, and the process error in the shared memory acquisition status management means Check whether there is any unshared memory that has not yet been released due to, for example, when the system is shut down. release.

  By configuring as described above, if the process stop process is not performed normally due to a process error, etc., it is possible to forcibly terminate the active process remaining at the time of system termination so that the process does not remain unnecessary. In addition, even when the shared memory release process is not normally performed due to an abnormal process process or the like, it is possible to forcibly release the acquired shared memory so that the shared memory does not remain unnecessary.

  The present invention also provides a process start step for starting a process in response to a start request from the process in a computer system in which a plurality of processes are executed and the process controls the shared memory. A process stop step for stopping a process in response to a stop request, a process start state management step for managing a process start state started by the process start step, and an acquisition request from a process started by the process start step A shared memory acquiring step for acquiring the corresponding shared memory, a shared memory releasing step for releasing the shared memory in response to a release request from the process acquired in the shared memory acquiring step, and the shared memory acquiring step. Shared memory acquisition that manages the acquired shared memory acquisition status Status management step, and a process shared memory status confirmation step for finally confirming the process activation status and the shared memory acquisition status, and the process shared memory status confirmation step is performed when the system is terminated. As a process shared memory management method, the process startup status and the shared memory acquisition status management step are confirmed, and the process in the startup state and the shared memory in the acquisition state are forcibly terminated. It can also be realized in a method aspect.

  In addition, the present invention provides a process start function for starting a process in response to a start request from the process, and a process start function from the process, in a computer system in which a plurality of processes are executed and the process controls the shared memory. A process stop function for stopping a process in response to a stop request, a process start state management function for managing a process start state started by the process start function, and an acquisition request from a process started by the process start function A shared memory acquisition function for acquiring a corresponding shared memory, a shared memory release function for releasing the shared memory in response to a release request from a process acquired by the shared memory acquisition function, and the shared memory acquisition function. Shared memory acquisition that manages the acquired shared memory acquisition status A program for causing a computer to execute a status management function and a process shared memory status confirmation function for finally confirming the process activation status and the shared memory acquisition status, wherein the process shared memory status confirmation function is As a program for confirming a process activation status by the process activation status management function and a shared memory acquisition status by the shared memory acquisition status management function, and forcibly terminating the process in the activated state and the shared memory in the acquired state It can also be realized in the form of a program.

  According to the present invention, in a computer system that performs processing for controlling a shared memory by a plurality of processes, problems caused by a process stop leak or a shared memory release leak can be prevented, and the fault tolerance of the system can be improved. Is possible.

<Embodiment 1>
A process shared memory management system according to an embodiment of the present invention will be described with reference to FIG. FIG. 1 is an overall configuration diagram of the process shared memory management system of this embodiment.

  The process shared memory management system of the present embodiment includes a process activation unit 11, a process stop unit 12, a shared memory acquisition unit 13, a shared memory release unit 14, a process activation state management unit 20, a shared memory acquisition state management unit 30, and a process sharing. The memory status confirmation unit 40 is configured.

  The process activation unit 11 activates a process upon receiving an activation request, and registers a process registration name in the process activation state management unit 20 when the process is activated. In addition, the process stop unit 12 stops the process in response to the stop request, and deletes the process registration name registered in the process activation status management unit 20 when the process is stopped.

  For example, the process registration name a21 is registered in the process activation status management unit 20 through the process activation unit 11 when the process A1 is activated. Similarly, the process registration name b22 for the process B2 and the process registration name c23 for the process C3 are registered in the process activation status management unit 20, respectively.

  On the other hand, when the process A1 is stopped, the process registration name a21 is deleted from the process activation status management means 20 through the process stop means 12. Similarly, the process registration name b22 is deleted when the process B2 is stopped, and the process registration name c23 is deleted when the process C3 is stopped.

  Note that only one process registration name can be registered for each process. This is because the registration name to be used must be unique when considering the improvement in fault tolerance of the system.

  The shared memory acquisition unit 13 acquires a shared memory in response to a memory acquisition request, and registers a shared memory registration name in the shared memory acquisition state management unit 30 at the time of acquisition. The shared memory releasing unit 13 releases the shared memory acquired in response to the memory release request, and deletes the shared memory registration name registered in the shared memory acquisition state management unit 30 at the time of releasing.

  For example, when the shared memory used by the process A1 is acquired, the shared memory registration name 1a31 is registered in the shared memory acquisition status management unit 30 through the shared memory acquisition unit 13. Similarly, the process registration name 1b32 for the shared memory of the process B2 and the process registration names 1c33 and 1d34 for the shared memory of the process C3 are registered in the shared memory acquisition status management unit 30, respectively.

  On the other hand, when the shared memory acquired by the process A1 is released, the shared memory registration name 1a31 is deleted from the shared memory acquisition status management unit 30 through the shared memory release unit 14. Similarly, the shared memory registration name 1b32 is deleted when the shared memory of the process B2 is released, and the process registration names 1c33 and 1d34 are deleted when the shared memory of the process C3 is released. However, there is a possibility that the shared memory used in a certain process cannot be released when it is being referenced from another process.

  A plurality of shared memory registration names can be registered for each process. For example, as described above, the process registration names 1c33 and 1d34 can be registered when the shared memory is acquired for the process C3. In addition, when considering the improvement of fault tolerance of the system, the registered name to be used must be unique.

  Then, the process shared memory status confirmation means 40 confirms the process activation status and the shared memory acquisition status when the system is terminated, and forcibly stops or releases the activated process and the acquired shared memory. Specifically, it is confirmed whether the process registration name or the shared memory registration name that has been registered without being deleted in the process activation status management means 20 or the shared memory acquisition status management means 30 remains. If so, delete the registered name and forcibly stop the process or release the shared memory.

  For example, for the process C3, when the process stop process is not normally performed due to a process abnormality or the like, the process registration name c23 is not deleted and remains in the process activation status management unit 20, but the process shared memory status confirmation unit 40 When the system ends, this process registration name c23 is deleted, and the process C3 is forcibly stopped.

  In addition, when the above process processing abnormality occurs, the shared memory release name is not normally executed and the shared memory registration names 1c33 and 1d34 are not deleted but remain in the shared memory acquisition status management unit 30. The shared memory status confirmation unit 40 deletes the shared memory registration names 1c33 and 1d34 when the system ends, and forcibly releases the shared memory used in the process C3.

  In this way, if the process stop process is not performed normally due to a process error or the like, the process startup status is checked when the system is shut down, and the process that has been started is forcibly terminated so that the process does not remain unnecessary. Can be dealt with. Also, if shared memory release processing is not performed normally due to process processing error, etc., the shared memory is not required by checking the shared memory acquisition status and forcibly releasing the acquired shared memory at the time of system termination Can be dealt with so as not to remain.

<Embodiment 2>
Next, a process shared memory management system according to another embodiment of the present invention will be described with reference to FIG. FIG. 2 is an overall configuration diagram of the process shared memory management system of this embodiment. In the present embodiment, the management method of the first embodiment is applied to a computer system in which a memory area for an application and a memory area for a driver are separated.

  In this embodiment, the processes are, for example, a log information control process 201, a trace information control process 202, a command exclusion control process 203, a file transfer control process 204, and a server configuration management process 205.

For example, the process registration name and the shared memory registration name corresponding to each process are set as follows.
Log information control process 221 and first log control information 231
Trace information control process 222 and first trace control information 232
Command exclusive control process 223, first command exclusive information 233, and second command exclusive information 234
File transfer control process 224, first file transfer information 235, and second file transfer information 236
Server configuration management process 225 and first server configuration management information 237
The process registration name is registered in the process activation status management unit 220 to manage the process activation status, and the shared memory registration name is registered in the shared memory acquisition status management unit 230 to manage the shared memory acquisition status.

  The operations of the process activation unit 211, the process stop unit 212, the shared memory acquisition unit 213, the shared memory release unit 214, and the process shared memory status confirmation unit 240 are the same as those in the first embodiment.

  For example, if the log information control process 201 is not normally stopped due to a problem, the log information control process 221 is not deleted but remains registered in the process activation status management unit 220. When the system is terminated, the process shared memory status confirmation unit 240 confirms the process activation status, finds the remaining log information control process 221, deletes the registered name, and forcibly stops the log information control process 201.

  Also, due to the processing abnormality of the log information control process 201, the first log control information 231 remains registered without being deleted in the shared memory acquisition status management unit 230. However, the process shared memory status confirmation unit 240 The first log control information 231 remaining after confirming the shared memory acquisition status is found, the registered name is deleted, and the shared memory used in the log information control process 201 is forcibly released.

  In this way, even if the process or shared memory remains without being stopped or released due to a process failure, check the process startup status and shared memory acquisition status at the time of system termination and forcibly stop or release it. By doing so, it is possible to deal with processes and shared memory so that they are not left unnecessarily.

<Embodiment 3>
Next, a process shared memory management system according to another embodiment of the present invention will be described with reference to FIG. FIG. 3 is an overall configuration diagram of the process shared memory management method of the present embodiment. In the second embodiment, a case where a shared memory is controlled by a plurality of processes such as a UNIX (registered trademark) user space has been described. However, an application or driver uses a memory area in units of processing tasks. Even in the case, it can be similarly implemented. In other words, in the present embodiment, the management method of the first embodiment is applied to a computer system in which a memory area for an application and a memory area for a driver are used in the same memory area.

  In this embodiment, the tasks are, for example, a disk control task 301, a port control task 302, a command exclusive control task 303, a data transfer control task 304, and a chip control task 305.

For example, the task registration name and the memory registration name corresponding to each task are set as follows.
Disk control task 321, first disk control information 331, and second disk control information 332
Port management task 322 and first port management information 333
Command exclusive control task 323, first command exclusive information 334, and second command exclusive information 335
Data transfer control task 324, first data transfer information 336, and second data transfer information 337
Chip control task 325 and first chip configuration management information 338
The task registration name is registered in the task activation status management unit 320 to manage the task activation status, and the memory registration name is registered in the memory acquisition status management unit 330 to manage the memory acquisition status.

  The task start means 311 is a process start means, the task stop means 312 is a process stop means, the memory acquisition means 313 is a shared memory acquisition means, the memory release means 314 is a shared memory release means, and the task memory status check means 340 is a process. Corresponding to the shared memory status confirmation unit, the operation of each component is the same as that of the first embodiment.

  For example, when the first disk control information 331 and the second disk control information 332 are referred to by a plurality of tasks and the release process is not performed normally due to a failure of the memory release process, both the memory acquisition status management unit 330 are informed. The registered memory name is not deleted but remains registered. The task memory status confirmation unit 340 confirms the memory acquisition status when the system is terminated, finds the remaining first disk control information 331 and second disk control information 332, deletes the registered name, and remains acquired. Force memory to be freed.

  In this way, even if memory is left unreleased due to a failure in memory release processing, memory is not left unnecessarily by checking the memory acquisition status and forcibly releasing it at the time of system termination. Can deal with.

  The above-described embodiment is a preferred embodiment of the present invention, and the scope of the present invention is not limited to the above-described embodiment alone, and various modifications are made without departing from the gist of the present invention. Implementation is possible.

It is a whole block diagram of the process shared memory management system which concerns on embodiment of this invention. It is a whole block diagram of the process shared memory management system which concerns on embodiment of this invention. It is a whole block diagram of the process shared memory management system which concerns on embodiment of this invention. It is a whole block diagram of the conventional process shared memory management system.

Explanation of symbols

1 Process A
2 Process B
3 Process C
11, 211 Process activation means 12, 212 Process stop means 13, 213 Shared memory acquisition means 14, 214 Shared memory release means 20, 220 Process activation status management means 21 Process registration name a
22 Process registration name b
23 Process registration name c
30, 230 Shared memory acquisition status management means 31 Shared memory registration name 1a
32 Shared memory registration name 1b
33 Shared memory registration name 1c
40,240 Process shared memory status confirmation means

Claims (7)

In a computer system in which a plurality of processes are executed and processing for controlling a shared memory is performed by the processes,
Process starting means for starting a process in response to a start request from the process;
A process stop means for stopping a process in response to a stop request from the process;
Process activation status management means for managing the process activation status activated by the process activation means;
A shared memory acquisition means for acquiring a corresponding shared memory in response to an acquisition request from a process activated by the process activation means;
A shared memory releasing means for releasing the shared memory in response to a release request from the process acquired by the shared memory acquiring means;
Shared memory acquisition status management means for managing the shared memory acquisition status acquired by the shared memory acquisition means;
Process shared memory status confirmation means for finally confirming the process activation status and the shared memory acquisition status,
The process shared memory status confirmation means confirms the process activation status management means and the shared memory acquisition status management means at the time of system termination, and forcibly stops the process in the activated state and releases the shared memory in the acquired state. A process shared memory management system characterized by The process activation means registers a process registration name, which is a registration name for identifying the activated process, in the process activation status management means,
The process stop unit deletes the process registration name registered by the process start unit from the process start state management unit,
The process shared memory status confirmation unit deletes a process registration name registered in the process activation status management unit without being deleted by the process stop unit when the system is terminated. Process shared memory management method. The shared memory acquisition means registers a shared memory registration name, which is a registered name for identifying the acquired shared memory, in the shared memory acquisition status management means,
The shared memory releasing means deletes the shared memory registration name registered by the shared memory acquiring means from the shared memory acquisition status managing means,
The process shared memory status confirmation unit deletes a shared memory registration name registered in the shared memory acquisition status management unit without being deleted by the shared memory release unit when the system is terminated. 3. The process shared memory management method according to 1 or 2.   4. The process shared memory management system according to claim 1, which is applied to a computer system in which a memory area for an application and a memory area for a driver are separated.   The process sharing according to any one of claims 1 to 3, wherein the memory area for an application and the memory area for a driver are applied to a computer system used in the same memory area. Memory management method. In a computer system in which a plurality of processes are executed and processing for controlling a shared memory is performed by the processes,
A process start step for starting a process in response to a start request from the process;
A process stop step for stopping a process in response to a stop request from the process;
A process activation status management step for managing the process activation status activated by the process activation step;
A shared memory acquisition step for acquiring a corresponding shared memory in response to an acquisition request from the process started by the process start step;
A shared memory release step for releasing the shared memory in response to a release request from the process acquired in the shared memory acquisition step;
A shared memory acquisition status management step for managing a shared memory acquisition status acquired by the shared memory acquisition step;
A process shared memory status confirmation step for finally confirming the process activation status and the shared memory acquisition status,
The process shared memory status confirmation step confirms the process activation status by the process activation status management step and the shared memory acquisition status by the shared memory acquisition status management step at the time of system termination, and the process in the activated state and the share in the acquired state A process shared memory management method characterized by forcibly terminating memory. In a computer system in which a plurality of processes are executed and processing for controlling a shared memory is performed by the processes,
A process start function for starting a process in response to a start request from the process;
A process stop function for stopping a process in response to a stop request from the process;
A process activation status management function for managing the process activation status activated by the process activation function;
A shared memory acquisition function for receiving an acquisition request from a process started by the process start function and acquiring a corresponding shared memory;
A shared memory release function for releasing the shared memory in response to a release request from a process acquired by the shared memory acquisition function;
A shared memory acquisition status management function for managing a shared memory acquisition status acquired by the shared memory acquisition function;
A program for causing a computer to execute a process shared memory status confirmation function for finally confirming the process activation status and the shared memory acquisition status,
The process shared memory status check function checks the process startup status by the process startup status management function and the shared memory acquisition status by the shared memory acquisition status management function when the system is terminated, and the process in the startup state and the share in the acquisition status A program characterized by forcibly terminating memory.

Images