JPH08328884A - Resource management device - Google Patents

Abstract

PURPOSE: To manage the resources so as to assure every exclusive access for plural application processes to the shared resources via a multitask type computer. CONSTITUTION: The application processes 41, 42...4m have no direct accesses to the resources 31, 32...3n respectively and ask a resource management process 1 managing these resources to have accesses to them. If the accesses are impossible and the access requested resources are occupied by other application processes, these accesses are registered in the queue of a waiting process register table file 5 and wait for their orders. If the accesses are impossible by another reason, this reason is notified to the application process of the requester.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a resource management device for a multitasking computer.

[0002]

2. Description of the Related Art When a plurality of application processes access a resource such as a disk or a memory, for example, while another application process is writing data to another resource, another application process may access the same resource. It is necessary to establish exclusive access between the programs of the application process so that data will not be read. Therefore, when there are simultaneous access from application processes that exceed the number of accesses permitted for one resource, exclusion must be taken to limit the number of application processes that can be accessed simultaneously.

Therefore, conventionally, in a multitasking computer, on / off of a bit of a memory is used, and exclusion is performed depending on the presence or absence of a file.

[0004]

However, such a conventional resource management device has the following problems.
In large systems, multiple designers often work together to build a system, but each designer may use a different method for exclusion. If different exclusive methods are adopted in the same system, there is a problem that management of the entire system becomes complicated and maintenance becomes difficult. There is also a problem that the programming work becomes complicated even in the design stage, and the burden on the programmer increases. In addition, in the system operation test, if an application process mistakenly accesses another resource due to a design error, it may destroy irrelevant data and delay the test of the entire system. It can happen.

The present invention has been made in view of such conventional problems, and reduces the burden on the programmer at the design stage, and when a plurality of application processes access requests for one resource at the same time. An object of the present invention is to provide a resource management device capable of managing access to resources including exclusion so that exclusion can be surely obtained.

[0006]

According to a first aspect of the present invention, in a resource management apparatus of a multi-tax system for accessing a plurality of application processes to each of a plurality of resources and performing desired processing, any one of the plurality of application processes is used. Resource access means for accessing any of the plurality of resources, process interaction means for interacting with each of the plurality of application processes, which application process is accessing which resource, which application process is accessing which resource Refers to the resource management table for registering the exclusivity of each resource, whether it is accessible or not, and the resource management table when an access request is made to any resource from any application process by the process interaction means. do it Access determination means for determining whether or not access is possible and access waiting, a waiting process registration table for registering the contrast between the application process waiting for access and the resource that is the target of access, and the access determination means for determining access waiting When the access is performed, the contrast between the application process waiting for the access and the resource that is the target of the access is sequentially registered in the process registration table, and when the access release of the application process for the resource is registered in the waiting process registration table. Waiting process registration means for executing an application process that is waiting for access to the corresponding resource, and arbitration between each means,
It is provided with a control means for controlling.

[0007]

According to the resource management apparatus of the present invention, when a plurality of resources are accessed from a plurality of application processes in a multitasking computer, first,
Which application process can access or cannot access which resource in the resource management table, information on the exclusivity of each resource is registered in advance, and which application process is accessing which resource Information is also registered one after another.

When the process interaction means recognizes that an access request has been made to any resource from any application process, the access determination means refers to the resource management table and applies the relevant resource to the relevant resource. It is determined whether the application process is accessible or not, whether another application process is already accessing it, or the like.

(I) If the determination is that access is possible, then the resource access means causes the application process to access the corresponding resource.

(Ii) When the above determination is accessible, but at the same time it is determined that another application process is accessing the corresponding resource, or the waiting process table is referred to, and the same resource is accessed first. If it is determined that another application process waiting for access is registered, the wait registration for access to the resource by the application process is added to the waiting process registration table, and the access to the resource by the application process is added. Wait until the application process that is currently accessing or the waiting application process releases the resource.

