JPH0651999A - Information processing system with resource exclusive control function - Google Patents

Abstract

PURPOSE:To provide an information processing system capable of executing an operation at high speed when the exclusive control of resource is performed by using a function provided by an operating system OS. CONSTITUTION:The information processing system equipped with one or <=2 resources used by a multitask OS 2 and each task is provided with a resource exclusive control function to perform the exclusive control of the resource under the environment of the multitask OS 2. Also, it is provided with a resource acquisition waiting managing means (resource managing table 16), a resource acquisition control part 12, and a resource release control part 13 which receives the release request of the resource from the task and requests the restart of the task set in a waiting state to the OS 2 corresponding to a resource acquisition waiting state managed by the resource acquisition state managing means. Also, a semaphore function is used in the waiting of the task. The resource acquisition control part 12 can be provided with a function to dynamically allocate the semaphore to be used. Since the semaphore is dynamically allocated, it is possible to reduce an area as a table set by the OS with the minimum number of semaphores.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing system for performing multitask processing, and more particularly to a multitask OS.
The present invention relates to an information processing system having a resource exclusive control function using a function provided in the.

[0002]

2. Description of the Related Art In the current OA (office automation) field, various information processing devices such as workstations and facsimiles are used. For example, facsimiles, which can deliver documents immediately, have become an indispensable device in offices. This facsimile is a telephone network G that sends a document in a few tens of seconds to a minute.
Three aircraft are widespread with about 4 million units.

Also, instead of the conventional public telephone network, ISDN (Integrated Services Digital Network) capable of communicating data in digital binary form.
Has been maintained. This ISDN provides various communication services such as voice, image and data by a unified interface, and a basic interface and a primary group interface have been put into practical use. Of these, the basic interface is 64 Kbps (bits per sec) on one subscriber line.
It has two ond) information transmission channels and one 16 Kbps control channel.

Under the influence of the establishment of such an infrastructure, G4 machines which can be connected to a digital network such as ISDN have attracted attention. This device can send one A4 original in a few seconds, and 400 × 400ppi (pels
Per-inch) high-definition image communication can be realized.

Many of these facsimiles are provided with a storage device such as a memory for temporarily storing the image data read by the scanner, and are provided with a broadcast transmission function for sequentially transmitting the stored image data to a plurality of destination facsimiles. .
Further, there is also an apparatus having a multi-access function for dividing a facsimile function into a job of reading a memory of a transmission original document, printing of a memory reception original document, memory communication, and the like, and executing the jobs in parallel. According to this multi-access function, the next transmission original can be read by the scanner and stored in the memory while the image data stored in the memory is being transmitted, the received image data is being stored in the memory, or the image data stored in the memory is being printed. It becomes possible to shorten the transmission waiting time. In addition, there is also an apparatus characterized by a multi-line communication control function of simultaneously communicating with a plurality of destination facsimiles by using two ISDN information transmission channels and a plurality of lines.

In the above apparatus, various processes (jobs) realized by software are divided into optimum units called tasks, and each task having an execution priority is operated in parallel under the environment of a multitasking operating system (OS). , Multi-task processing is being performed. In order to realize the multi-access function and the multi-line communication control function under the environment of the multi-task OS, it is necessary to exclusively control the hardware resources such as the scanner, the printer and the communication control device which are commonly used among the tasks. In addition, exclusive control of various control tables is also essential. For example, according to a device having a one-touch dial or speed dial function for transmitting to a destination facsimile registered in advance, the telephone number of the destination facsimile already stored in correspondence with the one-touch or speed dial number already reserved for transmission is stored. If changed, the reserved document will be sent to a different destination. Therefore, by mutually excluding each registration table corresponding to each one-touch or speed dial number, when one task is using the registration table, another task must be controlled not to use the registration table.

Such exclusive control of resources is not limited to facsimiles, and other OA for performing multitask processing is performed.
It is also necessary in equipment such as an information processing device such as a workstation.

For exclusive control of resources, there is a method of utilizing a semaphore function provided by the OS. A semaphore consists of status information and a task queue. The task occupying the resource requests the OS to acquire the semaphore. The OS that has received the semaphore acquisition request refers to the status, and if the semaphore is used by another task, it connects the task that issued the semaphore acquisition request to the queue and starts another executable task. Further, the task for releasing the resource requests the OS to release the semaphore. Upon receiving the semaphore release request, the OS refers to the queue and, if there is a task waiting to acquire the semaphore, activates the task at the head of the queue. Normally, O is used to exclusively control various resources.
S is capable of managing a plurality of semaphores, and identifies each semaphore by information called a semaphore number.

The exclusive control of resources is disclosed in Japanese Patent Laid-Open No. 63-24441.
It is also possible to use an event flag function that executes a synchronization process between tasks by changing the flag, as described in the publication.

FIG. 8 is a task sequence showing a conventional resource exclusive control system using the semaphore function provided by the OS, and the horizontal axis shows time.

In FIG. 8, it is assumed that tasks A and B share the same resource, and that task B has a higher priority than task A. First, task A requests semaphore acquisition for resource acquisition (). The OS confirms that the semaphore is unused, acquires the semaphore, and then performs task A
Restart (). After a lapse of a certain time, a factor of task switching occurs (), the OS suspends the execution of the task A, and then activates the task B having a higher priority. Task B
Starts activation and requests semaphore acquisition for resource acquisition (). After confirming that the semaphore is being used by another task, the OS connects task B to the semaphore queue and suspends execution. Then, the task A whose processing has been suspended is restarted (). When the task A completes the processing, it requests the semaphore release to release the resource (). The OS removes the task B waiting for the acquisition of the semaphore from the queue, acquires the semaphore for the task B, and then resumes execution (). When the task B finishes the processing, it requests the semaphore release to release the resource (). O
Since S does not have a task waiting for a semaphore, task B having a higher priority is restarted ().

[0012]

In general, a real-time multitasking OS has a task management function such as task generation, activation, termination, suspension, resumption, periodic activation using a timer, and designated time activation in addition to a semaphore function. The system has an event flag function that manages the occurrence of an event with a flag and executes a synchronization process between tasks according to a change in the flag, a mailbox function that executes message communication between tasks, and the like.

In order to realize such various functions, the multitask OS is a CPU that manages executable tasks.
It has a queue and a dispatcher unit that determines a task to be executed. For example, when a semaphore acquisition request is issued, the task is connected to the semaphore acquisition queue, then the task is transferred to the dispatcher unit, and a task with a high priority is selected from the tasks in the CPU queue and executed. When a semaphore release request is issued, the task in the semaphore acquisition queue is reconnected to the CPU queue, and then the process proceeds to the dispatcher unit to select and execute a task with a high priority from the tasks in the CPU queue. Similarly, the event flag and the mailbox function have queues for each function, and the dispatcher unit determines the task to be actually executed.

As described above, the semaphore acquisition or release function is composed of status update processing for each semaphore, semaphore acquisition queue reconnection processing, and dispatcher processing.

The dispatcher process takes a long processing time because it retrieves the task with the highest priority from the tasks existing in the CPU queue and puts it into execution. For example, consider the case where a task requests acquisition for a semaphore that is not used by another task. At this time, since the semaphore can be acquired, control should be immediately returned to the task that requested it.
It is queued and put into execution via the dispatcher section. In this way, when a request for acquisition or release of a semaphore is made, the dispatcher process is always executed, so a delay time of about several hundred microseconds occurs until control is returned to the task.

The delay time of this processing must be minimized because the dead time becomes large as a whole when there are many such tasks. For example, in a facsimile, the processing delay time is reflected in the communication time, which may increase the communication charge burden on the user. Therefore, the processing delay time must be minimized.

If there are many resources that need exclusive control,
If different semaphores are assigned to all the resources that need exclusive control, there is a problem that a large capacity memory area is required as a control table for managing the semaphores. For example,
Some facsimile machines have several hundred one-touch or speed dial registration tables depending on the specifications of the machines, and require a large-capacity memory area as a control table for managing semaphores.

A first object of the present invention is to provide an information processing system capable of executing resource exclusion control at high speed when implementing the resource exclusion control using the function of the OS. is there.

