JP2008186383A - User-level process controller having process management function, method for it, and program for it - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a control process to accurately hold a controlled process table for carrying out process control in generation/disappearance of a controlled process in user-level process control wherein the process control is carried out when a user-level control process changes attributes of the controlled process without modifying an operating system. <P>SOLUTION: In a user-level process control system, the control process 110 has a process management function 113. When the controlled process 120 generates a subprocess, the process management function receives a process generation notification 210. The process management function receiving the notification makes addition to the controlled process table 112. When the controlled process 120 disappears, the process management function receives a process disappearance notification 220. The process management function receiving the notification deletes the corresponding process from the controlled process table. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a user level process control apparatus, method, and program therefor having a process management function in a computer in which an OS (operating system) manages a process, and in particular, a user level control process without modifying an operating system. The present invention relates to a user level process control apparatus having a user level process management function for controlling a user level controlled process, a method thereof, and a program thereof.

  Conventionally, in a computing system in which a plurality of programs operate, the program is represented by an execution unit called a process or a thread (hereinafter referred to as a process or a thread when described as a single process). In a computing system in which the plurality of programs operate, it is required to appropriately control the operation of the process.

  For example, when there is a process performing real-time processing, the restriction that the process should be performed in real time can be satisfied by controlling the process so as to use the CPU preferentially. Other process control methods include control of memory usage for each process and control of available network bandwidth.

  Generally, in a computing system in which a plurality of processes as described above operate, an OS (operating system) controls the processes. For this reason, if the process control function of the OS being used cannot perform the necessary process control for the process set operated on the computing system, sufficient performance cannot be obtained.

  For example, if the scheduler that determines the allocation of processes to CPUs, which is one of the OS process control functions, performs control to allocate all processes equally to CPUs without performing special process management, real-time processing There arises a problem that sufficient CPU utilization time cannot be given to the process performing the process.

  As a solution for such a case, a method of changing the OS itself can be considered. Specifically, there are (1) a method using another OS capable of controlling the process to satisfy the required performance, and (2) a method of expanding the function by modifying the currently used OS. .

  Here, in order to realize the above example (1), a real-time OS suitable for real-time processing can be introduced. However, in general, when the OS is different, there is no compatibility of the program. Therefore, in order to continue using the program after changing the OS, there is a problem that the program must be modified so as to correspond to the changed OS.

  On the other hand, the method (2) has a problem that dedicated knowledge is required to modify the OS. In addition to that, it is often impossible to obtain source codes for commercial OSs and the like.

  Even if the source code can be obtained, if the OS is modified, it is still difficult to make a change due to a problem in the support system such as being out of the scope of manufacturer support.

  There is a user level process control as a solution when it is difficult to change the OS. In the user level process control, a user level process operating on the OS becomes a control process, and controls other processes. In this case, it is not necessary to change the OS.

  In this case, the OS generally sets an attribute for each process, and performs process control according to the attribute. The OS also provides an API for changing process attributes from the user level. Therefore, the user level control process performs process control by changing the attribute of the controlled process using the API.

  Patent Document 1 discloses a technique for performing process control using process attribute information as described above.

  On the other hand, Patent Document 2 discloses a technique related to user-level process control. This document describes a user level process scheduler that controls scheduling of a controlled process to a CPU by a user level control process.

  In Patent Document 2, a user-level process scheduler that is a control process changes the priority and executable / stopped state attributes of a plurality of controlled processes registered as control targets. Here, as an example, consider a case where the process scheduler of the OS performs an operation of preferentially assigning a CPU to a process with the highest priority.