(Iii) If the above-mentioned determination is that access is not possible, the process interaction means rejects access to the resource corresponding to the application process.

In this way, when a plurality of resources are accessed by a plurality of application processes in the multitasking method, reliable resource access management is performed so that the resources that are mutually exclusive between the application processes are not simultaneously accessed.

[0013]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 shows a functional block diagram of an embodiment of the present invention. In the resource management apparatus of this embodiment, each of a plurality of application processes accesses any one of a plurality of resources to read or write data. Resource management process 1 that manages loading, resource management table file 2 that registers the access status of resources, resources 31, 32, ... Application processes 41, 4
2, ..., 4 m, and a waiting process registration table file 5 for registering a queue of an access waiting process. The resource management process 1 is composed of a process dialogue unit 11, an access determination unit 12, a waiting process registration unit 13, a resource access unit 14, and a control unit 15 that controls and controls them.

The process interaction unit 11 functions to receive an access request for each of the resources 31 to 3n from each of the application processes 41 to 4m and return a resource access response or access result to each of the application processes. However, if there is a defect in the parameter of the resource access request, the application process is immediately notified and the subsequent processing is not performed.

When an access request is made from any one of the application processes 41 to 4m to any one of the resources 31 to 3n, the access judging unit 12 applies the resource management table file 2 for managing the access of the resource from the corresponding application process. Access to the resource to be accessed is referred to, and if it is accessible, a flag indicating that the resource is occupied is set in the resource management table file 2, and the application process that requested access To allow that access to.

In the resource management table file 2,
It describes the resource type, resource number, the number of application processes that are permitted to access, the number of simultaneous accesses, and the number of application processes currently being accessed. Here, the resource numbers are resources 41, 42,
..., 4n are respectively labeled as 1, 2, 3, ..., n, and application processes 31, 32, ..., 3
It is assumed that each m is attached with 1, 2, 3, ..., M, and these are registered in advance in the resource management table file 2 before operating the system.

The waiting process registration unit 13 functions to manage application processes waiting for resource access,
When the access determination unit 12 determines that the access to a certain resource is impossible to the application process that newly requests access because the access to the certain resource is occupied by another application process, It is additionally registered in the waiting process registration table file 5 having a queue structure to wait for access. Then, if another application process that has occupied access to the resource so far releases the resource and can access the resource, it is registered at the head of the queue of the waiting process registration table file 5. Reads the specified application process and grants access to the corresponding resource.

The resource access unit 14 accesses the resource for which the access is permitted and receives the response.

The control unit 15 plays a role of calling or inquiring about each of these units 12 to 14.

Next, the operation of the resource management device having the above configuration will be described with reference to the flow charts of FIGS. 4m does not directly access the resources 31, 32, ..., 3n, but requests access to the resource management process 1 that manages these resources. If access is impossible and the resource of the access request destination is occupied by another application process, it is registered in the queue of the waiting process registration table file 5 to wait for access. If the reason for inaccessibility is any other reason, the reason is notified to the requesting application process. The above processing is executed in the following procedure.

When the process dialogue unit 11 receives a resource access request from any of the application processes 41, 42, ..., 4m (step S1), the resource to be accessed, the resource number, the application process number of the access request, the command, and the data. It is determined whether the parameters such as the address are correct (step S2), and if the parameters are correct, those parameters are passed to the control unit 15 (step S3). If the parameters are not correct, an error is returned to the application process (step S4).

The control unit 15 receives a correct parameter from the process interaction unit 11, passes the same parameter except the command and the data address to the access determination unit 12, and inquires whether access to the resource to be accessed is permitted ( Step S5), access determination unit 1
In step 2, the resource management table file 2 is referenced to determine whether the access is possible or not and whether it is occupied by another application process (step S6).

If it is determined that the access is possible (step S7), the control unit 15 transfers the type of resource, the resource number, the command, the address, and the data for which the access request is made to the resource access unit 14 (step S8). ), The resource access unit 14 accesses the corresponding one of the resources 31, 32, ..., 3n to obtain its response, and the resource access unit 14 sends the response from the obtained resource through the process dialogue unit 11 to the request source. To the application process (steps S9 to S11).