A second object of the present invention is to provide an information processing system capable of executing resource exclusive control without requiring a large capacity memory area for semaphore management.

[0020]

In order to achieve the first object, according to the present invention, a multitasking OS (operating system) and a task used by each task 1
Alternatively, in an information processing system provided with two or more resources, an information processing system provided with a resource exclusion control function for exclusively controlling resources under the environment of a multitasking OS is provided.

The resource exclusive control function receives the resource acquisition waiting state management means for managing the resource acquisition waiting state and the resource acquisition request from the task, and responds to the resource acquisition waiting state managed by the resource acquisition waiting state management means. A resource acquisition control unit that requests the OS to shift to a task wait state,
A resource release control unit that receives a resource release request from a task and requests the OS to restart the wait state task according to the resource acquisition wait state managed by the resource acquisition wait state management unit. .

The resource acquisition control unit may have a function of receiving a resource acquisition request from each task and requesting the OS to acquire a semaphore. Also,
The resource release control unit may have a function of receiving a resource release request from a task and requesting the OS to release the semaphore.

The resource acquisition waiting state management means may have a resource management table in which table elements corresponding to the number of resources that need exclusive control are arranged.
Here, each table element includes a resource identifier storage area that stores an identifier for identifying a resource, a wait task counter storage area that stores a wait task counter that stores the number of tasks in the resource acquisition wait state, and a resource acquisition wait It can be configured to have a wait semaphore identifier storage area for storing the identifier of the semaphore used for.

The resource exclusive control function is provided by linking to the resource acquisition control unit, and is provided by being linked to the semaphore allocation unit for allocating the semaphore to be used and the resource release control unit for releasing the semaphore used. And a semaphore management table that manages the usage status of the semaphore. Here, the semaphore management table is provided at least for each resource acquisition request that may occur at the same time, and as many table elements as the acquisition request number are arranged. Each table element can be configured to have a semaphore identifier storage area for storing a semaphore identifier and a semaphore status storage area for storing a semaphore status. The semaphore identifier storage area stores the semaphore identifier managed by the OS in advance. For example, a semaphore number is used as the semaphore identifier.

In order to achieve the second object, according to the present invention, a multitask OS (operating system) and one or more resources used by each task are provided, and Provided is an information processing system equipped with a resource exclusion control system that exclusively controls resources using a semaphore function in an environment.

The resource exclusive control system includes a resource acquisition waiting state management means for managing a resource acquisition waiting state, and a management means for managing a number of semaphores corresponding to the number of resource acquisition requests that may occur at the same time. From the semaphore managed by the management means upon receiving a resource acquisition request,
The semaphore dynamically allocating means for dynamically allocating the semaphore to be used and the semaphore releasing means for releasing the used semaphore in response to the resource release request can be configured.

The semaphore management means may be configured to have a semaphore management table which is provided for at least resource acquisition requests that may occur at the same time and in which a number of table elements corresponding to the number of acquisition requests are arranged. . Here, each table element can be configured to have a semaphore identifier storage area for storing a semaphore identifier and a semaphore status storage area for storing a semaphore status. The semaphore identifier storage area stores in advance the semaphore identifier managed by the OS.

As described above, the resource acquisition waiting state management means has a resource management table in which table elements having a resource identifier storage area, a wait task counter storage area, and a wait semaphore identifier storage area are arranged. Can be

The semaphore dynamic allocation means searches for an empty semaphore identifier, and when an empty semaphore identifier is detected,
The semaphore identifier can be assigned as a semaphore for the resource, and the semaphore identifier can be stored and registered in the wait semaphore identifier storage area.

Further, according to the present invention, a multitasking OS
In an information processing system including an (operating system) and one or more file resources used by each task, a resource exclusion control function for exclusively controlling file resources under the environment of a multitasking OS, and management of file resources An information processing system including a file management unit that performs

The resource exclusive control function receives the resource acquisition waiting state management means for managing the resource acquisition waiting state and the resource acquisition request from the task, and responds to the resource acquisition waiting state managed by the resource acquisition waiting state management means. A resource acquisition control unit that requests the OS to shift to a task wait state,
A resource release control unit that receives a resource release request from a task and requests the OS to restart the wait state task according to the resource acquisition wait state managed by the resource acquisition wait state management means.

When the file management unit receives a write or read processing request in a file non-occupancy state, it requests the resource acquisition control unit to acquire a file resource, and after executing the write or read processing, It has a function of requesting the resource release control unit to release the file resource. Therefore, the file management unit has a function of receiving a write or read processing request in the file non-occupancy state and a resource acquisition control unit when receiving the write or read processing request in the file non-occupancy state. A function for requesting acquisition of a file resource, a function for executing a writing or reading process for a file after acquiring the file resource, and a function for executing a writing or reading process for the file It can be configured to have a function of requesting release.

[0033]

According to the present invention, in an information processing system provided with a multi-task OS (operating system) and one or more resources used by each task, the resource exclusion control function allows resources to be processed under the environment of the multi-task OS. Exclusive control of.

The resource exclusive control function manages the resource acquisition waiting state by the resource acquisition waiting state management means. Management is done using semaphores. The semaphore may be either fixedly allocated for resource correspondence or dynamically allocated as needed without fixing the correspondence relationship with the resource. According to the former, the procedure for allocating and releasing the semaphore is not required, and the speed can be increased accordingly. On the other hand, according to the latter, it is not necessary to provide as many semaphores as the number of resources, so that the storage capacity can be suppressed. In the latter, the number of semaphores actually required is the maximum number of resource acquisition requests that can occur at the same time, and even if different semaphores are assigned to all resources, some semaphores are used at the same time. , It was made with an eye on it. Both can be used together.

The resource acquisition control unit receives a resource acquisition request from the task and requests the OS to shift to the task wait state in accordance with the resource acquisition waiting state managed by the resource acquisition waiting state management means. That is, the resource acquisition control unit receives a resource acquisition request from a task, refers to the wait task counter of the resource acquisition waiting state management means, and only when the resource is used by another task,
In order to shift the task to the wait state, the OS is requested to acquire the semaphore. On the other hand, if the resource requested to be acquired is available, the semaphore is not requested to be acquired.

The resource release control unit receives a resource release request from the task and requests the OS to restart the wait state task in accordance with the resource acquisition wait state managed by the resource acquisition wait state management means. That is, the resource release control unit receives a resource release request from a task and, for example, refers to the wait task counter of the resource acquisition waiting state management means, and waits for a task in the wait state only when another task waits for resource acquisition. Request the OS to release the semaphore. If there is no task waiting for resource acquisition, the semaphore release is not requested. Therefore, it is possible to minimize the delay time of the processing by the OS.

In the present invention, to dynamically assign a semaphore, for example, the following is performed. In the resource acquisition waiting state management means, an identifier for identifying a resource is stored in the resource identifier storage area, a wait task counter for storing the number of tasks in the resource acquisition waiting state is stored in the wait task counter storage area, and , The wait semaphore identifier storage area stores the identifier of the semaphore used for waiting for resource acquisition. Further, as a semaphore management means, a semaphore management table in which a number of table elements corresponding to the number of resource acquisition requests that may occur at the same time are arranged is provided, and the semaphore identifier storage area of this table is managed by the OS. The semaphore identifier to be stored is stored in advance, and the semaphore status is stored in the semaphore status storage area. Further, a semaphore dynamic allocation means is provided, and by this means, a free semaphore identifier is searched for, the free semaphore identifier is detected, and this free semaphore identifier is assigned as a semaphore for the resource, and this semaphore identifier is also used as a wait semaphore identifier. Store and register in the identifier storage area.

As described above, according to the semaphore dynamic allocation of the present invention, it is not necessary for the OS to prepare semaphores corresponding to the number of resources for which exclusive control is required, and at least resource acquisition requests that may occur at the same time. Since a semaphore equivalent to the number is sufficient, the memory area used by the OS as a semaphore control table can be reduced.