When such a CPU is preferentially assigned to a specific controlled process, the priority of the process is maximized, and the priority of other controlled processes is lowered, so that the OS process scheduler Control to assign the highest priority process to the CPU.
Japanese Patent Laid-Open No. 10-021099 JP-A-9-54699

  The first problem of the conventional user level process control as described above is that when the controlled process newly generates a child process, the control process cannot control the generated child process.

  The reason is that the control process does not have a function of knowing that the controlled process has created a child process. That is, the process is generated by the OS, and the ID of the generated process is directly notified to the parent process. That is, the child process is generated regardless of the processes other than the OS and the parent process.

  Therefore, since the control process has no parent-child relationship with the controlled process, the control process cannot know that the child process has been created except in a special case having a function of knowing that the child process has been created. Therefore, the control process cannot change the attribute for performing process control on the newly generated child process.

  Therefore, even when the program is composed of a plurality of processes including a parent process and its descendant processes, the control process can control only the parent process. Therefore, the control process can control only a part of the program, and there is a problem that the control process cannot be controlled so as to operate with sufficient performance as a whole.

  In this regard, in the conventional solution of the above-described problem described in Patent Document 2, in order to add the generated child process to the control target, the child process itself requests the control process to join as a controlled process. The solution to do is taken. Therefore, in order to employ this method, it is necessary to change the program in advance so that the program serving as the child process makes a join request as a controlled process to the control process.

  Of course, when the program is changed, the source code of the control process is not necessarily available, and even if the source code is available, the change requires a corresponding cost. Therefore, it can be said that it is a problem to know generation of a child process without changing the controlled process as in the conventional example.

  The second problem is that the controlled process cannot be excluded from the control target because the control process cannot know the disappearance of the controlled process. This is because the control process does not have a function of knowing the disappearance of the controlled process as described above.

  For this reason, even if the controlled process has already disappeared, the control process continues to be controlled even for the controlled process that does not exist, and there is a problem that the performance of the entire system deteriorates.

  As described above, the first object of the present invention is for the control process to know the generation of the child process by the controlled process and the disappearance of the controlled process. It is a second object of the present invention to provide a user level process control mechanism that allows the control process to change the attribute for all processes that need to be subject to process control.

  According to the present invention, a user level process control apparatus in which a user level control process performs process control, a means for generating a child process, a means for extinguishing a controlled process to be controlled, and a process There is provided a user level process control apparatus, method, and program characterized by comprising means for detecting the state change and process state grasping means for grasping the state change.

  In the above case, the information processing apparatus may further include means for managing process execution based on the process information grasped by the process state grasping means and the process state.

  According to the present invention, in a user level process control system, even when a process generates a child process or a process disappears by accurately grasping a process that needs to be controlled by the control process. It becomes possible to control the process appropriately.