Thereafter, the control unit 15 registers the release of the occupancy of the corresponding resource in the resource management table file 2 through the access determination unit 12 (steps S12 to S14), and at the same time, the waiting process registration unit 13 recognizes the released resource. It is inquired whether or not the application process waiting for access is registered (step S15). Here, if the application process waiting for access is registered in the queue of the waiting process registration table file 5 (YES branch at step S16), the steps after step S8 are repeated to access the resource of interest. Access to all waiting application processes is sequentially repeated (steps S8 to S1).
6). If there is no application process waiting for access to the same resource, the first step S1
Return to the work from (branch to NO side in step S16).

When the application process cannot access the resource requested to be accessed by the determinations in steps S6 and S7, and the reason is occupied by another application process (step S6).
7, S17), the control unit 15 notifies the waiting process registration unit 13 of the application process number and its parameters (step S18), and the waiting process registration unit 13 transfers the received application process information to the waiting process registration table file 5. Additional registration (step S
19).

When the occupancy of the corresponding resource is released, steps S12 and thereafter are executed to sequentially release the occupancy of all application processes registered in the waiting process registration table file 5. To access (steps S19, S1, S
12-S16).

When the application process cannot access the resource requested to be accessed by the determination in steps S6 and S7 described above, and the reason is that the resource is not occupied by another application process (S
In 17), the process branches to the NO side) and returns to the requesting application process as an error (step S20).

Next, a more specific embodiment of the present invention will be described with reference to FIGS. 1 and 5-8. The resource management system of this embodiment is applied to a parts inventory management system for managing a wide variety of parts inventory. The resource management process 1 has the functional configuration shown in FIG. 1, and is a component input / output process 41 as an application process.
A magnetic disk (registered as a process number a), a component registration process 42 (denoted as a process number b), and a component information search process 43 (denoted as a process number c), which register the component master file 31 as a resource ( Resource number 1), a magnetic disk for registering the parts inventory file 32 (referred to as resource number 2), an internal memory 33 (referred to as resource number 11) for registering parts master data, and other resource numbers 12, 13, Equipped with 14 internal memories. It should be noted that the component master file 31 and the component inventory file 32 are not registered in separate magnetic disks here, but are files registered in separate common magnetic disks with different names, and each of these files is a resource. They are numbered. Similarly,
The internal memory is not separate for each resource number 11, 12, ..., The resource number is assigned to each file registered in the area of the memory having a different address.

Before running this system, it is necessary to determine the process number of each application process and register the number of the application process to be accessed for each resource as the access permission process of the resource management table file. FIG. 6 shows an example of initial registration of the resource management table file 2, but here, as described above, the process number a of the component input / output process 41,
The process number b of the component registration process 42 and the process number c of the component information search process 43 are set, and the resource number 1 of the component master file 31 and the component inventory file 3 are set.
Resource number 2 of 2 and resource number 1 of parts master data 33
It is set to 1.

In the resource management table file 2, a component registration process 42 (process number b) and a component information search process 4 are available as application processes that can access the component master file 31 (resource number 1).
3 (process number c) is set, and similarly, a, b, c are set as the application processes accessible to the component inventory file 32 of resource number 2 only by the process number, and the component of resource number 11 is set. Process numbers b and c are set as application processes that can access the master data 33. Note that the "number of simultaneous accesses" is set to indicate the exclusivity of any of these resources, but in this registration example, only one application process is used. In addition, since no resources are accessed by any application process in the initial registration,
In the "accessing process" column, "-1" is set as a flag indicating that the process is not occupied.