The present invention also enables exclusive control of file resources. In this case, the file management unit requests the resource acquisition control unit to acquire a file resource when a write or read processing request is received in a file non-occupancy state, and after executing the write or read processing, the resource management unit Requests the release control unit to release the file resource. Therefore, a task that does not need to occupy a file for a long period of time can request writing or reading of a file without requesting acquisition and release of a file resource.

[0040]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 shows a first information processing system according to the present invention.
1 shows an example of the configuration of a workstation that is an embodiment.

In FIG. 1, the present embodiment shows a main controller (C
PU) 1, a main memory 19 for storing its operation program and data, a display 20, a keyboard 21, and a disk device 22 for reading and writing a hard disk or a flexible disk as main components.

The main memory 19 stores software executed by the CPU 1 to realize various functions, and data used in the execution. That is, a multitask OS 2 that manages the operation of a task configured by software, a display control unit 23 that controls the display 20 and displays image data, and a keyboard 21 that controls operation instructions and data input. The input control unit 24 to perform, a resource acquisition request from each task, and a resource acquisition control unit 12 requesting the OS 2 to acquire a semaphore as needed, and a resource release request from the task, and if necessary A resource release controller 13 that requests the OS 2 to release a semaphore, a semaphore allocator 14 that dynamically allocates a semaphore to be used, a semaphore canceler 15 that cancels a used semaphore, and a write or write operation to a disk device 22. File management unit 18 that controls the reading process
Various programs for realizing the respective function realizing means are stored. Further, the main memory 19 stores management information of each resource, and functions as a resource management table 16 that functions as a means for managing a resource acquisition waiting state, and a means that manages the usage status of a dynamically allocated semaphore. Data that respectively configures the semaphore management table 17, and
Application programs 25, 26, etc. are stored.

The resource acquisition control unit 12 and the resource release control unit 13 are reentrant modules that operate as extensions of tasks. Further, the resource acquisition control unit 12 functions as a means for dynamically allocating a semaphore. A semaphore allocation unit 14 is linked to the resource acquisition control unit 12, and a semaphore cancellation unit 15 is linked to the resource release control unit 13.

Although not shown, a printer, a communication control device, and the like can be connected to the workstation of this embodiment.

FIG. 2 illustrates the configuration of the resource management table 16. As shown in the figure, the resource management table 16 is provided for each resource for which exclusive control is required, and is constituted by sequentially arranging a number of table elements (hereinafter referred to as resource management table elements) 160 corresponding to the number of resources. It Here, in this embodiment, a resource number is used as an identifier for identifying a resource. Further, a semaphore number is used as an identifier for identifying a semaphore used for waiting for resource acquisition.

Resource management table element 1 for a resource
60 is a resource number storage area 16a for storing resource numbers,
Wait task counter storage area 1 forming a wait task counter that stores the number of tasks in the resource acquisition wait state
6b, an information storage area of a wait semaphore number storage area 16c for storing a semaphore number used for waiting for resource acquisition. The resource number storage area 16a stores a resource number previously assigned to each resource. The wait task counter storage area 16b is initialized to "-1", and the wait semaphore number storage area 16c is initialized to "0" indicating that the semaphore number is not registered.

FIG. 3 illustrates the structure of the semaphore management table 17. The semaphore management table 17
A table element (hereinafter referred to as a semaphore management table element) 170, which is provided at least for each resource acquisition request that may occur at the same time and corresponds to the number of acquisition requests, is sequentially arranged. The semaphore management table element 170 for one semaphore is composed of a semaphore number storage area 17a for storing a semaphore number and a semaphore status storage area 17b for storing a semaphore status. The semaphore number storage area 17a stores in advance the semaphore number managed by the OS2. The status storage area 17b is initialized to "0" indicating that the semaphore is unused.

The semaphore function of the OS 2 used in this embodiment is a logical semaphore (or binary semaphore) representing two states of whether it is in use or not. In the case of the present embodiment, the semaphore status of the OS2 is initialized to "in use" before executing the resource exclusive control. It is also possible to use a counting semaphore (or an integer semaphore) capable of realizing an arbitrary number of resource exclusive controls. In this case, the initial value of the semaphore number of OS2 is set to "0".

In this embodiment, the resource acquisition control unit 12, the resource release control unit 13, the semaphore allocation unit 14, the semaphore release unit 15, the resource management table 16, and the semaphore management table 17 are used for resource exclusive control. Realize the function.

When the resource acquisition control unit 12 receives a resource acquisition request from a task, the resource acquisition control unit 12 refers to the resource number in the resource number storage area 16a of the resource management table element 160, and searches for the target resource of the acquisition request. When the resource management table element 160 corresponding to the requested resource is detected, the function of counting up the wait task counter configured in the wait task counter storage area 16b of the detected resource management table element 160 and the count result A function of determining whether or not the resource requested to be acquired is in use, and a function of confirming whether or not the semaphore number is registered in the wait semaphore number storage area 16c if the resource is in use When the semaphore number is not registered, the semaphore dynamic allocation function that dynamically assigns the semaphore and the semaphore If it is or if the semaphore register is a a function of requesting a semaphore acquisition request to the OS2, after the semaphore acquisition, or if the resources not used, and a function of notifying a resource acquisition completion to the task.

The semaphore dynamic allocation function causes the semaphore allocation unit 14 to search for an empty semaphore number, and when the empty semaphore number is searched, the function of allocating this semaphore number as a semaphore for the resource and the semaphore number Is stored in the wait semaphore number storage area 16c and registered.

When the resource release control unit 13 receives a resource release request from a task, the resource release control unit 13 refers to the resource number of the resource number storage area 16a of the resource management table element 160 and searches for the target resource of the release request; When the resource management table element 160 corresponding to the requested resource is detected, the function of counting down the wait task counter configured in the wait task counter storage area 16b of the detected resource management table element 160 and the count result are used. And a function to confirm whether there are tasks waiting to acquire resources to be released, and a function to confirm whether there are multiple tasks waiting to acquire resources when there are tasks waiting to acquire resources to be released. If the number of tasks waiting to acquire resources is 1, the function to release the semaphore number and the task waiting to acquire resources are duplicated. If the case or semaphore number there is released a, a function of requesting a semaphore release request to the OS2, after semaphore release, or, if there is no wait tasks, and a function for notifying the resource release completion to the task.

FIG. 4 is a flow chart showing the operation of the resource acquisition control unit 12 which constitutes this embodiment.

When the resource acquisition control unit 12 receives a resource acquisition request from a task such as the application 25 or 26,
Resource number storage area 16a of resource management table element 160
Then, it is confirmed whether or not the resource is the resource requested for acquisition (step 401). If the resource is different from the resource of the acquisition request, the resource management table element 160 of the next array is referred to (step 402), and in step 401, it is confirmed again whether the resource is the resource of the acquisition request. When the resource management table element 160 corresponding to the resource of the acquisition request is detected in step 401, "1" is added to the wait task counter configured in the wait task counter storage area 16b of the detected resource management table element 160. (Step 40
3).

After that, the resource acquisition control unit 12 confirms whether or not the resource to be acquired is being used by another task (step 404). When software is controlled by the main control unit 1 of a general CPU, if "1" is added to "-1", a carry signal representing a carry is generated. In the resource exclusive control method of this embodiment, the wait task counter is initialized to "-1", so that a carry signal is always generated when the resource to be acquired is not used by another task. On the other hand, when the resource is used by another task, the wait task counter indicates a value of "0" or more, and therefore, a carry signal is not generated even if "1" is added. Therefore, the use status of the resource in step 404 is confirmed by detecting a carry signal as a result of adding the wait task counter.

When the carry signal is not generated in step 404, the resource acquisition control unit 12 determines that the resource to be acquired is used by another task, and next, the wait semaphore number storage area of the resource management table element 160. It is confirmed whether or not the semaphore number is registered in 16c (step 405). If the value of the wait semaphore number storage area 16c is "0", it is determined that the semaphore number is not registered and the semaphore allocating unit 14 is instructed to allocate the semaphore (step 406). When the semaphore assigning unit 14 searches for a free semaphore number, the resource acquisition control unit 12 stores the assigned semaphore number in the wait semaphore number storage area 16c (step 407) and then proceeds to step 408. If the value of the wait semaphore number storage area 16c is other than "0" in step 405, the semaphore number has already been registered, so steps 406, 40.
Without executing 7, the process proceeds to step 408.