The best mode for carrying out the invention will be described in detail with reference to the drawings.
First, the outline of the present invention will be described with reference to FIG. The control process 110 includes a process management function unit 111, and the process management function of the control process is characterized by receiving notifications when a child process is generated by the controlled process 120 and when the controlled process disappears.

  Upon receiving the child process generation notification 210, the process management function unit 111 of the control process adds the child process to the controlled process table 112 and updates the controlled process table to an accurate state.

  When the process management function unit 111 receives the notification 220 of the disappearance of the controlled process, the process management function unit 111 deletes the process from the controlled process table 112. As a result, unnecessary processes are excluded from the controlled process table, and the controlled process table is updated to an accurate state.

  From the above, even when a controlled process is generated or disappears, the controlled process table is maintained in an accurate state, so that the attribute change function 112 of the controlled process performs the process of the OS 130 for all necessary processes. The attributes recorded in the table 131 can be changed.

  The process control function unit 132 of the OS 130 performs process control with reference to attributes in the process table.

  FIG. 2 is a diagram showing a basic configuration of the embodiment of the present invention. The embodiment includes a control process 110, a controlled process 120, an OS 130, a process generation detection unit 310, and a process disappearance detection unit 320. The control process 110 includes a process attribute change function unit 112, a controlled process table 113, and a process management function unit 111.

  The present embodiment is characterized in that the process management function unit 111 of the control process 110 uses a user-level process generation detection unit 310 and a process disappearance detection unit 320.

  First, the OS 130 includes a process table 131 that holds process information and a process control function unit 132. The process control function unit 132 of the OS 130 performs process control according to the process attributes recorded in the process table 131.

  Next, the attribute change function unit 112 of the control process 110 changes the attribute of the controlled process 120 recorded in the process table 131 using the API provided by the OS 130. The controlled process table 113 of the control process 110 records the processes that are controlled by the control process.

  In addition, when a new child process is generated, the process management function unit 111 of the detection control process 110 detects and detects the child process generation of the controlled process 120 using the process generation detection unit 310. The child process is added to the controlled process table 113. Further, when the controlled process disappears, the process management function unit 111 of the control process 110 uses the process disappearance detection unit 320 to detect the disappearance of the controlled process 120, and from the controlled process table 113. delete.

  The process generation detection unit 310 is at a user level, and has a function of detecting generation of a child process of a process and notifying the control process 110 that is monitoring the generation. The process disappearance detection unit 320 is at the user level, and has the function of detecting the disappearance of the process and notifying the control process 110 that monitors the disappearance, as in the case of the above generation.

  Next, the operation of this embodiment will be described in detail with reference to FIGS. In the description, for simplification, only one process is displayed as a controlled process.

  FIG. 3 shows an operation in which the control process 110 controls the controlled process A120.

  Here, the operation is as follows. First, the control process indicates a change in the attribute of the process A120 in the process table 131 in order to control the process A120 (S10). Next, the process control function unit 132 of the OS 130 reads the attribute of the process A 120 recorded in the process table 131 (S11). Furthermore, it represents that the process control function unit 132 of the OS 130 controls the process A 120 according to the attribute (S12).

  FIG. 4 shows an operation when the control process detects the generation of the child process B122 by the controlled process A120 using the process generation detection unit 310 at the user level. First, the process A120 creates a child process B122 (S20). Accordingly, the process generation detection unit 310 detects the generation of the process B122 (S21).

  Then, the process generation detection unit 310 notifies the control process 110 of generation of a child process (S22). Next, the process management function unit 111 of the control process 110 that has received the notification registers the process B122 newly generated this time in the controlled process table 113 (S23).

  At this time, the attribute change function unit 112 of the control process 110 recognizes that the process B 122 is a control target, and changes the attribute of the process table 131 of the OS 130 (S24).

FIG. 5 shows an operation in which the control process 110 detects the disappearance of the controlled process B122 using the process disappearance detection unit 320 at the user level. First, the process disappearance detection unit 320 detects the disappearance of the process B122 (S30). Next, the process disappearance detection unit 320 notifies the control process 110 of the disappearance of the process B122 (S31). The process management function unit 111 of the control process 110 deletes the process B122 from the controlled process table 113 (S32).
[Embodiment]
Next, the operation of the best mode for carrying out the present invention will be described using specific embodiments. The configuration of the first embodiment of the present invention is shown in FIG. Note that the embodiment described below corresponds to the first embodiment of the present invention, but the attribute changing function of the control process is omitted in FIG.

  This embodiment is used when a library function that is called when a controlled process 120 generates a child process or when a controlled process ends is dynamically linked.

  In addition, this embodiment is characterized in that a dynamic linker and a dynamic link library provided in the dynamic linker are used as a user level process generation detection unit and a process disappearance detection unit.

  When a process generates a child process or terminates a process, a system call for requesting the OS to perform the process is performed. In this respect, in general, a process does not directly perform a system call, but calls a dedicated function in the system library, and the system call is executed in the library function.

  Therefore, if the library function that is called at the time of child process creation or process termination has a function to notify the control process, the child process creation or process termination is detected and further notified to the control process. Even that is possible.

  If the library function is dynamically linked, the dynamic linker resolves the link at process run time. A system library 420 shown in FIG. 6 indicates a library that is originally provided in the system. Here, the function in the system library 420 does not have a function of notifying the control process.

  On the other hand, the custom library 430 in FIG. 6 has the same function name as the function of the system library 420, but includes a function having a notification function to the control process in addition to the original function such as process generation and disappearance. .

  The dynamic linker 410 links a function in the custom library 430 as a library function called from the controlled process 120 instead of a function in the system library 420. That is, not the function in the system library 420 but the function in the custom library 430 is called.

  As a result, the function in the custom library 430 detects the generation of the child process or the disappearance of the controlled process, and further notifies the control process 110 of the fact of the creation or disappearance.

  Here, the replacement operation in which the function linked by the dynamic linker 410 is not a function in the system library 420 but a function in the custom library 430 is performed in the order in which the dynamic linker 410 searches the library function. This can be done by specifying a custom library 430.

  Also, in the case of Gnu (Gnu is Not Unix (registered trademark)) dynamic linker widely used in Linux, the replacement can be applied only to the controlled process using environment variables. is there.

  Furthermore, it is possible to replace all the dynamically linked processes by changing the dynamic linker setting file.

  Note that an inter-process communication function provided by the OS can be used for notification from the function in the custom library 430 to the control process 110 when the child process generation or the disappearance of the controlled process is detected.

  Next, an operation when the controlled process 120 generates a child process will be described with reference to FIG. First, the controlled process 120 calls the child process generation function fork (S40). Next, the dynamic linker 410 calls a fork function in the custom library 430 (S41).

  The fork function in the custom library 430 calls the fork function in the system library 420 (S42).