The parts loading / unloading process 41 (process number a) is executed by the parts inventory file 3 in response to a request for loading / unloading parts.
The process of rewriting the contents of 2 is performed. Parts registration process 42
The (process number b) registers the component data in the component master file 31 and secures a storage area in the component inventory file 32. The component information retrieval process 43 (process number c) retrieves the component master file 31 and the component inventory file 32 to perform a process of examining the component data and inventory.

Now, while the worker is leaving the parts,
The operation when another operator makes a part registration and makes a part information inquiry will be described below. When receiving instructions from workers,
The parts loading / unloading process 41 confirms the stock in the parts inventory file 32. That is, the stock quantity is read. At this time, the process dialogue unit 11 in the resource management process 1 receives the access request and passes it to the control unit 15, and the control unit 15 inquires of the access determination unit 12 whether or not the parts inventory file 32 can be accessed. Resource management table file 2
6 is in the initial registration state shown in FIG. 6, the access requesting part loading / unloading process 41 (process number a) is registered as accessible to the parts inventory file 32 (resource number 2), and the parts inventory is Since there is no other application process that is accessing the file 32 (accessing process flag = −1), the access determination unit 12 sets the accessing process flag = 1 (occupied) of the component inventory file 32 to permit access. To do. As a result, the contents of the resource management table file 2 will be rewritten as shown in FIG. 7 (in the figure, the flag rewritten from -1 to 1 is marked with a circle for convenience and is shown easily. Available).

Upon receiving the access permission from the access determination unit 12, the control unit 15 reads the stock quantity from the parts inventory file 32 through the resource access unit 14 and returns the data to the parts loading / unloading process 41 through the process dialogue unit 11.

If it is necessary to register a new part, the part registration process 42 (process number b) registers the part master file 41 and then reserves a storage area in the part inventory file 42. There is a need.
The content of this access request is passed from the process dialogue unit 11 in the resource management process 1 to the control unit 15, and the control unit 15 inquires the access determination unit 12 here. At this time, if the resource management table file 2 is in the state shown in FIG. 7, the component inventory file 32 (resource number 2) is occupied by another application process, that is, the component loading / unloading process 41 (accessing process flag = Since it is 1), the response of occupation is returned from the access determination unit 12. Therefore, the control unit 15 determines that it is necessary to wait for access, sends the content of the access request to the waiting process registration unit 13, and the waiting process registration unit 13 additionally registers the waiting process registration table file 5 and the parts inventory file 32.
It waits until the occupation of (resource number 2) is released and it becomes accessible.

Similarly, while the parts inventory file 32 (resource number 2) is being accessed by the parts loading / unloading process 41, an access request for inquiring parts information from the parts information retrieval process 43 (process number c) is sent to the parts inventory file 32. Also, even if there is a reply, it is additionally registered in the waiting process registration table file 5 as a waiting process.

FIG. 8 shows a state in which the above-mentioned two waiting processes are registered in the waiting process registration table file 5, and the first is resource number 2 (parts inventory file 32).
Process number b (parts registration process 42) is waiting for access for writing, and process number c (parts information retrieval process 43) is secondly read for the same resource number 2. It can be seen that it is waiting for access.

After this, the parts loading / unloading process 41, which has accessed the stock parts file 32 (resource number 2) to obtain the stock quantity, subtracts the quantity of the stocked parts and writes new data to the stock parts file 32, The process ends.
As a result, it is no longer necessary to occupy the parts inventory file 32 and the occupancy is released. As a result, the resource management table file 2 returns from the state shown in FIG. 7 to the state shown in FIG. 6, which is the initial state, and the in-access process flag of the component inventory file 32 (resource number 2) =-1 (not occupied). .

When any resource is released, the control unit 1
Reference numeral 5 inquires of the waiting process registration unit 13 whether or not there is an application process waiting for access. When the waiting process registration unit 13 receives this inquiry, the waiting process registration table file 5 is searched. However, since the process number b (component registration process 42) is registered first in the waiting process here, the access determination unit 12
Request access judgment to give access permission to. Then, a storage area is secured in the parts inventory file 32 through the resource access unit 14, and then the occupation of the file is released. If you get permission for this waiting process,
The registration of the component registration process 42 (process number b) is deleted from the waiting process registration table file 5, and the waiting process, process number c, which has been secondly registered until then, is moved up to the first.