In step 408, the resource acquisition control unit 12 uses the registered wait semaphore number to update the OS.
2 is requested to acquire the semaphore, the waiting state is continued until the acquisition is completed, and then the process proceeds to step 409.

On the other hand, when the carry signal is generated in step 404, the resource acquisition control unit 12 determines that the resource to be acquired is not used by another task, and does not execute steps 405 to 408, but step 409. The process is terminated after the completion of acquisition of resources is notified to the task requesting acquisition of resources.

FIG. 5 is a flow chart showing the operation of the resource release control unit 13 of the present invention.

Upon receiving the resource release request from the task, the resource release control unit 13 refers to the resource number storage area 16a of the resource management table element 160 and confirms whether or not the resource is the release request resource (step 501). If it is different from the resource of the release request, the resource management table element 160 of the next array is referred to (step 502), and in step 501, it is confirmed again whether the resource is the resource of the release request. In step 501, the resource management table element 1 corresponding to the resource of the release request
If 60 is detected, "1" is subtracted from the wait task counter of the detected resource management table element 160 (step 503).

After that, the resource release control unit 13 confirms whether or not there is a task waiting to acquire the resource to be released (step 504). When software is controlled by the main control unit 1 of a general CPU, a carry signal representing a carry is generated when "1" is subtracted from "0". When there is no task waiting for resource acquisition, the wait task counter indicates "0", so that a carry signal is generated whenever "1" is subtracted. On the other hand, when there is a task waiting to acquire a resource, the wait task counter indicates a value of "1" or more, and therefore a carry signal is not generated even if "1" is subtracted. Therefore, the confirmation of the resource acquisition waiting task in step 504 is performed by detecting the carry signal as a result of subtracting the wait task counter.

When the carry signal is not generated in step 504, the resource release control unit 13 judges that there are tasks waiting to acquire the resource to be released, and confirms whether or not there are a plurality of tasks waiting to acquire the resource next. (Step 505). If the value of the wait task counter is "0" in step 505, it is determined that there is one task waiting for resource acquisition, and the semaphore canceling unit 15 is instructed to cancel the semaphore (step 506). Semaphore release unit 15
However, when the used semaphore number is released, the resource release control unit 13 stores “0” in the wait semaphore number storage area 16c (step 507), and then the step 50.
Move to 8.

If the value of the wait task counter is "1" or more in step 505, the resource release control unit 13 does not execute steps 506 and 507 because there are a plurality of tasks waiting for resource acquisition, and the step 508 is executed. Move to.

In step 508, the resource release control unit 13 uses the registered wait semaphore number to request the OS 2 to release the semaphore, and waits until the release is completed, and then proceeds to step 509. .

On the other hand, when the carry signal is generated in step 504, the resource release control unit 13 determines that there is no task waiting to acquire the resource to be released, and then the step 50
5 to 508 without executing, go to step 509,
After notifying the task requesting the resource release that the resource release is completed, the processing is terminated.

The confirmation processing of step 404 of the resource acquisition control unit 12 and step 504 of the resource release control unit 13 described above is performed by the wait task counter storage area 1 of the calculation result.
It is also possible to change the processing to refer to 6b. However, in this case, task switching may occur immediately after the calculation of the wait task counter, and the value of the wait task counter may be further calculated by the acquisition request for the same resource from another task, and the wait counter to be referenced may be changed. Conceivable. For this reason, processing (for example, interrupt prohibition processing) that prohibits task switching is required during calculation and reference of the wait task counter.

On the other hand, according to the present embodiment, steps 404 and 50 are executed depending on the carry signal generated as a result of the calculation.
4 confirmation processing is realized. In this case, even if task switching occurs immediately after the calculation of the wait task counter, when the control returns, the carry signal generated as a result of the calculation is
Since it is recovered by 2, there is no need for special processing for prohibiting task switching.

The processing of steps 404 and 504 is not limited to using the carry signal. For example, a zero signal indicating that the calculation result is “0” and a negative signal indicating that the calculation result is negative may be used. In step 404, if the zero signal is not generated, the process proceeds to step 405, and if the zero signal is generated, the process proceeds to step 409 without executing steps 405 to 408. Also, in step 504,
If a negative signal is not generated, the process proceeds to step 505, and if a negative signal is generated, step 50.
Without executing 5 to 508, the process proceeds to step 509.

FIG. 6 is a flow chart showing the operation of the semaphore allocation unit 14 of the present invention.

The semaphore allocation unit 14 instructed by the resource acquisition control unit 12 to allocate the semaphore refers to the status storage area 17b of the semaphore management table element 170 to search for an unused semaphore (step 601). If the status is not "0", the semaphore management table element 170 of the next array is referred to (step 602), and in step 601, it is again confirmed whether or not it is an unused semaphore. If an unused semaphore is detected in step 601, the status storage area 17 of the semaphore number is detected.
A value other than "0" indicating that the semaphore is being used is stored in b (step 603), the semaphore number of the semaphore management table element 170 is notified to the resource acquisition control unit 12, and the processing is ended.

FIG. 7 is a flow chart showing the operation of the semaphore canceling section 15 of the present invention.

The semaphore cancellation unit 15 instructed by the resource release control unit 13 to cancel the semaphore refers to the semaphore number storage area 17a of the semaphore management table element 170 and confirms whether or not the semaphore is a cancellation request (step 701).
If it is different from the release request semaphore, the semaphore management table element 170 of the next array is referred to (step 702), and in step 701, it is confirmed again whether or not the release request semaphore. If the release request semaphore is detected in step 701, the value “0” indicating that the semaphore is an unused one is stored in the status storage area 17b (step 703), and the resource release control unit 13 completes the semaphore release. Is notified and the process ends.

Next, the resource exclusive control operation according to the present embodiment will be described by taking as an example the case where resources are acquired between the tasks A and B.

FIG. 9 shows the conventional task sequence in FIG. 8 executed by the resource exclusive control of this embodiment. In this embodiment, before executing exclusive control of resources,
All the semaphore statuses managed by S are initialized to "in use". Note that task B has a higher priority than task A.

First, when task A requests resource acquisition (a), the resource acquisition control unit 12 causes the resource management table 16
The wait task counter storage area 16b of the corresponding resource management table element 160 is referred to, it is confirmed that the resource is unused, and control is returned to the task A without going through the OS (b). After a lapse of a certain time, a factor of task switching occurs, and the OS 2 suspends the execution of the task A and then activates the task B having a higher priority (c).

Task B starts activation and requests resource acquisition (d). The resource acquisition control unit 12 refers to the wait task counter storage area 16b of the corresponding resource management table element 160, confirms that the resource is being used by another task, and then requests acquisition of a semaphore (e). The OS 2 confirms that the semaphore is being used by another task, connects the task B to the semaphore queue, and restarts the task A whose processing has been suspended (f).

When the task A completes the processing, it requests the resource release (g). The resource release control unit 13 refers to the wait task counter storage area 16b of the corresponding resource management table element 160, confirms that there is a task waiting for resource acquisition, and requests semaphore release (h). O
In S2, the task B waiting for the acquisition of the semaphore is dequeued and the execution is resumed (i).

When the task B finishes the processing, it requests the resource release (j). The resource release control unit 13 refers to the wait task counter storage area 16b of the corresponding resource management table element 160, confirms that there is no task waiting for the resource acquisition, and then controls the task B without going through the OS2. Return (k).

As described above, according to the resource exclusive control operation in the system of this embodiment, the resource acquisition control unit 12 receives the resource acquisition request from the task, and wait resource counter storage area of the corresponding resource management table element 160. 16
If the resource is used by another task with reference to b, the task O
Request S2 to acquire a semaphore. If the resource requested for acquisition is available, do not request acquisition of the semaphore. Further, the resource release control unit 13 receives the resource release request from the task, similarly refers to the wait task counter, and restarts the task in the wait state only when another task waits for the resource acquisition. Request OS2 to release the semaphore. If there is no task waiting for resource acquisition, the semaphore release is not requested. Therefore, in this embodiment, it is possible to minimize the delay time of the processing by the OS.