When the fork function in the system library 420 issues a system call, the OS 130 generates a child process (S43).
The fork function in the custom library 430 acquires the process ID of the generated child process and notifies the process management function unit 111 of the control process 110 using inter-process communication (S44). Then, the control process 110 adds the child process to the controlled process table 113 (S45).

  The control process 110 can grasp that a new process has been generated by the procedures of (S40) to (S45), and thereafter, the controlled process table with the newly generated process as a control target. It becomes possible to add to.

Next, an operation when the controlled process 120 disappears will be described.
First, the controlled process calls the process end function exit (S40).

  Next, the dynamic linker 41 calls the exit function in the custom library 430 (S41). Subsequently, the exit function in the custom library 430 calls the exit function in the system library 420 (S42).

  When the exit function in the system library 420 issues a system call, the controlled process disappears when the OS 130 performs the controlled process disappearance process (S43).

  The exit function in the custom library 430 notifies the process management function unit 111 of the control process 110 that the controlled process has disappeared using inter-process communication (S44).

  The control process 110 deletes the notified extinguished process from the controlled process table 113 (S45).

  With the above procedure, the control process 110 can grasp that the process has disappeared.

  As another form of the first embodiment, a configuration may be adopted in which the OS calls the OS 130 by a system call directly made by a custom library, and causes the OS to execute process generation or process extinction. As still another form of the first embodiment, the function in the system library 420 may be provided with a function for notifying the control process without using the custom library 430.

  The first embodiment can be realized simply by creating the custom library 430 and setting environment variables and changing the setting file of the dynamic linker. There is an effect that work such as adding a function is unnecessary.

  Further, since it can be applied to any function that is dynamically linked, there is an effect that even a function or call other than fork and exit can be detected and notified to the control process.

  Next, a modification of the embodiment of the present invention will be described with reference to FIG. The present embodiment is characterized in that the OS 130 includes a process generation detection unit 310 and a process disappearance detection unit 320, and the control process 110 uses them. The operation of this embodiment is the same as that of the above-described embodiment.

  Next, a mode for carrying out a further modification of the present invention will be described with reference to FIG. The embodiment shown in FIG. 9 is characterized in that the control process 110 itself has a process generation detection unit 310 and a process disappearance detection unit 320. The operation of this embodiment is the same as that of the above-described embodiment.

  2, 8, and 9, the process generation detection unit 310 and the process disappearance detection unit 320 exist in the same part of the user level, in the OS, or in the control process, respectively. is doing.

  In this regard, as a further different embodiment of the present invention, each of the process generation detection unit 310 and the process disappearance detection unit 320 may exist in different places.

  In addition to the above, as a different embodiment of the present invention, the process management function unit 111 of the controlled process 110 may use only the process generation notification or the process disappearance notification.

  As another embodiment of the present invention, the process management function unit 111 of the control process 110 may use a plurality of process generation detection units 310. Further, as a different embodiment of the present invention, the process management function unit 111 of the control process 110 may use a plurality of process disappearance detection units 320.

  In addition, as a different embodiment of the present invention, a configuration in which a plurality of control processes 110 exist may be employed. Further, as an embodiment of the present invention, the process management function of the control process may detect a process state change (for example, sleep) other than the generation and disappearance of the process and use it for user level process control.

  Next, the 2nd Embodiment of this invention is shown using FIG. The second embodiment corresponds to the above-described first embodiment of the present invention.

  The present embodiment is characterized in that a static link library is used as the process generation detection unit and the disappearance detection unit at the user level. Similar to the first embodiment, the basic configuration is the same in that a custom library 430 having a function having the same name as a process generation or disappearance function in the system library 420 is used.

  The difference from the first embodiment is that, when the controlled process generates a child process or when the controlled process disappears, the function in the custom library 430 is called instead of the function of the system library 420. This is realized by statically linking the custom library 430 to the controlled process 120.

  In FIG. 10, a configuration in which both the custom library 430 and the system library 420 are statically linked is illustrated. However, as another embodiment of the present embodiment, a configuration in which only the custom library 430 is statically linked may be employed. The operation of this embodiment is the same as that of the first embodiment. The advantage of the second embodiment is that the present invention can be used even when the controlled process uses a static link.

  Next, FIG. 11 shows the configuration of the third embodiment of the present invention. The third embodiment also corresponds to the first embodiment of the present invention. The present embodiment is characterized in that the process trace function 134 of the OS 130 is used to detect process generation or process disappearance.

  Here, the process trace function 134 of the OS 130 provides a function of temporarily stopping the trace target process and notifying the monitored process when the trace target process makes a system call. For example, Linux has such a process trace function.

  In this embodiment, first, the process management function unit 111 of the control process 110 calls a system call (for example, Linux ptrACe system call) that instructs to trace the process, and the control process 110 traces the controlled process 120. An instruction is issued to the OS 130 so that it can be performed.

  At this time, it is set to trace a system call related to process generation (for example, fork or Clone) and a system call related to disappearance (for example, exit).

  Thereafter, the control process 110 executes a wait system call and waits for a notification from the process trace function 134 of the OS 130.

  Next, an operation procedure when the controlled process creates a child process will be described with reference to FIG. The procedure is as follows. The controlled process 120 issues a system call for generating a child process (S50).

  The process trace function of the OS 130 is called according to the setting made in advance (S51).

  Next, the process trace function 134 of the OS 130 stops the controlled process 120 (S52). Furthermore, the process trace function 134 of the OS 130 notifies the control process 110 that a system call for generating the child process has been issued from the controlled process 120 (S53). Upon receiving the notification, the control process 110 returns from the wait system call and adds the newly created child process to the controlled process table 113 (S54).

  The control process 110 executes a system call for restarting the controlled process 120 (S55).

  Thereafter, the OS 130 restarts the controlled process 120 (S56).

  The operation when the controlled process 120 disappears under the above configuration is as follows.

  The controlled process 120 issues a system call for extinguishing the child process (S50). The process trace function of the OS 130 is called according to the setting made in advance (S51).

  The process trace function 134 of the OS 130 stops the controlled process 120 (S52). The process trace function 134 of the OS 130 notifies the control process 110 that the controlled process 120 has issued a system call for erasing the child process (S53). Upon receiving the notification, the control process 110 returns from the wait system call and deletes the child process to be deleted from the controlled process table 113 (S54).

  The control process 110 executes a system call for restarting the controlled process 120 (S55).

  Thereafter, the OS 130 restarts the controlled process 120 (S56).

  Unlike the first or second embodiment, the third embodiment has an effect that it can be used regardless of the link method of the controlled process. Furthermore, there is an effect that it is not necessary to create a custom library for notification. In addition, since the OS trace function stops the controlled process once and notifies the control process, the controlled process does not start operating before the control process is notified. There is also an effect.

  Next, FIG. 13 shows the configuration of the fourth embodiment of the present invention. The fourth embodiment corresponds to the third embodiment of the present invention. In the present embodiment, the control process has a process table search function 114 for searching a process table of the OS 130, so that the control process 110 itself has a process generation detection function and a process disappearance detection function. .

  The process table search function 114 has a function of accessing the process table 131 of the OS 130 using the API provided by the OS 130 and checking information on existing processes. As an API for accessing the process table 131, for example, the proC file system of Linux is cited.

  Next, the operation of the fourth embodiment when the controlled process generates a child process will be described with reference to FIG.

  First, the controlled process 120 executes a system call for generating a child process to the OS 130 (S60). The OS 130 receives the system call, generates a child process, and adds the ID of the new process and the ID of the parent process of the process to the process table 131 (S61).

  The process management function unit 111 of the control process 110 calls the process table search function 114 and searches for a new process having the current controlled process 120 as a parent process (S62).

  Next, the process table search function 114 of the control process 110 accesses the process table 131 to search for and find the new child process having the current controlled process 120 as the parent process (S63).

  Thereafter, the process management function unit 111 of the control process 110 receives the search result of the process table search function 114 and detects that a child process has been generated (S64).

  Then, the process management function unit 111 registers the new child process as a new control target in the controlled process table 113 (S65).

  By following the above procedure, the control process 110 can grasp that the controlled process has generated a child process.

  Further, by taking the same procedure, not only when a child process is generated, but also when the process disappears, the controlled process can grasp the fact that the process disappears.

  The fourth embodiment described above uses the process table as described above to link a custom library when it is difficult to add a notification function to the dynamic linker or when a program is statically linked. Even if it is impossible to implement any of the first to third embodiments, such as when the OS is not equipped with a process trace function, the present invention can be used.

  Next, a specific example of the execution result when the present invention is executed will be described with reference to FIG. The present invention is characterized in that the control process has a management function of a child process whose controlled process is a parent process, and is irrelevant to the specific contents of process control performed by the control process. In this embodiment, in order to show the effect of the above in an easy-to-understand manner, the description will be made using the allocation control (user level process scheduling) to the CPU of the process.

  In this specific example, a change in process execution / stop state attribute by a signal is used as an attribute changing means for user level process scheduling. In this specific example, it is assumed that there are three processes as controlled processes.

  Process A 510 is a real-time processing process for playing back music, and operates periodically. If this periodic operation is disturbed, sound skipping occurs and the user is uncomfortable. That is, it is a process that is required to be processed in real time.

  Next, the process B520 is an e-mail display process, and it is assumed that an e-mail is received during music playback and an e-mail display program is started. The e-mail display process is a non-real-time processing process that does not affect the user even if the operation is somewhat delayed.

  On the other hand, the process C530 is a child process generated by the process B520 and is a process for displaying an image attached to the mail. This is also a non-real-time processing process.

  Here, FIG. 15 shows that the convex portion of the figure uses the CPU, and that time advances from the left to the right in the figure. This figure shows the CPU usage of each process when each process performs an ideal operation. Further, the execution time of the control process is short, so it is omitted in the figure.

  FIG. 15A shows the use of the CPU when individual processes move independently, and FIG. 15B shows the case where three processes are moved simultaneously without performing user level process control. Since the OS process scheduler does not know the characteristics of each process as described above, desirable scheduling is not always performed.

  In this example, the processes B520 and C530 preferentially use the CPU by OS process scheduling. In this case, as described above, characteristics of each process such as whether or not it is a real-time processing process is not taken into consideration, so that the periodic operation of the process A51 is disturbed and sound skipping occurs.

  In order to avoid such an inappropriate state, it is necessary to control each process to use the CPU appropriately.

  FIG. 15C shows a case where user level process control having no process management function is used. Therefore, CPU usage time control is performed only for the process B which is the parent process.

  In the present embodiment, in accordance with the execution timing of the process A 510, a signal is sent from the control process to the process B 520 to change to the execution stop state, so that the execution of the process A 510 is not hindered and sound skipping can be prevented. . However, since the process C530 which is a child process is not under the control of the user level process control mechanism, the CPU usage time control is not performed for the process C53, which hinders the operation of the process A510. Therefore, it is impossible to completely control the process in accordance with the execution timing of the process A 510. As a result, it is not possible to completely prevent sound skipping.

  Further, FIG. 15D shows the use of the CPU in the case of a user level process control mechanism having a process management function. In (d), the CPU usage time is also controlled in the process C530. For this reason, the CPU A is preferentially assigned to the process A 510 which is a real-time processing process, and normally operates periodically. As a result, the above-described problem of sound skipping is prevented.

  In this way, by using user-level process control with a process management function, even if the controlled process generates a child process without modifying the OS or individual processes, the process is maintained so that real-time processing is maintained. Control can be performed.

  In the above description, the means for realizing user level process control is described as an attribute and attribute change, but this is merely an example of means for realizing user level process control. Therefore, as a matter of course, other means that the OS uses for process control and can be changed from the user level may be used without being limited to the realizing means. Therefore, it is assumed that the attribute and attribute change mentioned above collectively refer to other means for realizing user level process control.