When the occupation of the file is released, the control unit 15 inquires the waiting process registration unit 13 again whether there is an application process waiting for access. And the process number c is still waiting
Since (Parts Information Search Process 43) is registered,
Next, this process 43 obtains access permission to access the parts inventory file 32.

Thus, in the resource management system of the above embodiment, the application processes 41, 42, ..., 4m
3n does not directly access the resources 31, 32, ..., 3n, but requests access to the resource management process 1 that manages these resources. When the resource of the request destination is occupied by another application process, it is registered in the queue of the waiting process registration table file 5 and the order of access is waited. By notifying the requesting application process, when access is concentrated on a specific resource due to a large number of application processes, designers who are not skilled in designing can easily and reliably exclude resource access. You will be able to take advantage of it.

[0041]

As described above, according to the invention of claim 1,
Rather than having each of multiple application processes directly accessing each of multiple resources, request access to the resource management device that manages these resources. If access is impossible, request access. When the previous resource is occupied by another application process, register it in the queue of the waiting process registration table file, wait for access,
If the reason for the inaccessibility is any other reason, the requesting application process is notified of the reason. Therefore, when a large number of application processes concentrate access to a specific resource, they are proficient in design. Even a designer who does not have one can easily and surely obtain exclusive access to a resource, and surely obtain an exclusive access to one resource by a plurality of application processes, so that a malfunction of the system can be prevented in advance. become able to. It also saves programming time during the design phase, and when you debug your system's application processes, you will be immediately aware of any attempt to access the wrong resource, reducing system test time. Furthermore, at the time of maintenance, a person other than the designer can easily find out if he / she has access to the wrong resource. Therefore, productivity is improved and maintainability is also improved.

[Brief description of drawings]

FIG. 1 is a functional block diagram of an embodiment of the present invention.

FIG. 2 is a front part of a flowchart of the operation procedure of the above embodiment.

FIG. 3 is a middle section of a flowchart of the operation procedure of the above embodiment.

FIG. 4 is a latter part of the flowchart of the operation procedure of the above embodiment.

FIG. 5 is a functional block diagram of an embodiment applied to the parts inventory management system of the present invention.

FIG. 6 is an explanatory diagram showing an example of initial registration of a resource management table in the above embodiment.

FIG. 7 is an explanatory diagram showing an example of registration of a resource management table in the above embodiment.

FIG. 8 is an explanatory diagram showing a registration example of a waiting process registration table in the above embodiment.

[Explanation of symbols]

 1 resource management process 2 resource management table file 5 waiting process registration table file 11 process dialogue unit 12 access determination unit 13 waiting process registration unit 14 resource access unit 15 control unit 31, 32, ... 3m application process 41, 42, ..., 4n resources

Claims (1)

[Claims] 1. A resource management apparatus of a multi-tax system that allows a plurality of application processes to access a plurality of resources to perform desired processing, and allows any one of the plurality of application processes to access any one of the plurality of resources. Resource access means, process interaction means for interacting with each of the plurality of application processes, which application process is accessing which resource, which application process is accessible or inaccessible to which resource Alternatively, a resource management table for registering the exclusivity of each resource and a reference to the resource management table when an access request is made to any resource from any application process by the process interaction means Access determination means for determining whether or not access is allowed and access waiting, a waiting process registration table for registering a contrast between an application process waiting for access and a resource to be waited for access, and the access determination means for determining whether access is waiting When this happens, the contrast between the application process waiting for the access and the resource to be the target of the access is sequentially registered in the process registration table, and when the access release of the application process to the resource is registered in the waiting process registration table. A resource management apparatus comprising waiting process registration means for executing an application process waiting for access to a corresponding resource, and control means for arbitrating and controlling the means.