Further, in the present embodiment, the semaphore allocation unit 14
The semaphore canceling unit 15 dynamically allocates and releases the semaphore. That is, the semaphore allocation unit 14 receives the semaphore allocation instruction from the resource acquisition control unit 12 and dynamically allocates the semaphore to be used, and the semaphore cancellation unit 15 receives the semaphore cancellation instruction from the resource release control unit 13 and uses it. Cancel the semaphore that you did. Here, the dynamic allocation of a semaphore means that the semaphore and the resource are not fixedly coupled, but the semaphore is issued in correspondence with the resource as needed. According to such a control method, it is not necessary for the OS to prepare semaphores corresponding to the number of resources that need exclusive control.

As described above, the resource acquisition control unit 12 of this embodiment requests the OS 2 to acquire a semaphore and releases the resource only when it is necessary to shift the task to the waiting state due to the competition of resources. The control unit 13 uses the OS only when it is necessary to activate a task in the resource acquisition waiting state.
Request 2 to release the semaphore. Exclusive control of resources is an indispensable function in a device that executes a plurality of tasks in parallel, but the probability of resource competition usually is extremely low. According to the conventional exclusive control method, when the resource is acquired or released, the processing by the OS 2 is always delayed. However, according to the exclusive control method of the present embodiment, at the time of acquisition or release without causing resource competition, the intervention of the OS 2 is unnecessary, and it becomes possible to shorten the overall processing time of the device.

Further, since the semaphore allocating unit 14 dynamically allocates the semaphore to be used as needed, it is not necessary to prepare the semaphore corresponding to the number of resources for which the exclusive control is necessary in the OS2, and the semaphore can occur at the same time. OS2 because semaphores equivalent to the number of acquisition requests for resources
It is possible to reduce the memory area used by the semaphore control table.

Further, in the present embodiment, the processing time is reduced by combining the method of requesting acquisition or release of a semaphore according to need with the dynamic semaphore allocation method. It is possible to reduce the processing time in a limited range only by the method. For example, when dynamic semaphore allocation is not performed, semaphores corresponding to the number of resources for which exclusive control is required are prepared in OS2, and different semaphore numbers are set in advance for all wait semaphore numbers in the resource management table element 160, The processes of steps 405 to 407 of the resource acquisition control unit 12 and steps 505 to 507 of the resource release control unit 13 may be removed. If the semaphore acquisition or release request according to need is not executed, the wait task counter storage area of the resource management table element 160 is deleted, and the resource acquisition control unit 12
Steps 403 and 404, and the resource release control unit 1
It suffices to eliminate the processing of steps 503 and 504 of No. 3.

The operation and effect of the resource exclusive control operation of this embodiment described above are the same in other embodiments described later. Also, the semaphore allocation method is the same in other embodiments described later.

Next, a second embodiment of the present invention will be described.

FIG. 11 shows an example of the configuration of a facsimile apparatus which is a second embodiment of the information processing system of the present invention.
The same components as those in the first embodiment are designated by the same reference numerals, and the duplicated description will be omitted.

Referring to FIG. 11, this embodiment is a facsimile apparatus which is connected to a line 7 such as ISDN to transmit and receive images, and stores a main control unit (CPU) 1 and its operation program and data. Main memory 19
A scanner 3 for reading and binarizing a transmission document, a printer 5 for printing image data on recording paper, a communication control unit (NCU) 8 for controlling the line 7, and an image memory 11 for storing image data. It has as a main component.

The main memory 19 stores software and data executed by the CPU 1 to realize various functions. That is, the same OS as in the first embodiment
2, a resource acquisition control unit 12, a resource release control unit 13, a semaphore allocation unit 14, a semaphore release unit 15, a resource management table 16, a semaphore management table 17, and a file management unit 40 are stored. Further, in the main memory 19, as a program for configuring the function realizing means peculiar to the present embodiment, the reading control unit that controls the scanner 3 and compresses the binarized image data, and then stores the compressed image data in the image memory 11. Four
Then, the printer 5 is controlled to decompress the image data stored in the image memory 11, and then the recording control unit 6 for outputting to the printer 5 and the NCU 8 are controlled to execute the communication procedure (protocol) with the destination facsimile. It stores the transmission of the image data stored in the image memory 11, and the communication control units 9 and 10 that store the received image data in the image memory 11.

The file management unit 40 includes a plurality of transmission management tables for storing, for each task, information such as the telephone number of the transmission destination, the position and size of the image data accumulated in the image memory 11, and each transmission management table. , And a transmission queue for connecting in the order of reading by each table address or the like. An external storage device (not shown) such as a memory or a disk device may be connected to the storage device to further control it.

The programs stored in the main memory 19 have a hierarchical relationship. FIG. 12 shows the hierarchical structure of the above program group. In the figure, a resource acquisition control unit 12 and a resource release control unit 13 are present on the multitask OS 2, and a reading control unit 4, a recording control unit 6, a communication control unit 9 and 10, a file management unit 40 is provided. In addition,
Although not shown, the programs of other embodiments can have substantially the same configuration.

The image memory 11 in this embodiment is
Although it is provided separately from the main memory 19, it can be provided as an area in the main memory 19.

Next, the operation of the facsimile apparatus of this embodiment will be described.

In the facsimile apparatus of this embodiment, the original to be transmitted is read by the scanner 3 and the image of the read original is stored in the image memory 11. The images of the stored originals are connected to a queue (transmission queue) in the file management unit 40 in the reading order until the line 7 becomes usable.
Therefore, the transmission management table stores the telephone number of the transmission destination, the position and size of the image data accumulated in the image memory 11, and the like for the document. Further, for each transmission management table, the table address and the like are connected to the transmission queue in the reading order. The transmission queue is shared by tasks such as the reading control unit 4, the communication control unit 9, and the communication control unit 10. However, since each transmission management table is connected by a table address or the like, a task accesses the table address. While another task, if another task changes the table address, malfunction may occur. Therefore, exclusive control is required for the transmission queue.

For example, when the communication control unit 9 or 10 reads the first transmission information from the transmission queue, the resource acquisition control unit 1
2 is requested to acquire the exclusive right to the transmission queue. As described above, the resource acquisition control unit 12 searches the resource management table element 160 (see FIG. 2) corresponding to the transmission queue in steps 401 and 402 shown in FIG. 4, and adds “1” to the wait task counter. Yes (Step 40
3). At this time, since a carry signal is generated from the calculation result (step 404), the resource acquisition control unit 12 proceeds to step 409 and returns the control to the communication control unit 9 or 10. The communication control unit 9 or 10 obtains the exclusive right of the transmission queue and accesses the information of the transmission management table in the file management unit 40.

During this time, when the user sets an original on the scanner 3, the reading control unit 4 reads the original, stores it in the image memory 11, and then requests acquisition of the exclusive right of the transmission queue. The resource acquisition control unit 12, in steps 401 and 402, the resource management table element 1 corresponding to the transmission queue.
60 is searched, and "1" is added to the wait task counter (step 403). At this time, since the carry signal is not generated from the calculation result (step 404), the resource acquisition control unit 12 executes the processing of steps 405 to 408, and causes the OS 2 to shift the reading control unit 4 to the waiting state.

On the other hand, when the communication control unit 9 or 10 finishes the access to the transmission queue, it notifies the resource release control unit 13 of release of the exclusive right to the transmission queue. The resource release control unit 13, as shown in FIG. 5, steps 501 and 502.
In step S503, the resource management table element 160 corresponding to the transmission queue is searched, and "1" is subtracted from the wait task counter (step 503). At this time, since the carry signal is not generated from the calculation result (step 504), the resource release control unit 13 executes the processes of steps 505 to 508, and the OS 2 releases the waiting state of the read control unit 4.

The read control unit 4 obtains the exclusive right of the transmission queue, accesses the information of the transmission management table, and when the access is completed, notifies the resource release control unit 13 of the release of the exclusive right of the transmission queue. In steps 501 and 502, the resource release control unit 13 searches the resource management table element 160 corresponding to the transmission queue and subtracts "1" from the wait task counter (step 503).