The present invention is a computer system in which a plurality of application programs run under the control of an OS, and can be used for the purpose of appropriately operating each application program.

It is drawing for demonstrating the outline | summary of this invention. It is drawing for demonstrating the structure of the 1st Embodiment of this invention. It is a figure for demonstrating the operation | movement of the process control in the 1st Embodiment of this invention. It is drawing for demonstrating the operation | movement at the time of the child process production | generation by the controlled process in the 1st Embodiment of this invention. It is drawing for demonstrating the operation | movement at the time of extinction of the controlled process in the 1st Embodiment of this invention. It is drawing for demonstrating the structure of the 1st Embodiment of this invention. It is a figure for demonstrating the operation | movement at the time of the child process production | generation by the controlled process in the 1st Embodiment of this invention. It is drawing for demonstrating the structure of the modification of the 1st Embodiment of this invention. It is drawing for demonstrating the structure of the modification of the 1st Embodiment of this invention. It is drawing for demonstrating the structure of the 2nd Embodiment of this invention. It is drawing for demonstrating the structure of the 3rd Embodiment of this invention. It is a figure for demonstrating the operation | movement at the time of the child process production | generation by the controlled process in the 3rd Embodiment of this invention. It is drawing for demonstrating the structure of the 4th Embodiment of this invention. It is drawing for demonstrating the operation | movement at the time of the child process production | generation by the controlled process in the 4th Embodiment of this invention. It is drawing for demonstrating a specific effect about the execution result at the time of implementing this invention.