At this time, since a carry signal is generated from the calculation result (step 504), the resource release controller 13
Shifts to step 509 and returns the control to the reading control section 4.

As described above, according to the facsimile apparatus of the present embodiment, when the communication control unit 9 or 10 requests the acquisition of the exclusive right to the transmission queue, and when the reading control unit 4 notifies the exclusive right release of the transmission queue, OS2 is unattended,
It is possible to reduce unnecessary overhead.

Next, a third embodiment of the present invention will be described. The present embodiment is an example of an information processing system that exclusively controls file resources. That is, the present embodiment is applied to exclusive control of file resources stored in the disk device 22 in the information processing system shown in FIG. 1, for example. However, the file resource is not limited to the one stored in the disk device 22, and may be a file stored in the main memory 19, a file stored in the image memory 11 or the like.

In the system of this embodiment, in addition to the constituent elements of the resource exclusive control function of the first embodiment, the file management unit 18 has a function of receiving a write or read processing request in the file non-occupancy state, A function of requesting the resource acquisition control unit 12 to acquire a file resource when receiving a request for a write or read process in a file non-occupancy state, and a write or read process for a file after acquiring the file resource And a function of requesting the resource release control unit 13 to release the file resource after executing the writing or reading process.

FIG. 10 is a flow chart showing the exclusive control operation of the file management unit 18 in the embodiment of the present invention.

First, in the information processing system shown in FIG. 1, a case will be described in which the file management control is executed in a state where the file management unit 18 does not have the above-mentioned function.

In this case, a task desiring to occupy a file first requests the resource acquisition control unit 12 to acquire a file resource. After executing the acquisition processing of the corresponding file resource, the resource acquisition control unit 12 notifies the task of a unique access right number that permits access to the file. Next, the task requests the file management unit 18 to write or read the file together with the access right number. The file management unit 18 refers to the input access right number (step 1001), confirms the occupancy state of the resource, and then executes the data writing or reading process for the file (step 1002), and controls the task. Bring back. After confirming the end of the file writing or reading process, the task requests the resource release control unit 13 to release the file resource.

According to such file management control, the task requests acquisition of file resources before requesting file writing or reading processing, and releases the file resources after completion of writing or reading processing. Need to request.

By the way, when writing or reading a file, if the writing or reading process is executed a plurality of times on the same file, the file must be occupied, but if the writing or reading process is executed once. Occupies the file only during processing. Therefore, in the present embodiment, as described above, the file management unit 1
8 is provided with a file management control function in a resource occupied state, so that it is not necessary to acquire and release file resources in a task that does not need to occupy a file for a long period of time.

The task does not request the resource acquisition control unit 12 to acquire the file resource, but requests the file management unit 18 to write or read the file. At this time, "0" indicating that the file is not occupied is notified as an access right number. The file management unit 18 refers to the input access right number (step 1001), confirms the unoccupied state of the resource, and then requests the resource acquisition control unit 12 to acquire the file resource (step 100).
3). Here, the resource acquisition control unit 12 performs resource acquisition control according to the procedure shown in FIG. 4 described above.

After the resource acquisition control unit 12 acquires the corresponding file resource, the file management unit 18 executes a data writing or reading process for the corresponding file (step 1004). After writing or reading the file,
The file management unit 18 tells the resource release control unit 13 that
A request is made to release the file resource (step 1005), and control is returned to the task. Here, the resource release control unit 13 releases resources according to the procedure shown in FIG. 5 described above.

According to the file management control according to the present embodiment, when the writing or reading process for the unoccupied file is requested, the file management unit 18 executes the acquisition and release of the resource. It becomes possible to eliminate the occupancy process.

Further, according to the present embodiment, for example, even when the task B requests the writing or reading process for the file occupied by the task A without acquiring the file resource, the file management unit The file can be protected because the writing or reading process of the task B is put on standby until the task A releases the file resource according to the file resource acquisition request (step 1003) requested by the file 18.

Although the third embodiment is applied to file management in the system of the first embodiment, it may be applied to file management in the system of the second embodiment.

In each of the above embodiments, the resource acquisition control unit 1
2 and the resource release control unit 13 collectively execute contention control for all resources shared by each task. Therefore, the resource management table 16 having an array configuration is provided, and steps 401 to 402 and steps 501 to 502 are provided.
Then, the resource management table element 160 of the corresponding resource is searched. However, the resource acquisition control unit 12 and the resource release control unit 13 are provided for each resource, and the resource acquisition control unit 1 for each resource is provided.
2 and the resource release control unit 13 fixedly allocates the wait task counter to access
The table search processing in steps 1 to 402 and steps 501 to 502 can be eliminated, and the speed can be further increased. In this case, the resource management table element 160
Becomes unnecessary.

Next, a fourth embodiment of the present invention will be described as an embodiment of an information processing system including a resource acquisition control unit and a resource release control unit that perform competition control for each resource.

FIG. 13 shows the construction of a workstation to which the present embodiment is applied, which is equipped with a resource acquisition control section and a resource release control section for competing control for each resource.

In this embodiment, the main control unit (CPU) 1, the main memory 19 for storing its operation program and data, the display 20, the keyboard 21, the hard disk or the flexible disk are read and written in FIG. Disk device (HDD / FD
D) 22 as main components.

The main memory 19 stores software which is executed by the CPU 1 to realize various functions and data used when the software is executed. That is, a multitask OS 2 that manages the operation of a task configured by software, a display control unit 23 that controls the display 20 and displays image data, and a keyboard 21 that controls operation instructions and data input. The input control unit 24, various programs for realizing the respective function realizing means, and the application program 25,
26 and the like are stored. These are constructed similarly to the elements provided in the embodiment shown in FIG.

In the main memory 19, the resource acquisition control unit 27 and the resource release control unit 28, the resource acquisition control unit 30 and the resource release control unit 31, and the resource acquisition control unit 33.
And a resource release control unit 34 corresponding to resources. Furthermore, in response to these, the wait task counter 29,
32, a resource management table 35, a semaphore allocation unit 14,
It has a semaphore management table 17 and a semaphore canceling unit 15.

Although not shown, a printer, a communication control device and the like can be connected to the workstation of this embodiment.

The resource acquisition control unit 27 and the resource release control unit 28 are provided corresponding to a certain resource (for example, resource A) and perform competition control for this. Therefore, the array configuration like the resource management table 16 shown in FIG. 2 is unnecessary. Further, since the resource can be specified, the resource number of the resource management table 16 is not necessary. Further, since the dynamic semaphore allocation is not performed and a specific semaphore (for example, semaphore A) is allocated to the resource A, the resource management table 16
The wait semaphore number of is also unnecessary. Therefore, the resource acquisition control unit 27 and the resource release control unit 28 execute the competition control only by the wait task counter 29 in FIG.

As shown in the flowchart of FIG. 14, when the resource A acquisition request is received from the application program 25 or 26 (step 1401), the resource acquisition control unit 27 increments the wait task counter 29 by "1". , (Step 1402), it is confirmed whether the resource A to be acquired is being used by a task (step 140).
3). If it is being used by another task, it requests the OS 2 to acquire the semaphore A (step 1404), and after waiting the completion of the acquisition, the process proceeds to step 1405. On the other hand, in step 1403, if the resource A is not used by another task, step 14
The process proceeds to step 1405 without executing 04.

Further, as shown in the flow chart of FIG. 15, when a release request for the resource A is received from the application program 25 or 26 (step 1501), the resource release control unit 28 subtracts "1" from the wait task counter 29. After that (step 1502), it is confirmed whether there is a task waiting to acquire the resource A to be released (step 1503). If there is a task waiting to be acquired, the OS
2 to request release of semaphore A (step 150
4) Step 1 after continuing the waiting state until the release is completed
Move to 505. On the other hand, in step 1503,
If there is no task waiting to acquire the resource A, step 1504 is skipped and step 1505 is entered.

Similarly, the resource acquisition control unit 30 and the resource release control unit 31 perform competition control for a certain resource (for example, resource B), so the wait task counter 32
And uses the specific semaphore for the resource B (for example, semaphore B) to request the OS2 to acquire or release the semaphore. Application program 25 or 2
A resource acquisition control unit 3 acquires or releases the resource B.
0 and request to the resource release control unit 31.

Further, the resource acquisition control unit 33 and the resource release control unit 34 dynamically allocate semaphores to individual files in the disk device (HDD / FDD) 22 managed by the file management unit 18 and control the competition. Is to do. Similar to the embodiment shown in FIG. 1 or FIG. 11, the resource management table 35, the semaphore allocation unit 14, and the semaphore release unit 1
5. Using the semaphore management table 17, the semaphore is dynamically assigned and released.

As described above, in the fourth embodiment shown in FIG. 13, a resource acquisition control unit and a resource release control unit are provided for each resource. Therefore, a specific semaphore defined in advance is used for a single resource such as resource A or resource B. Therefore, steps 401, 402, and step 4 of the resource acquisition control units 27 and 30.
05 to 407, and resource release control units 28 and 31
The processes of steps 501 and 502 and steps 505 to 507 of are unnecessary, and the contention control can be speeded up. In addition, this embodiment includes a resource acquisition control unit and a resource release control unit that perform dynamic semaphore allocation. As a result, the storage capacity required for semaphore management is reduced in the case of file management with many resources.