Explanation of symbols

110 Control Process 111 Process Management Function Unit 112 Attribute Change Function Unit 113 Controlled Process Table 114 Process Table Search Function 120 Controlled Process 121 Controlled Process A
122 Controlled process B
130 operating system 131 process table 132 process control function 133 process generation / deletion function 134 process trace function 210 process generation notification 220 process deletion notification 310 process generation detection unit 320 process end detection unit 410 dynamic linker 420 system library 430 custom library 510 process A
520 Process B
530 Process C

Claims (25)

A user level process control apparatus in which a user level control process performs process control,
Means for generating a child process;
Means for extinguishing the controlled process that is subject to process control;
Means for detecting process state changes;
A process status grasping means for grasping the status change;
A user level process control apparatus comprising: The user level process control device according to claim 1,
The state change detected by the process state grasping means indicates generation of a child process or disappearance of a controlled process which is a target of the process control. The user level process control device according to claim 1 or 2,
A user-level process control apparatus, further comprising means for setting an attribute of a process having undergone a change when the process state change is detected. The user level process control device according to any one of claims 1 to 3,
A user level process control apparatus, further comprising means for newly setting a child process that has detected the generation as a controlled process. The user level process control device according to any one of claims 1 to 4,
The means for detecting a change in the state of the process is performed based on a process trace function provided in the OS. The user level process control device according to any one of claims 1 to 4,
The user level process control apparatus according to claim 1, wherein the means for detecting a change in the state of the process is performed based on information held in a process table provided in the OS. The user level process control device according to any one of claims 1 to 4,
The means for detecting a change in the state of the process is performed based on a linker. The user level process control device according to any one of claims 1 to 7,
The user-level process control apparatus, wherein the controlled process detected by the control process is excluded from a control target by a subsequent user-level control process. The user level process control device according to any one of claims 1 to 8,
The process level grasping means is performed by a user level process generation or disappearance detection unit. The user level process control device according to any one of claims 1 to 8,
The process level grasping means is performed by a process generation or disappearance detection unit provided in the OS. The user level process control device according to any one of claims 1 to 8,
The process level grasping means is performed by a process generation or disappearance detection unit process generation detection unit possessed by a control process. The user level process control device according to any one of claims 1 to 11,
A user level process control apparatus, further comprising means for managing process execution based on the process information and process state grasped by the process state grasping means. A user level process control method in which a user level control process performs process control,
Creating a child process,
Extinguishing the controlled process that is the subject of the process control;
Detecting process state changes; and
A process state grasping step for grasping the state change;
A user-level process control method comprising: 14. A user level process control method according to claim 13, comprising:
The user level process control method characterized in that the state change detected in the process state grasping step indicates generation of a child process or disappearance of a controlled process which is a target of the process control. 15. A user level process control method according to claim 13 or 14,
A user-level process control method, further comprising a step of setting an attribute of a process having the change when a change in the state of the process is detected. The user level process control method according to any one of claims 13 to 15,
A user-level process control method, further comprising the step of newly setting a child process whose generation has been detected as a controlled process. The user level process control method according to any one of claims 13 to 16, comprising:
The means for detecting a change in the state of the process is performed based on a process trace function provided in the OS. The user level process control method according to any one of claims 13 to 16, comprising:
The user level process control method according to claim 1, wherein the means for detecting a change in the state of the process is performed based on information held in a process table provided in the OS. The user level process control method according to any one of claims 13 to 16, comprising:
The user level process control method according to claim 1, wherein the means for detecting a change in the state of the process is performed based on a linker. A user level process control method according to any one of claims 13 to 19, comprising:
The user level process control method characterized in that the extinguished controlled process detected by the control process is excluded from a control target by a subsequent user level control process. 21. A user level process control method according to any one of claims 13 to 20, comprising:
The user level process control method, wherein the process state grasping step is performed by a user level process generation or disappearance detection unit. 21. A user level process control method according to any one of claims 13 to 20, comprising:
The process level grasping step is performed by a process generation or disappearance detection unit provided in the OS. 21. A user level process control method according to any one of claims 13 to 20, comprising:
The process state grasping step is performed by a process generation or disappearance detection unit process generation detection unit possessed by a control process. A user level process control method according to any one of claims 13 to 23,
A user level process control method, further comprising a step of managing execution of a process based on process information and process state grasped by the process state grasping step.   A program causing a computer to execute the process control method according to any one of claims 13 to 24.

Images