The present invention is not limited to the embodiments described above, but can be applied to all information processing systems that realize exclusive control of resources under the environment of a multitasking OS. That is, the resource exclusive control system of the present invention can be applied to various resources that cause a task to transit to a waiting state when contention occurs. For example, as described above, the present invention can be applied to resource exclusive control in a facsimile machine.
In a facsimile machine, a scanner, printer, communication control device, line, memory, external storage device (HDD, F
Hardware such as a storage area in a DD, an IC card, etc., a job control table for registering information about a job such as a transmission queue or a print queue, a registration table such as a shortening or one-touch dial, an individual file or record in an external storage device In addition, it is possible to regard data or a group of data such as various control tables shared among a plurality of tasks as resources, and perform competitive control by the resource exclusive control method of the present invention.

Further, in the above embodiment, the semaphore function is used as a means for shifting the task requesting the resource acquisition to the wait state, but the event flag function, the mailbox function, the ENQ / DEQ function, etc. provided in the OS can be substituted. Is.

As described above, the present invention can speed up the competition control of various resources shared by a plurality of tasks.

[0129]

According to the present invention, the OS delay is minimized because the OS is requested to acquire or release the semaphore only when the task operating state needs to be changed. It is possible.

Further, when dynamically assigning semaphores to be used as needed, it is not necessary to prepare semaphores corresponding to the number of resources for which exclusive control is required in the OS, and at least resources that may occur at the same time. Since a semaphore equivalent to the number of acquisition requests of the above is sufficient, it is possible to reduce the memory area used by the OS as a semaphore control table.

[Brief description of drawings]

FIG. 1 is a lock diagram showing a configuration of a workstation which is a first embodiment of an information processing system of the present invention.

FIG. 2 is an explanatory diagram of information of a resource management table used in the embodiment of the present invention.

FIG. 3 is an explanatory diagram of information in a semaphore management table.

FIG. 4 is an operation flowchart of a resource acquisition control unit.

FIG. 5 is an operation flowchart of a resource release control unit.

FIG. 6 is an operation flowchart of a semaphore allocation unit.

FIG. 7 is an operation flowchart of a semaphore canceling unit.

FIG. 8 is a task sequence according to the conventional resource exclusive control method.

FIG. 9 is a task sequence according to the resource exclusive control method of the present invention.

FIG. 10 is an operation flowchart of the file management unit in the information processing system according to the third embodiment of the present invention.

FIG. 11 is a lock diagram showing a configuration of a facsimile apparatus that is a second embodiment of the information processing system of the present invention.

FIG. 12 is an explanatory diagram showing a hierarchical structure of software according to the second embodiment of this invention.

FIG. 13 is a lock diagram showing a configuration of a workstation which is a fourth embodiment of the information processing system of the present invention.

FIG. 14 is an operation flowchart of a resource acquisition control unit corresponding to resources in the fourth embodiment.

FIG. 15 is an operation flowchart of a resource release control unit corresponding to resources in the fourth embodiment.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Main control part, 2 ... Multitask OS, 12 ... Resource acquisition control part, 13 ... Resource release control part, 14 ... Semaphore allocation part, 15 ... Semaphore cancellation part, 16 ... Resource management table,
17 ... Semaphore management table, 18, 40 ... File management unit.

Claims (30)

[Claims] 1. An information processing system comprising a multitasking OS (operating system) and one or more resources used by each task. A resource exclusion control function for exclusively controlling resources under the environment of the multitasking OS. The resource exclusive control function includes a resource acquisition waiting state management unit that manages a resource acquisition waiting state, and a resource acquisition request state that is received from a task, depending on the resource acquisition waiting state managed by the resource acquisition waiting state management unit. , A resource acquisition control unit that requests the OS to shift to a task wait state, and a resource acquisition wait state managed by the resource acquisition wait state management means upon receipt of a resource release request from a task. An information processing system, comprising: a resource release control unit for requesting restart of a wait state task. 2. The resource acquisition control unit according to claim 1, which has a function of receiving a resource acquisition request from each task and requesting the OS to acquire a semaphore. , An information processing system having a function of receiving a resource release request from a task and requesting the OS to release a semaphore. 3. The resource acquisition waiting state management means according to claim 2, comprising a resource management table in which table elements corresponding to the number of resources for which exclusive control is required are arranged, and each table element identifies a resource. Resource identifier storage area for storing an identifier for storing resources, a wait task counter storage area for storing a wait task counter for storing the number of tasks in the resource acquisition waiting state, and a wait semaphore for storing an identifier of a semaphore used for resource acquisition waiting. An information processing system having an identifier storage area. 4. The resource exclusive control function according to claim 3,
A semaphore allocator that is linked to the resource acquisition controller and allocates the semaphore to use, a semaphore canceler that links the resource release controller and releases the used semaphore, and manages the usage status of the semaphore An information processing system further comprising a semaphore management table. 5. The semaphore management table according to claim 4, wherein the semaphore management table is provided at least for each resource acquisition request that may occur at the same time, and a number of table elements corresponding to the number of acquisition requests are arranged. A semaphore identifier storage area for storing a semaphore identifier, and a semaphore status storage area for storing a semaphore status, wherein the semaphore identifier storage area stores an identifier of a semaphore managed by the OS in advance. Information processing system. 6. The resource acquisition control unit according to claim 5, upon receiving a resource acquisition request from a task, searches the target resource of the acquisition request by referring to the resource identifier in the resource identifier storage area of the resource management table element. Function and function to count up the wait task counter configured in the wait task counter storage area of the detected resource management table element when the resource management table element corresponding to the acquisition request target resource is detected, and the count result. Function that determines whether the resource requested to be acquired is in use based on the above, and if the resource is in use, a function that checks whether the semaphore identifier is registered in the wait semaphore identifier storage area. When the semaphore identifier is not registered, the semaphore dynamic allocation function that dynamically allocates the semaphore and the semaphore is registered. When a semaphore is registered or a semaphore is registered, it has a function of requesting a semaphore acquisition request from the OS and a function of notifying the task of resource acquisition completion after the semaphore is acquired or when the resource is not used. Information processing system. 7. The semaphore dynamic allocation function according to claim 6, causes the semaphore allocation unit to search for a free semaphore identifier, and when the free semaphore identifier is searched, the semaphore identifier is allocated as a semaphore for the resource. An information processing system having a function and a function of storing and registering this semaphore identifier in a wait semaphore identifier storage area. 8. The function according to claim 6, which determines whether or not the resource requested to be acquired is in use, by detecting a carry signal when the wait task counter is counted up. Information processing system. 9. The wait task counter in the wait task counter storage area according to claim 8, wherein the wait task counter is initialized to "-1", and the function for counting up the wait task counter is
An information processing system that adds "1". 10. The resource release control unit according to claim 6, when the resource release request is received from the task, refers to the resource identifier of the resource identifier storage area of the resource management table element to search for the target resource of the release request. If the function and the resource management table element corresponding to the target resource of the release request are detected, the function that counts down the wait task counter configured in the wait task counter storage area of the detected resource management table element and the count result Based on this, a function to check whether there are tasks waiting to acquire resources to be released, and a function to check whether there are multiple tasks waiting to acquire resources when there are tasks waiting to acquire resources to be released If the number of tasks waiting to acquire resources is 1, there is a function to release the semaphore identifier and there are multiple tasks waiting to acquire resources. If the case or semaphore identifier is released, a function of requesting the semaphore release request to the OS, after semaphore release, or, if there is no wait task,
An information processing system having a function of notifying a task of completion of resource release. 11. The information processing system according to claim 10, wherein the function of confirming whether or not there is a task waiting to acquire a resource to be released is performed by detecting a carry signal when the wait task counter is counted down. 12. The wait task counter in the wait task counter storage area according to claim 11, wherein the wait task counter is "-1".
The function that counts up the wait task counter is
"1" is added, and the function to count down the wait task counter is
An information processing system that subtracts "1". 13. The resource exclusion control function according to claim 2, wherein a resource acquisition control unit and a resource release control unit are provided commonly for a plurality of resources and those provided for each specific resource. Information processing system that has. 14. The resource exclusive control function according to claim 13, wherein the resource acquisition control section and the resource release control section, which are commonly provided for a plurality of resources, require exclusive control as a resource acquisition waiting state management means. A resource management table in which table elements corresponding to the number of different resources are arranged, each table element stores a resource identifier storage area for storing an identifier for identifying the resource, and the number of tasks in the resource acquisition waiting state. An information processing system having a wait task counter storage area for storing a wait task counter to be stored, and a wait semaphore identifier storage area for storing an identifier of a semaphore used for waiting for resource acquisition. 15. The resource exclusive control function according to claim 14, wherein the resource acquisition waiting state management means is configured to set the number of tasks waiting for resource acquisition for the resource acquisition control unit and the resource release control unit provided for each specific resource. An information processing system including one having a wait task counter for counting. 16. The information processing system according to claim 1, wherein the resource acquisition waiting state management means is a wait task counter for counting the number of tasks waiting for resource acquisition. 17. The resource acquisition control unit, the resource release control unit, and the wait task counter according to claim 16,
An information processing system provided for dealing with resources to be exclusively controlled. 18. The function according to claim 17, wherein the resource acquisition control unit counts up a wait task counter when a resource acquisition request is made by a task, and the resource requested to be acquired is used based on the count result. A function to determine whether or not the resource is in use, a function to request a semaphore acquisition request from the OS if the resource is being used, and a task to notify the task of completion of resource acquisition after the semaphore is acquired or when the resource is not used An information processing system having a function to perform. 19. The resource release control unit according to claim 18, wherein when a task releases a resource, the resource release control unit counts down the wait task counter, and based on the count result, the task waiting to acquire the resource to release. If there is a task that waits for acquisition of resources to be released, a function that requests a semaphore release request from the OS, and if there are no wait tasks after releasing the semaphore,
An information processing system having a function of notifying a task of completion of resource release. 20. A file management unit according to claim 1, further comprising a file management unit that has at least a file resource as a resource and manages the file resource, wherein the file management unit writes or reads in a file unoccupied state. A function for receiving a processing request, a function for requesting the resource acquisition control unit to acquire a file resource when receiving a write or read processing request in the unoccupied state of the file, and a function for acquiring a file resource after acquiring the file resource. An information processing system having a function of executing a write or read process according to the above, and a function of requesting the resource release control unit to release a file resource after executing the write or read process. 21. The resource acquisition control unit according to claim 20, having a function of receiving a resource acquisition request from each task and requesting the OS to acquire a semaphore. , An information processing system having a function of receiving a resource release request from a task and requesting the OS to release a semaphore. 22. In an information processing system comprising a multitasking OS (operating system) and one or more file resources used by each task, resource exclusion for exclusively controlling file resources under the environment of the multitasking OS. The resource exclusive control function includes a control function and a file management unit that manages file resources. The resource exclusive control function receives a resource acquisition waiting state management unit that manages a resource acquisition waiting state and receives a resource acquisition request from a task. A resource acquisition control unit that requests the OS to shift to the task wait state according to the resource acquisition waiting state managed by the waiting state management unit, and a resource release waiting state management unit that receives a resource release request from the task A resource solution that requests the OS to restart a wait state task in accordance with a resource acquisition waiting state managed by When a file management unit receives a write or read processing request in a file unoccupied state, the file management unit requests the resource acquisition control unit to acquire a file resource and executes the write or read processing. An information processing system having a function of subsequently requesting the resource release control unit to release a file resource. 23. In an information processing system comprising a multitasking OS (operating system) and one or more resources used by each task, resources are excluded by utilizing a semaphore function under the environment of the multitasking OS. A resource exclusive control system for controlling, a resource acquisition waiting state managing means for managing a resource acquisition waiting state, and a resource acquisition waiting state managed by the resource acquisition waiting state managing means for receiving a resource acquisition request from a task. The OS in response to a resource acquisition control unit that requests the OS to shift to the task wait state and a resource release request from a task, and the resource acquisition wait state managed by the resource acquisition wait state management unit. A resource exclusion control system comprising: a resource release control unit for requesting the resumption of a wait state task. 24. The resource acquisition control unit according to claim 23, having a function of receiving a resource acquisition request from each task and requesting the OS to acquire a semaphore. A resource exclusive control system having a function of receiving a resource release request from a task and requesting the OS to release a semaphore. 25. The resource acquisition waiting state management means according to claim 24, comprising a resource management table in which table elements corresponding to the number of resources for which exclusive control is required are arranged, and each table element identifies a resource. Resource identifier storage area for storing an identifier for storing resources, a wait task counter storage area for storing a wait task counter for storing the number of tasks in the resource acquisition waiting state, and a wait semaphore for storing an identifier of a semaphore used for resource acquisition waiting. A resource exclusive control system having an identifier storage area. 26. The system according to claim 25, further comprising: a semaphore allocating unit that dynamically allocates a semaphore to be used in response to a resource acquisition request, and a semaphore canceling unit that receives a resource to be released and cancels a used semaphore. Resource exclusion control system. 27. In an information processing system comprising a multitasking OS (operating system) and one or more resources used by each task, resources are excluded by utilizing a semaphore function under the environment of the multitasking OS. A resource exclusive control system for controlling, a resource acquisition waiting state management means for managing a resource acquisition waiting state, and a management means for managing a number of semaphores corresponding to the number of resource acquisition requests that may occur at the same time. , A semaphore dynamic allocation means for dynamically allocating a semaphore to be used from a semaphore managed by the management means in response to a resource acquisition request, and a semaphore releasing means for canceling the used semaphore in response to a resource release request A resource exclusion control system comprising: 28. The semaphore management means according to claim 27, wherein the semaphore management means is provided at least for each resource acquisition request that may occur at the same time, and in which a number of table elements corresponding to the acquisition request number are arranged. Each table element has a semaphore identifier storage area for storing a semaphore identifier and a semaphore status storage area for storing a semaphore status. The semaphore identifier storage area previously stores an identifier of a semaphore managed by the OS. A resource exclusive control system characterized by being stored. 29. The resource acquisition waiting state management means according to claim 28, further comprising a resource management table in which table elements corresponding to the number of resources for which exclusive control is required are arranged, and each table element identifies a resource. Resource identifier storage area for storing an identifier for storing resources, a wait task counter storage area for storing a wait task counter for storing the number of tasks in the resource acquisition waiting state, and a wait semaphore for storing an identifier of a semaphore used for resource acquisition waiting. A resource exclusive control system having an identifier storage area. 30. In claim 29, the semaphore dynamic allocation means searches for a free semaphore identifier, and when a free semaphore identifier is detected, the semaphore identifier is assigned as a semaphore for the resource, and A resource exclusion control system having a function of storing and registering a semaphore identifier in a wait semaphore identifier storage area.