JPH11203150A - Task controller and storage medium storing task control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a task controller which improves the processing efficiency of a task, reduces a program size and controls data communication between tasks. SOLUTION: A sending request receiving part 103 receives a data sending request from a task and stores data to be sent in a data storing part 104. A receiving request receiving part 106 receives a data receiving request from task, reads a receiving data size of the task from a receiving data size managing part 105, a data extracting part 108 extracts data of the size from the part 104 and a data transferring part 109 transfers data for the receiving data size from a data storing means to the task.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a task control device for controlling data communication between a plurality of tasks in an operating system, and a storage medium for storing a task control program.

[0002]

2. Description of the Related Art Conventionally, an operating system has realized a mechanism for exchanging data between a plurality of tasks by using system services such as a queue (also called a mailbox) and a rendezvous. The details are described, for example, in "2.2 Interprocess Communication" in "Chapter 2 Process" of "Basic and Application of OS" by AS Tanenbaum (published by Toppan Co., Ltd.).

In the above system service, data of a predetermined data size is transmitted or received between a transmission task and a reception task.

[0004]

However, according to the prior art, the data size required for internal processing often differs depending on the task, and the reception task requires processing for rearranging transmission data to a required data size.
There has been a problem that task processing efficiency deteriorates and the program size increases.

For example, if the internal processing units of task A and task B are 32 bytes and 64 bytes, respectively, and the transmission data size is set to 32 bytes, reception task B performs the first data reception processing. , The second data reception waiting process and the second data reception process must be performed. Performing such processing individually by each task puts a burden on the processing time that the task should originally perform, so that there is a problem that the processing efficiency is deteriorated and the program size is increased.

Further, in a system composed of a plurality of processors, even though the data size that can be optimally processed usually differs depending on the bus width and processing time of each processor, task data communication between the processors is difficult. Since a common data size had to be set, there is a similar problem. The present invention has been made in view of the above points,
Regarding a task control device and a task control program that control data communication between a plurality of tasks, by reducing the load of data communication processing in each task, it is possible to improve the processing efficiency of the entire task and reduce the program size of the task. It is to plan.

[0007]

In order to solve the above-mentioned problems, a task control device according to the present invention comprises: a data storage unit having an area for temporarily storing data to be transmitted by a task; Receives a data transmission request from the task
Transmission request processing means for transferring data to be transmitted of the first task to the data storage means, management means for managing the size of each data stored in the data storage means, and data reception request from the second task When the data having the size equal to the reception data size required by the second task is stored in the data storage means with reference to the management means, the data having the size equal to the reception data size is transmitted from the data storage means. Receiving request processing means for transferring to the second task.

The reception request processing means includes a reception size table for holding a reception data size required for each task, and a reception data size from the reception size table when receiving a data reception request from the second task. Reading the size of each data from the management means and determining whether or not data larger than the received data size of the second task is stored in the data storage means; and larger than the received data size of the second task. And a second transfer unit that transfers data having a size equal to the received data size from the data storage unit to the task that has requested the reception when it is determined that the received data is stored.

Further, the transmission request processing means includes: a transmission size table for holding a transmission data size required for each task; and when a data transmission request is received from the first task, the transmission request processing means transmits the transmission task size from the transmission size table. A vacancy determining unit that reads the data size and determines whether there is more vacancy in the data storage unit, and a first transfer that transfers data to be transmitted by the first task to the data storage unit when there is vacancy. Means may be provided.

The data storage means has a plurality of queue buffers for storing data in a first-in first-out manner.
The management means manages, for each queue buffer, a size of stored data and a data size of a free area, the data transmission request includes designation of a queue buffer for storing a transmission data, and the data reception request includes: Includes a designation of a queue buffer of a reception data request destination, and the empty judgment means judges whether or not the queue buffer specified by the data transmission request has an empty space equal to or larger than the transmission data size read from the transmission size table. The determination may be such that the size determination unit determines whether or not there is data in the queue buffer specified by the data reception request that is equal to or larger than the reception data size read from the reception size table.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS <First Embodiment><Schematic Description of Task Control Device> FIG. 1 is an explanatory diagram showing an overview of a task control device according to an embodiment of the present invention.

As shown in FIG.
Is realized by operating an operating system (hereinafter referred to as OS (Operating System)) 2 having a multitasking function on hardware 1 having a processor (CPU). That is, the task control device is a part of the function of OS2 that supports multitasking,
Controls data communication between multiple tasks.

In FIG. 1, tasks 3 to 5 are executed on the OS 2.
(Tasks A to C) are being executed.
Each task has a transmission data area for temporarily storing data to be transmitted to another task in a memory area allocated to itself by the OS 2, and a data for receiving data from another task and temporarily storing the data. It has a reception data area to hold. The transmission data size and the reception data size are not necessarily the same among a plurality of tasks. The task is
When transmitting data to another task, data to be transmitted is stored in a transmission data area, and then a transmission request is notified to the task control device 101. When data is received from another task, the task control device 101 is notified of a reception request.

The task control device has a buffer (data storage unit) for temporarily storing transmission / reception data between tasks in a memory area allocated for the OS, and stores a buffer when a transmission request is notified from the task. Then, when a reception request is notified from the task, data corresponding to the reception data size required by the task is transmitted to the task. That is, the task control device controls data transmission between tasks while adjusting the difference between the transmission data size of the transmission task and the reception data size of the reception task. At this time, even if the transmission data size of the transmission task and the reception data size of the reception task are different, the task control device transfers data of the reception data size to the reception task in one transfer. Control to do so. <First Hardware Configuration Example> FIG. 2 is a diagram showing a hardware configuration example when the present task control device is mounted on a television receiver.

This hardware shows a main part of the television receiver, and includes a CPU 1, a memory 2, and a plurality of I / Os.
/ O (input / output) units 3 to 7 are provided. The CPU 1 executes the software stored in the memory 2 to
The function of the task control device of the present invention is realized. As shown in FIG. 1, this software has a part of an OS having a multitask function, that is, a function of controlling data communication between tasks. The CPU 1 executes a plurality of tasks under the control of the OS.

The memory 2 has a storage area for the OS (including the data area) and a storage area for each task (including the data area for the task). In the data area of each task,
The transmission data area and the reception data area are included. I
The / O unit 3 includes remote controllers I / F and I / F for receiving key data transmitted from a remote controller attached to the television receiver.
The O unit 4 is an operation panel for receiving a key input from the user, and an I / O.
The section 5 is a tuner section for selecting broadcast waves, the I / O section 6 is a display section for displaying video, and the I / O section 7 is an audio output section.

Each task shown in FIG. 1 has the above-mentioned transmission data area and reception data area in, for example, a stack or a work area in a memory area reserved for the task by the OS. The transmission data in the transmission data area is written by the task and read by the task control device. The received data in the received data area is written by the task control device and read by the task.

The tasks executed on the OS are provided in the hardware shown in FIG. 1, for example, corresponding to each I / O unit. For example, I / O unit 3 (remote control I / F unit)
, The operation of the I / O unit 4 (operation panel), the operation of the I / O unit 5 (tuner unit), and the operation of the I / O unit 6 (display unit). , A task for controlling the I / O unit 7 (audio output unit), and the like. Of course, there are other various tasks for processing internal operations other than I / O.

For data transmission / reception between tasks, for example, data indicating channel up / down or data directly specifying a channel number is transmitted from a remote controller I / F section task to a tuner task, Data indicating volume up / down, data instructing mute, and the like are transmitted from the panel task to the audio output section task, and the display section task performs time data, numeric data, Various data needs to be transmitted and received between tasks, such as requesting display data such as channel number data as received data.

Here, the tasks for the remote controller I / F unit, the tuner unit, and the display unit are referred to as tasks A to C. FIGS. 5A and 5B show examples of the transmission data size and the reception data size of the tasks A to C. FIG. As shown in the figure, the transmission data size and the reception data size of these tasks are determined according to the processing contents. <Second Hardware Configuration Example> FIG. 3 is a diagram showing a hardware configuration example when the present task control device is mounted on a set-top box (satellite broadcast tuner).

The hardware includes a control unit 11 for controlling the entire set-top box, a remote control receiving unit 13 for receiving key data from a remote control 14, a reception for receiving a digital or analog broadcast wave and selectively receiving a desired channel. A decoding unit for decoding a signal of a received channel when a digital broadcast is received; and a video signal processing unit for outputting a decoding result as a video signal.

The control unit 11 includes a CPU 11a, a bus I / F
The unit 11c includes a main memory 11d. The main memory 11d stores software such as the OS and the application (a plurality of tasks). The function as the task control device is exhibited by the CPU 11a executing the software of the main memory 11d. In this case, the tasks executed on the OS include a task for controlling the operation of the remote control receiving unit 13, a task for controlling the operation of the receiving unit 15, a task for controlling the operation of the MPEG decoder 16, and the video signal processing unit 1.
7 and the like to control the operation of FIG.

These tasks are performed as in FIG.
Transmits and receives data of the transmission data size and the reception data size determined according to the processing content of the task. The transmission data size and the reception data size in the case where a text multiplex broadcast is received and a video signal for character display is output in this set-top box will be described. The task for the receiving unit 15 is a vertical blanking interval (VBI).
Is received and transmitted to the video signal processing unit 17 task. The video signal processing unit 17 outputs a video signal for character display from the received character data.
In this case, the transmission data size of the task for the receiving unit 15 is
It is desirable that the size be equivalent to the number of characters in one VBI section. The reception data size of the task for the video signal processing unit 17 is set to a size (approximately 400 bytes) corresponding to the number of characters to be displayed on one screen when the update unit of the display is one screen unit. In the case of a line unit, the size is equivalent to the number of characters displayed on one line (about 40 bytes). In this case, in place of the task for the video signal processing unit 17, a plurality of tasks such as a task of updating display in units of one screen and a task of updating display in units of lines may be used.

Here, the task for the remote control receiving section 13, the task for the receiving section 15, and the task for the video signal processing section 17 are called task A.
To C. In this case, the transmission data size and the reception data size of the tasks A to C are, as shown in FIGS. 5A and 5B, the transmission data size and the reception data size of these tasks according to the processing contents. Determined. <Structure of Task Control Device> FIG. 4 is a block diagram showing the structure of the task control device. The present task control device 101
Are the transmission data size management unit 102 and the data storage unit 10
4. Received data size management unit 105, reception request reception unit 1
06, a data extraction unit 108, and a data transfer unit 109. Although the task control device 101 in FIG. 1 is illustrated as being disassembled into functional blocks, software that performs the functions in FIG. 4 is actually executed as a part of the OS on the hardware illustrated in FIG. It is realized by doing.

The transmission data size management unit 102 stores the transmission data size of each task. FIG. 5A shows an example. In the figure, the transmission data sizes of tasks A, B, and C are 32, 64, and 64 bytes, respectively. The transmission request receiving unit 103 receives a transmission request from a task having transmission data to another task, and further stores the transmission data in the data storage unit 104. Here, the transmission request includes the start address of the transmission data stored in the transmission data area of the task and the data storage unit 10.
4 designation of the queue. Transmission request receiving unit 10
No. 3, when there is no free space in the data storage unit 104, the reception of the transmission request is suspended, and when there is a free space in the data storage unit 104, the transmission data size of the task is read from the transmission data size management unit 102. Then, data corresponding to the transmission data size is read from the specified address in the data area of the task, and stored in the specified queue of the data storage unit 104.

The data storage unit 104 includes the transmission request receiving unit 1
03 temporarily stores and manages the transmission data received. Therefore, the data storage unit 104 has a plurality of first-in first-out queues and a queue management table corresponding to each queue. Received data size management unit 105
Stores the received data size of each task. FIG.
(B) shows an example. In the figure, the received data sizes of tasks A, B, and C are 32, 64, and 128 bytes, respectively.

The reception request receiving unit 106 receives a reception request (designation of a queue and the start address of reception data to be stored in the reception data area) from the task, and receives the reception data size of the task from the reception data size management unit 105. The data extraction unit 108 is notified of an extraction request (the above-described queue designation, head address, and received data size) for reading and extracting data from the data storage unit 104.

Upon receiving a data extraction request, the data extraction unit 108 checks whether or not data corresponding to the reception data size is stored in the designated queue. And notifies the data transfer unit 109 of a transfer instruction (the read data, the above-described head address, and the received data size). If not, the check is repeated again after a predetermined time.

Upon receiving the transfer instruction, the data transfer section 109 transfers the data of the received data size to the storage location indicated by the address specified in the reception request. <Data Storage Unit 104> FIG. 6 is an explanatory diagram showing an example of a data storage system of the data storage unit 104. In this example, the data storage unit 104 stores the queues 21a, 22a, and 23a.
And queue management tables 21b, 22b and 23b.

The queue 21a is a buffer for temporarily storing transmission data addressed to the task A from any task, and is physically secured in the memory area (data area) of the OS in the memory 2. Logically, it is configured as a first-in first-out queue in combination with the queue management table 21b. The minimum size of the data managed by the queue 21a may be set to the greatest common divisor of the transmission data size and the reception data size of the data transmitted / received via the queue. As shown in FIGS. 5A and 5B, the transmission data size of each of the tasks B and C to be transmitted to the queue 21a is 64 bytes, and the reception data size of the task A is 32 bytes. The greatest common divisor may be 32 bytes.

The queue management table 21b stores the queue 21
In order to manage the state of a, the area for the queue 21a secured in the memory area (data area) of the OS is
This is a table for managing the address, data size, number of data, and the like. Queues 22a, 23a,
The same applies to the queue management tables 22b and 23b.

The number of queues is determined according to the number of tasks that receive data and the type of data that each task receives. The reason why the number of queues is three in the figure is that tasks A, B, and C each receive one type of data from another task. If task A receives a plurality of types of data from other tasks, the same number of queues may be provided for task A,
One queue may be enough. Further, when a plurality of tasks receive the same type of data, one queue may be shared. <Queue Management Table> FIGS. 7A and 7B show queue 2
FIG. 1A is an explanatory diagram showing a more detailed configuration of a queue management table 21b.

In FIG. 6A, reference numerals 71 to 75 denote five ring-shaped data storage areas. Reference numeral 76 denotes a head pointer indicating the first data storage area in which data is stored. Reference numeral 77 denotes a tail pointer indicating the end where data is stored. In FIG. 3B, the queue management table 21b includes “data size”,
"Head pointer", "Tail pointer", "Maximum number", "Free number", "Use number", "Reception request queue"
Is stored.

Here, the "data size" is the data size of each data storage area of the queue. In the example shown in the figure, the data size is 32 bytes. This data size is such that the received data size of task A that receives data via queue 21a is 32 bytes,
Since the transmission data size of tasks B and C for transmitting data via a is 64 bytes, the maximum common divisor is set to 32 bytes.

A "head pointer (head)" and a "tail pointer (tail)" are pointers indicating the head and end of queue data, respectively. In the example shown in the figure, the head pointer points to the data storage area 72 and the tail pointer points to the data storage area 74. "Maximum number",
The "number of free spaces" and "the number of used spaces" indicate the total number of data storage regions, the number of free data storage regions, and the number of data storage regions in use, respectively. In the example of the figure, the maximum number is 5, the number of free spaces is 2, and the number of used spaces is 3.

The "reception request queue" is a queue (queue) of reception requests issued to the queue.
The figure shows a state in which a reception request from task A is waiting. The reception request includes the task name of the request source and the storage destination address of the reception data area of the task. <Transmission Request Accepting Process> FIG. 8 is a flowchart showing a transmission request accepting process in the task control device.

In FIG. 7, when a transmission request (a head address of transmission data and designation of a queue) is received from any of the tasks (step 80),
The transmission data size of the requesting task is extracted from the transmission data size management unit 102 (step 81), and the queue management unit of the designated queue is referred to to determine whether or not the queue has a free space. If not, an error message indicating the fact is notified to the requesting task (steps 82 and 83), and the process ends.

For example, when a transmission request from the task B is received (the destination is the queue 21a, the head address of the transmission data stored in the transmission data area of the task B), the transmission request receiving unit 103 manages the transmission data size. The transmission data size of the task B from the unit 102 (64 shown in FIG.
Byte). Further, the transmission request receiving unit 103
Checks whether there is a vacancy by examining the magnitude relationship between the transmission data size of task B and the product of the "number of vacancies" and "data size" in the queue management table 21b. If there is no free space, an error message is notified to task B, and the process ends.

If there is a vacancy, the transmission request receiving unit 10
3 transfers the data of the transmission data size (64 bytes) from the specified address in the transmission data area of the requesting task B to the queue 21a in the data storage unit 104 (steps 82 and 84), and The management table is updated (step 85). For example, in the case of a request for transmission from the task B to the queue 21a, the transmission data size of the task B is 64 bytes as shown in FIG. 5A, and the data of the queue 21a is transmitted as shown in FIG. Since the size is 32 bytes, the queue management table 21
If the “number of vacancies” of b is 2 or more, the transmission request receiving unit 103 determines that there is a vacancy. Task B 64
The byte transmission data is transferred to the queue 21a by the transmission request receiving unit 103 and stored as two pieces of queue data. At this time, the “number of uses” of the queue management unit 21b is 2
Increase, and the number of "empties" decreases by 2.

After updating the queue management table, if a reception request is registered as a queue in the queue management table, the data extraction unit 108 refers to the reception data size management unit 105 to receive the task waiting for reception. The data size is read (steps 86 and 87), and if there is data of the received data size in the queue, the data is transferred from the queue to the data area of the task waiting for reception (step 8).
8, 89), and updates the queue management table (step 90). As described above, the data extraction unit 108 checks whether or not a reception request has been registered after updating the queue management table, when there is a task waiting for data.
This is because data is transferred as soon as a transmission request addressed to the task is issued. <Reception Request Accepting Process> FIG. 9 is a flowchart showing a receiving request accepting process in the task control device.

In the figure, the reception request receiving unit 106
When a reception request (storage destination address of reception data area and designation of queue) is received from any task (step 91), the reception data size of the task is read out with reference to the reception data size management unit 105 (step 91). Step 9
2) It is determined whether there is data of the received data size in the queue (step 93).

For example, when task A issues a reception request, reception request receiving section 106 receives data size of task A (32 bytes) from reception data size management section 105.
Is read, and it is determined from the “data size” and “number of uses” in the queue management table 21b whether or not there is data of the received data size. In this case, since the “data size” of the queue management table 21b is 32 bytes, if the “number of uses” is 1 or more, it is determined that data required by the task A exists.

If there is data of the received data size, the data extracting unit 108 extracts data of the received data size from the queue. Further, the data transfer unit 1
09 transfers the fetched data to the specified address of the task reception data area (step 9).
5). At that time, the data extraction unit 108 updates the queue management table (Step 96).

For example, when there is a reception request from task A, 32-byte queue data is extracted from the queue 21a by the data extraction unit 108, and the data transfer unit 109 specifies the reception data area of the task A. Is forwarded to the specified address. Also, the reception request receiving unit 1
06, if there is no data of the reception data size in the queue, the reception request of the task is registered in the reception request queue of the queue management table (step 93,
94).

The operation of the task control device according to the first embodiment of the present invention configured as described above will be described below. The operation will be described by taking as an example a case where data is transmitted from task A having a transmission data size of 32 bytes to task B having a reception data size of 64 bytes. First, task A stores 32-byte transmission data in the transmission data area of task A, and issues a transmission request to transmission request receiving section 103. This transmission request includes a head address of transmission data in the transmission data area and a destination indicating the queue 22a.

It is assumed that the queue 22a is empty as shown in FIG. The transmission request receiving unit 103
Upon receiving the transmission request, the transmission data size management unit 1
The transmission data size (32 bytes) of the task A is extracted from 02 (step 81), and it is determined whether or not the queue has a free space by referring to the queue management table 22b of the queue 22a specified as the destination. In this case, since there is a space, the transmission request receiving unit 103 stores the data of the transmission data size (32 bytes) from the specified address in the transmission data area of the task A of the request source in the queue 22a in the data storage unit 104. And updates the queue management table 22b. The state of the queue 22a and the queue management table 22b at this time are shown in FIG.
(B). In FIG. 3B, one piece of 32-byte queue data is stored.

Further, when the transmission request from the task A to the task B is issued again, the 32-byte transmission data is stored in the queue 22a and the queue management table 22b is updated in the same manner as described above. This state is shown in FIG.
Shown in In this way, the task on the transmitting side can issue a transmission request at any time regardless of the data size of the task on the receiving side.

Further, in the state shown in FIG.
Has issued a reception request. The reception request includes a storage destination address of the task B in the reception data area and designation of the queue 22a. The reception request receiving unit 106
The reception data size (64 bytes) of the task B is read from the reception data size management unit 105, and it is determined whether or not there is data of the reception data size based on “data size” and “number of uses” in the queue management table 22b. In this case, since the “data size” of the queue management table 22b is 32 bytes and the “number of uses” is 2 or more, it is determined that the data required by the task B exists.

Further, the data extracting unit 108
Data corresponding to the received data size is extracted from 2a.
Further, the data transfer unit 109 transfers the extracted data to a specified address in the task reception data area. At that time, the data extraction unit 108 updates the queue management table, and as a result, returns to the state of FIG.

If the task B issues a reception request in the state shown in FIG. 10B, the queue data in the queue 22a is smaller than the reception data size. Therefore, the reception request of the task B is stored in the queue management table 22b. It is registered in the reception queue. Thereafter, when the state shown in FIG. 10C is reached, 64-byte data is transferred to the task B by the data transfer unit 109.

In this way, the task on the receiving side can issue a reception request at any time regardless of the data size of the task on the transmission side, and the data size required at one time by issuing one reception request can be obtained. Can be obtained. In the above embodiment, the case where the tax control device is mounted on the television receiver (FIG. 2) and the set-top box (FIG. 3) has been described. However, the functions of the functional block diagram of FIG. 4 are realized by software. Therefore, the present invention can be implemented with any hardware configuration having a CPU that supports multitasking. For example, the present invention can be implemented in a personal computer, a workstation, a portable information device, or the like. The software for realizing the functions shown in FIG. 4 can be recorded on a storage medium such as a floppy disk or an optical disk or distributed via a communication network. Therefore, a computer that can read the storage medium can execute the present invention by executing the software read from the storage medium. <Second Embodiment> FIG. 11 is a block diagram showing a configuration of a task control device 200 according to a second embodiment.

The task control device 200 shown in FIG. 10 is different from the task control device 101 in FIG. 4 in that a transmission request reception unit 201 is provided instead of the transmission request reception unit 103, and a direct transfer unit 202 is newly added. Only the differences are the other components are the same. The hardware configuration is the same as in FIG. Hereinafter, the same points will not be described, and different points will be mainly described.

In FIG. 11, a transmission request receiving unit 201
In addition to the function of the transmission request receiving unit 103, if a reception request corresponding to the transmission request is already registered in any of the queue management tables in the data storage unit 104 at the time of receiving the transmission request, The direct transfer unit 202 is instructed to transfer directly without storing the data in the data storage unit 104. When direct transmission is instructed by the transmission request receiving unit 201, the direct transfer unit 202 directly transfers data from the transmission data area of the task of the transmission request source to the reception data area of the task of the reception request source. <Transmission Request Accepting Process> FIG. 12 is a flowchart showing a transmission request accepting process in the task control device. In the processing contents of FIG. 11, steps 121 to 123 are newly added to the transmission request reception processing of FIG. The description of the same points will be omitted, and only different points will be described.

In the figure, the transmission request receiving unit 201
When a transmission request is received from the task and the transmission data size is confirmed (steps 80 and 81), it is determined whether a reception request corresponding to the transmission request is registered in any of the queue management tables in the data storage unit 104. A determination is made (step 121). Here, the reception request corresponding to the transmission request means that the transmission data size and the reception data size are the same, and the queue to which the transmission request is addressed and the queue in which the reception request is waiting are the same. Say.

If a reception request corresponding to the transmission request is registered, the transmission request receiving unit 201
2 is instructed to transfer directly. The direct transfer unit 202 directly transfers the data of the transmission data size from the transmission data area of the task of the transmission request source to the reception data area of the task of the reception request source (step 122), and transfers the reception request from the queue management table. It is deleted (step 123).

When the reception request corresponding to the transmission request is not registered, the process is the same as in the first embodiment. As described above, the task control device 200 of the present embodiment directly performs data transfer between the data areas of the transmission task and the reception task when the reception request corresponding to the transmission request is already registered when the transmission request is issued. Data communication between tasks can be realized at high speed because the operation of storing and reading data in the data storage unit 104 becomes unnecessary.

Although the determination of the presence or absence of the corresponding reception request in step 121 is made based on the size and the queue, the task of the transmission request source and the task of the reception request source (or queue ) May be prepared in advance as a table, and the determination may be made by referring to the table. <Third Embodiment> FIG. 13 is a block diagram showing a configuration of a task control device 300 according to a third embodiment.

4 differs from the task control device 101 of FIG. 4 in that the transmission request reception unit 301 is replaced by the transmission request reception unit 301 instead of the transmission request reception unit 103.
6, a reception request receiving unit 302 and a data storage unit 10
4 except that a data storage unit 304 is provided and a direct transfer unit 303 is newly added, and the other components are the same. The hardware configuration is the same as in FIG. Hereinafter, the same points will not be described, and different points will be mainly described.

Referring to FIG. 13, transmission request receiving section 301
Does not store the data in the queue specified as the destination in the transmission request when the transmission request is a specific transmission request at the time of receiving the transmission request in addition to the function of the transmission request receiving unit 103 Then, a transmission request is registered in the queue management table. Here, the specific transmission request is a transmission request that allows direct transfer between tasks, and is a predetermined transmission request. For example, a specific transmission request may have a possibility that a reception request having the same transmission data size and the same reception data size and the same queue will be issued.

In addition to the function of reception request receiving section 106, reception request receiving section 302 has already received a specific transmission request corresponding to the reception request at the time of receiving the reception request. If it is registered in the queue management table, it instructs the direct transfer unit 303 to perform direct transfer. Here, the transmission request corresponding to the reception request means that the transmission data size and the reception data size are the same, and the destination queue of the reception request is the same as the queue in which the transmission request is waiting. .

[0061] The direct transfer unit 303 includes the reception request receiving unit 30.
2, when the direct transfer is instructed, the data is directly transferred from the transmission data area of the task of the transmission request source to the reception data area of the task of the reception request source. Data storage unit 304
Stores, in addition to the function of the data storage unit 104, a specific transmission request as a queue in each queue management table. <Transmission Request Accepting Process> FIG.
5 is a flowchart showing a transmission request receiving process in the embodiment. In the processing contents of FIG. 14, steps 141 and 142 are newly added to the transmission request reception processing of FIG.
The description of the same points will be omitted, and only different points will be described.

In the figure, the transmission request receiving unit 301
When a transmission request is received from the task and the transmission data size is confirmed (steps 80 and 81), it is determined whether or not the transmission request is a specific transmission request (step 141).
If the request is a specific transmission request, the transmission request receiving unit 301
Registers the transmission request in the corresponding queue management table in the data storage unit 304. At this time, the transmission data is
It is not stored in the queue of the data storage unit 304.

If it is not a specific transmission request, it is the same as in the first embodiment. <Reception Request Accepting Process> FIG.
9 is a flowchart showing a reception request reception process in FIG. In the processing contents of FIG. 14, steps 151 to 153 are newly added to the reception request reception processing of FIG. The description of the same points will be omitted, and only different points will be described.

In the figure, the reception request receiving unit 302
When a reception request is received from the task and the reception data size is confirmed (steps 91 and 92), it is determined whether a transmission request corresponding to the reception request is registered in any of the queue management tables in the data storage unit 304. A determination is made (step 151). If the transmission request corresponding to the reception request is registered, the reception request receiving unit 302
3 is instructed to transfer directly. The direct transfer unit 303 obtains, from the transmission data area of the registered task of the transmission request source,
The data of the transmission data size is directly transferred to the reception data area of the task of the reception request source (step 152), and the transmission request is deleted from the queue management table (step 153).

When the transmission request corresponding to the reception request is not registered, the processing is the same as in the first embodiment. As described above, when a specific transmission request is issued, the task control device 300 of the present embodiment registers the transmission request in the queue management table, and transmits the transmission request when the corresponding reception request is issued. Since the data transfer is directly performed between the data area of the task and the data area of the receiving task, the data communication between the tasks can be realized at high speed because the operation of storing and reading the data in the data storage unit 404 becomes unnecessary. <Fourth Embodiment> FIG. 16 is a diagram showing a hardware configuration of a task control device 400 according to a fourth embodiment.

This hardware includes a gate 30, a CPU
31, memory 32, I / O units 33 to 35, CPU 41,
It has a memory 42, I / O units 43 and 44, a CPU 51, a memory 52, I / O units 53 and 54, and has a multiprocessor configuration. Hereinafter, CPU 31, CPU 41, CP
The hardware parts centering on U51 are called processor X, processor Y, and processor Z, respectively.

The processors X, Y, and Z are substantially the same as the hardware shown in FIG. 2, respectively.
The functions of the task control device of the present invention are realized by executing software in the memory in the same manner as in. As shown in FIG. 2, software of each processor has a part of an OS having a multitasking function, that is, a function of controlling data communication between tasks.

Further, the processors X, Y, and Z are connected via a memory 32. That is, a part of the storage area of the memory 32 is a shared memory, and is configured to be usable from any processor via the gate 30. Although the shared memory is physically different from the memories 42 and 52 of the processors Y and Z, the same memory is accessed from any processor. Each processor logically looks at the shared memory like its own memory.
The processors X, Y, and Z also perform task data transmission and reception between the processors.

The I / O units are the same as in the first embodiment. <Configuration of Task Control Device> FIG.
FIG. 3 is a block diagram illustrating a configuration of a task control device 400 in a processor X. Since the same applies to the processors Y and Z, the processor X will be described here as a representative.

The task control device 400 shown in FIG. 11 differs from the task control device 101 shown in FIG. 4 in that the transmission request reception unit 1703 is used instead of the transmission request reception unit 103 and the transmission data size is used instead of the transmission data size management unit 102. Management unit 171
2 is different from the reception data size management unit 105 in that a reception data size management unit 1705 is provided instead of the reception data size management unit 105, and a processor management unit 1701 and a data delivery unit 1702 are newly added. Hereinafter, the same points will not be described, and different points will be mainly described.

The processor management section 1701 stores which processor is executing each task. FIG. 18 illustrates a storage example of the processor management unit 1701. In the figure, task A is executed by processor X, task B is executed by processor Y, and task C is executed by processor Z. The data delivery unit 1702 is a transmission request receiving unit 1
In response to the instruction of 703, if the data transmission destination is another processor, the transmission data is transferred to that processor.
In this transfer, the transmission data is stored in the data storage unit 104 of the processor via the shared memory from the transmission data area of the task requesting the transmission. Transmission request receiving unit 1
When the transmission request is received, if the transmission destination of the data is another processor, 703 issues a distribution instruction to the data distribution unit 1702 to the processor.

The transmission data size management unit 1712 and the reception data size management unit 1705 have the functions of the transmission data size management unit 102 and the reception data size management unit 105, respectively. The data size is also stored. In the present embodiment, the transmission data size management unit 1712 and the reception data size management unit 1705 determine the transmission data size shown in FIGS.
It is assumed that the received data size is stored. <Transmission Request Accepting Process> FIG.
5 is a flowchart showing a transmission request receiving process in the embodiment. 8 differs from the transmission request receiving process of FIG. 8 only in that steps 201 and 202 are newly added. The description of the same points will be omitted, and only different points will be described.

In the figure, a transmission request receiving unit 1703
When a transmission request is received from a task and the transmission data size is confirmed (steps 80 and 81), the processor refers to the processor management unit 1701 to determine whether the transmission request is addressed to a task of another processor (step 80). 201), if it is another processor, it instructs the data delivery unit 1702 to deliver the transmission data to the processor. At this time, the data delivery unit 1702 reads out the transmission data from the transmission data area of the task that requested the transmission, and stores the transmission data in the data storage unit 104 of the processor via the shared memory (Step 202). For example, the data delivery unit 1702 stores the transmission request and the transmission data in an area addressed to the shared memory (an area for relaying the transmission request and the transmission data for each processor). From the area, the data storage unit 104 of the other processor stores the data in the designated queue and updates the queue management table.

As described above, in the multiprocessor system, since the data delivery unit 1702 delivers the transmission data, even if the transmission data is destined for the task (or queue) of another processor, the task of the transmission destination may be transmitted. Even if the received data size and the transmitted data size do not match, data can be transmitted. Further, neither task needs to recognize which processor is the task of the transmission destination and the task of the transmission source. <Fifth Embodiment> The hardware configuration of the task control device of the fifth embodiment is the same multiprocessor system as that of the fourth embodiment shown in FIG.

FIG. 22 is a block diagram showing a configuration of a task control device 500 according to the fifth embodiment. The task control device 500 shown in FIG.
, A reception request reception unit 2203 instead of the reception request reception unit 106, a transmission data size management unit 1712 instead of the transmission data size management unit 102, and a reception data size management unit instead of the reception data size management unit 105. 1
705 is provided, and only a processor management unit 2201 and a data delivery unit 2202 are newly added. Hereinafter, the same points will not be described, and different points will be mainly described.

In FIG. 22, the processor management unit 220
1 is the same as the processor management unit 1701 of the fourth embodiment. The reception request receiving unit 2203 is the reception request receiving unit 1
In addition to the function 06, when a reception request is received, if the queue (or task) specified in the reception request belongs to another processor, the data distribution unit 2202 is instructed to distribute received data.

When the reception request receiving unit 2203 instructs the reception request receiving unit 2203 to distribute the reception data, the data distribution unit 2202 reads the data of the reception data size from the data storage unit 104 of the processor that executes the task of the data transmission source indicated by the reception request. Is read and stored in the data storage unit 104 of its own processor. The data stored in the data storage unit 104 is
The data is transferred to the receiving task in the same manner as in the first embodiment.

The reception data size management section 1705 and transmission data size management section 1712 are the same as those described in the fourth embodiment. <Reception Request Accepting Process> FIG.
9 is a flowchart showing a reception request reception process in FIG. 9 differs from the reception request reception processing of FIG. 9 in that steps 231 to 233 are newly added. Hereinafter, description of the same points will be omitted, and only different points will be described.

In the figure, a reception request receiving unit 2203
When a reception request is received from a task and the reception data size is confirmed (steps 91 and 92), it is determined whether the data transmission source task indicated by the reception request is a task being executed by another processor. (Step 231).
When it is determined that the task is being executed by another processor, a delivery request is instructed to the data delivery unit 2202 (step 232). When instructed by the reception request receiving unit 2203 to deliver received data, the data delivery unit 2202 transfers data of the reception data size from the data storage unit 104 of another processor that executes the task of the data transmission source indicated by the reception request. The data is read and transferred to the data storage unit 104 of its own processor. The data stored in the data storage unit 104 is transferred to the receiving task as in the first embodiment. At this time, if there is no data of the reception data size in the data storage unit 104 of another processor, the data delivery unit 2202 registers the reception request in the data storage unit 104 of its own processor.

As described above, in the multiprocessor system, since the data delivery section 2202 delivers received data, even if the data is a task (or queue) transmission data of another processor, the transmission destination task Even if the received data size and the transmitted data size do not match, data can be transmitted. Sixth Embodiment The hardware configuration of the task control device of the sixth embodiment is the same multiprocessor system as that of the fourth embodiment shown in FIG.

FIG. 24 is a block diagram showing the configuration of the task control device 600 according to this embodiment. 4 is different from the task control device 101 in FIG. 4 in that a transmission request reception unit 2403 is provided instead of the transmission request reception unit 103, and a processor management unit 1701 is newly added.
The only difference is that a substitute task starting unit 2402 and a substitute task 2401 are added. Hereinafter, the same points will not be described, and different points will be mainly described.

When the task of another processor issues a data transmission request to the task of its own processor (processor X), the proxy task 2401 once fetches the transmission data into the transmission data area in the proxy task.
A process of storing the transmission data in the data storage unit 104 of the processor X on behalf of the task of the transmission request source is performed. One substitute task is provided for each processor that receives data transmission from a task of another processor.

The transmission request receiving unit 2403 receives a transmission request in addition to the function of the transmission request receiving unit 103.
It is determined whether or not the transmission request is a transmission request to a task of another processor by referring to the processor management unit 1701. If the transmission request is a transmission request to a task of another processor, this fact is indicated as a substitute task activation unit 2402 Notify. Upon receiving the above notification from the transmission request receiving unit 2403, the substitute task activating unit 2402 activates the substitute task of the other processor.

The processor management section 1701 is the same as the processor management section in the fourth embodiment. <Transmission Request Accepting Process> FIG.
5 is a flowchart showing a transmission request receiving process in the embodiment. 8 differs from the transmission request reception processing of FIG. 8 only in that steps 251 to 253 are newly added. The description of the same points will be omitted, and only different points will be described.

In the figure, a transmission request receiving unit 2403
When a transmission request is received from a task and the transmission data size is confirmed (steps 80 and 81), the processor refers to the processor management unit 1701 to determine whether the transmission request is addressed to a task of another processor (step 80). 251) If there is another processor, the transmission data is stored in the shared memory (step 252), and the proxy task activation unit 2402 is notified that the request is a transmission request addressed to a task of another processor. Upon receiving this notification, the substitute task activation unit 2402 activates the substitute task of the processor (step 253). <Processing Content of Proxy Task> FIG.
6 is a flowchart showing the processing contents of No. 1.

The activated substitute task 2401 first
The transmission data to be substituted stored in the shared memory is transferred to the transmission data area in the memory area for the substitution task (step 261), and the transmission data size of the substitution task is read from the transmission data size management unit 102. (Step 262), the data of the transmission data size is transferred from its own transmission data area to the data storage unit 104 (Step 263).

As a result, the data storage unit 104 stores the transmission data of the task of the other processor which has requested transmission, as if it had been sent from the task itself. The transmission data in the data storage unit 104 is transferred to the task that issued the reception request, as in the first embodiment.

As described above, in the present embodiment, one processor is provided for each processor that receives data transmission from a task of another processor.
By providing the substitute tasks one by one, data communication of tasks between processors can be performed in the same manner as data communication with a single processor, even if the size of transmitted / received data differs for each task.

[0089]

The task control device of the present invention is a task control device for controlling data communication between a plurality of tasks,
A data storage unit having an area for temporarily storing data to be transmitted by the task, and a transmission for receiving a data transmission request from the first task and transferring the data to be transmitted of the first task to the data storage unit Request processing means, management means for managing the size of each data stored in the data storage means, reception of a data reception request from the second task, reception referring to the management means and required by the second task And receiving request processing means for transferring, when the data having the size equal to the data size is stored in the data storage means, the data having the size equal to the received data size from the data storage means to the second task.

According to this configuration, the transmission data from the task is temporarily stored in the data storage means, and the data size is managed by the management means. , The size difference can be absorbed. That is, the task of the data reception request source can obtain data of its own reception data size by one data transfer. Therefore, each task does not receive the data of the received data size in a plurality of times, and the complexity of the data reception waiting process is reduced, so that the load is reduced, the processing efficiency of the entire task is improved, and the task is improved. There is an effect that the program size can be reduced.

Further, the reception request processing means includes a reception size table for holding a reception data size required for each task, and a reception data size when receiving a data reception request from the second task. Size determination means for reading out the size of each data from the management means and determining whether or not data larger than the reception data size of the second task is stored in the data storage means;
And a second transfer unit for transferring data having a size equal to the received data size from the data storage unit to the reception request source task when it is determined that data larger than the received data size of the task is stored. It may be.

According to this configuration, in addition to the above effects, the size determination means refers to the reception size table and the management means so that data larger than the reception data size of the second task is stored in the data storage means. Can be easily determined. Further, the transmission request processing means includes: a transmission size table for holding a transmission data size required for each task; and when receiving a data transmission request from the first task, a transmission data size of the task from the transmission size table. And a first transfer unit for transferring data to be transmitted by the first task to the data storage unit when there is a free space, and determining whether there is more free space in the data storage unit. May be provided.

According to this configuration, in addition to the above-described effects, the vacancy determining unit easily determines whether or not there is a vacancy equal to or larger than the transmission data size in the data storage unit by referring to the transmission size table and the management unit. be able to. Further, the data storage means has a plurality of queue buffers for storing data in a first-in first-out manner, and the management means manages the size of stored data and the data size of free space for each queue buffer. The data transmission request includes a specification of a queue buffer of a transmission data storage destination, the data reception request includes a specification of a queue buffer of a reception data request destination, and the empty determination unit is specified by the data transmission request. The queue buffer determines whether or not there is free space in the queue buffer equal to or larger than the transmission data size read from the transmission size table. The size determination unit reads the queue buffer specified by the data reception request from the reception size table. It may be configured to determine whether or not there is data that is equal to or larger than the received data size.

According to this configuration, in addition to the above effects, since the management means has a plurality of queue buffers, the management means easily manages the size of the data stored in each queue buffer and the data size of the free space. Each task only needs to recognize the queue buffer as the destination of data transmission and reception, and there is an effect that it is not necessary to recognize the task of the transmission and reception partner.

The data storage means has a plurality of queue buffers provided for each task and which stores data in a first-in first-out manner, and the management means determines the stored data size and size for each queue buffer. Managing the free data size, the data transmission request includes a specification of a task of a data transmission destination, the data reception request includes a specification of a task of a data reception source, and the vacancy determining unit specifies the task of the data transmission request. Determining whether or not there is free space in the queue buffer corresponding to the performed task, and determining whether the queue buffer corresponding to the task of the data reception request source has data larger than the reception data size. The determination may be made.

According to this configuration, in addition to the above effect, each task only needs to recognize the partner task as the destination of data transmission / reception, and does not need to recognize the existence of the queue buffer. . Here, the management means is provided in correspondence with the queue buffer, and includes a plurality of reception request buffers for temporarily storing data reception requests for which it is determined by the size determination means that data larger than the reception data size is not stored. Wherein the transmission request processing means further receives a transmission request from the first task,
If a reception request that matches the transmission request is stored in the reception request buffer, the transfer by the first transfer unit is prohibited,
It may be configured to include a direct transfer unit that directly transfers data from the first task to the second task.

According to this configuration, when a reception request corresponding to a transmission request is already held in the reception request buffer, data is directly transmitted from the transmission task to the reception task without interposing data storage means. Since the transfer is performed, there is an effect that the task control device and thus the overall processing efficiency are improved. Here, the transmission request processing means includes:
Further, a determination unit for determining whether a data transmission request from the first task satisfies a predetermined condition is provided, and the management unit is further provided corresponding to a queue buffer,
When the determining means determines that the predetermined condition is satisfied,
A plurality of transmission request buffers for temporarily prohibiting the transfer of the transmission data of the data transmission request by the first transfer unit and temporarily holding the data transmission request; and the reception request processing unit further includes: When receiving, if a transmission request that matches it is held in the transmission request buffer,
It may be configured to include a direct transfer unit that directly transfers data from the first task to the second task.

According to this configuration, when a reception request is generated and a corresponding transmission request is held in the transmission request buffer, data is directly transmitted from the transmission task to the reception task without interposing data storage means. Since the transfer is performed, there is an effect that the task control device and thus the overall processing efficiency are improved. Further, the task control device of the present invention,
A task control device used in a system having a plurality of processors, comprising the same number of task control units corresponding to the processors, and controlling data communication between tasks of the processors, wherein each task control unit should transmit a task. A data storage unit having an area for temporarily storing data, and receiving a data transmission request from a first task of its own processor and transmitting it to a task of another processor or transmitting a request to another task of its own processor. Processor determination means for determining whether the data is to be transmitted, transmission request processing means for transferring data to be transmitted of the first task to the data storage means when it is determined that the data is to be transmitted to the task of another processor; If it is determined that the data is to be transmitted to the task, the first data to be transmitted is transmitted to the data storage means of the other processor. Data delivery means, management means for managing the size of each data stored in the data storage means, and receiving a data reception request from a second task of its own processor, and referring to the management means for the second processing. Receiving request processing means for transferring data having a size equal to the received data size from the data storing means to the second task when data having a size equal to the received data size required by the task is stored in the data storage means; And

According to this configuration, in a system having a plurality of processors, even if the transmission data size and the reception data size are different, each task does not need to recognize the size difference and has a delivery means. Thus, there is no need to know at all which processor is the task of the transmission / reception partner, so that there is an effect that the load of the data transmission / reception processing of the task itself is light and the program size can be reduced.

The task control device according to the present invention is used in a system having a plurality of processors, is composed of the same number of task control units corresponding to the processors, and controls data communication between tasks of the processors. Each of the task controllers receives a data transmission request from a first task of its own processor, and stores data from the first task in response to a data transmission request having an area for temporarily storing transmission data between tasks. Transmission request processing means for transferring transmission data to the means, management means for managing the size of data stored in the data storage means, and receiving a data reception request from a task of its own processor, and receiving a data reception request from a task of another processor. Processor determination means for determining whether the received data is received from the own processor or a task of the own processor; When it is determined that the reception from the click,
When the data having the size equal to the reception data size required by the task is stored in the data storage unit with reference to the management unit, the data having the size equal to the reception data size is stored in the second task from the data storage unit. And a data acquisition means for acquiring data to be received from the data storage means of the other processor when it is determined that the data is to be received from a task of another processor.

According to this configuration, since the data acquisition means is provided, there is no need to recognize at all which processor is the task of the transmission / reception partner. Therefore, the load of the data transmission / reception processing of the task itself is light, and therefore, There is an effect that the program size can be reduced. Further, the task control device of the present invention is used in a system having a plurality of processors, the task control device includes the same number of task control units corresponding to the processors, and controls data communication between tasks of the processors. The task control unit includes: a data storage unit having an area for temporarily storing transmission data between tasks; and a data transmission request from a task of its own processor, and transmission to another processor's task, or its own processor. Processor determination means for determining whether the transmission is to the task, and transmission request processing means for transferring the transmission data from the task of the transmission request source to the data storage means when transmission to the task of the processor is determined. If it is determined that the transmission is to a task of another processor, the transmission is performed by executing a specific task of the other processor. A specific task execution unit that transfers transmission data from the requesting task to the data storage unit of the other processor; a management unit that manages the size of data stored in the data storage unit; Receiving a reception request, referring to the management means, when data having a size equal to the reception data size required by the task is stored in the data storage means, storing data having a size equal to the reception data size. Receiving request processing means for transferring from the means to the task.

According to this configuration, since the specific task execution means is provided, it is not necessary to know at all which processor is the task of the transmission / reception partner. Therefore, the load of the data transmission / reception processing of the task itself is light. There is an effect that the program size can be reduced.
Further, the storage medium storing the task control program of the present invention is a computer-readable storage medium storing a task control program for controlling data communication between tasks, wherein the task control program transmits a data transmission request from the task. Receiving request, a transmission request processing unit for storing transmission data of the task in the buffer memory, a management unit for managing the size of data stored in the buffer memory, and a data reception request from the task, and referring to the management unit. And receiving request processing means for transferring data having a size equal to the received data size from the buffer memory to the task when data having a size equal to the received data size required by the task is stored in the buffer memory. A feature characterized by being executed by a computer It is a medium.

According to this configuration, the transmission data from the task is temporarily stored in the data storage means, and its data size is managed by the management means. , The size difference can be absorbed. That is, the task of the data reception request source can obtain data of its own reception data size by one data transfer. Therefore, each task does not receive the data of the received data size in a plurality of times, and the complexity of the data reception waiting process is reduced, so that the load is reduced, the processing efficiency of the entire task is improved, and the task is improved. There is an effect that the program size can be reduced.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram showing an outline of a task control device 101 according to a first embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of a hardware configuration when the task control device 101 is mounted on a television receiver.

FIG. 3 is a diagram illustrating an example of a hardware configuration when the task control device 101 is mounted on a set-top box (satellite broadcast tuner).

FIG. 4 is a block diagram illustrating a configuration of a task control device 101.

FIG. 5A shows an example of the storage contents of a transmission data size management unit 102. (B) An example of the storage contents of the reception data size management unit 105 is shown.

FIG. 6 is an explanatory diagram illustrating an example of a data storage method of a data storage unit 104.

FIG. 7 is an explanatory diagram showing a more detailed configuration of a queue 21a and a queue management table 21b.

FIG. 8 is a flowchart showing a transmission request acceptance process in the task control device 101.

FIG. 9 is a flowchart showing a reception request reception process in the task control device 101.

FIG. 10 is an explanatory diagram showing a state change of a queue 21a and a queue management table 21b.

FIG. 11 is a task control device 20 according to the second embodiment.
FIG. 3 is a block diagram showing a configuration of a 0.

FIG. 12 is a flowchart showing a transmission request acceptance process in the task control device 200.

FIG. 13 illustrates a task control device 30 according to the third embodiment.
FIG. 3 is a block diagram showing a configuration of a 0.

FIG. 14 is a flowchart showing a transmission request acceptance process in the task control device 300.

FIG. 15 is a flowchart showing a reception request receiving process in the task control device 300.

FIG. 16 illustrates a task control device 400 according to a fourth embodiment.
FIG. 3 is a diagram illustrating an example of hardware.

FIG. 17 is a task control device 400 in the processor X.
FIG. 3 is a block diagram showing the configuration of FIG.

18 shows a storage example of a processor management unit 1701. FIG.

FIG. 19 shows an example of the transmission data size of tasks A, B, and C.

FIG. 20 shows an example of the received data size of tasks A, B, and C.

FIG. 21 is a flowchart showing a transmission request acceptance process in the task control device 400.

FIG. 22 shows a task control device 50 according to the fifth embodiment.
FIG. 3 is a block diagram showing a configuration of a 0.

FIG. 23 is a flowchart showing a reception request receiving process in the task control device 500.

FIG. 24 is a task control device 600 according to the sixth embodiment.
FIG. 3 is a block diagram showing the configuration of FIG.

FIG. 25 is a flowchart showing a transmission request acceptance process in the task control device 600.

FIG. 26 is a flowchart showing processing contents of a proxy task 2401.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 CPU 2 Memory 3 I / O part 4-7 I / O part 10 Data storage part 11 Control part 11a CPU 11c Bus I / F part 11d Main memory 13 Remote control receiving part 14 Remote control 15 Receiving part 16 MPEG decoder 17 Video signal processing Units 21a to 23a queues 21b to 23b queue management table 101 task control device 102 transmission data size management unit 103 transmission request reception unit 104 data storage unit 105 reception data size management unit 106 reception request reception unit 108 data extraction unit 109 data transfer unit

Continued on the front page (72) Inventor ▲ Yoshi ▼ Kento Ii 1006 Kadoma Kadoma, Osaka Prefecture Inside Matsushita Electric Industrial Co., Ltd. (72) Inventor Hirofumi Tanaka 1006 Kazuma Kadoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd.

Claims (25)

[Claims] 1. A task control device for controlling data communication between a plurality of tasks, comprising: a data storage unit having an area for temporarily storing data to be transmitted by a task; Transmission request processing means for receiving a transmission request and transferring data to be transmitted in the first task to the data storage means; management means for managing the size of each data stored in the data storage means; Receiving a data reception request from the storage device and referring to the management unit, if data having a size equal to the reception data size required by the second task is stored in the data storage unit, the data having the size equal to the reception data size And a reception request processing means for transferring the request from the data storage means to the second task. 2. The reception request processing means according to claim 1, wherein: a reception size table for holding a reception data size required for each task; and a reception size table when a data reception request is received from a second task. A size determination unit that reads the received data size from the storage unit and a size of each data from the management unit, and determines whether or not data larger than the reception data size of the second task is stored in the data storage unit; And a second transfer unit for transferring data of a size equal to the received data size from the data storage unit to the task that has requested the reception when it is determined that data larger than the received data size is stored. Task control device. 3. The transmission request processing means according to claim 2, wherein: a transmission size table for holding a transmission data size required for each task; and a transmission size table when a data transmission request is received from the first task. Read the transmission data size of the task from the data storage means, and determine whether or not there is more free space in the data storage means. If there is a free space, the data to be transmitted by the first task is stored in the data storage means. A task control device, comprising: a first transfer unit that transfers the data. 4. The task control device according to claim 3, wherein the data storage means has a plurality of queue buffers for storing data in a first-in first-out manner, and the management means stores the data for each queue buffer. The data transmission request includes a designation of a queue buffer of a transmission data storage destination, and the data reception request includes a designation of a queue buffer of a reception data request destination. The vacancy determining means determines whether or not the queue buffer specified by the data transmission request has a vacancy equal to or larger than the transmission data size read from the transmission size table; It is determined whether or not the queue buffer specified in が あ る contains data larger than the reception data size read from the reception size table. Task control unit, characterized by. 5. The task control device according to claim 4, wherein the management unit is provided corresponding to a queue buffer,
A plurality of reception request buffers for temporarily storing data reception requests for which data larger than the reception data size has not been stored by the size determination unit, wherein the transmission request processing unit further includes a first task When a transmission request is received from the server and a reception request matching the transmission request is stored in the reception request buffer, the transfer by the first transfer unit is prohibited, and data is transferred from the first task to the second task. A task control device comprising direct transfer means for performing direct transfer. 6. The task control device according to claim 4, wherein the transmission request processing unit further includes a determination unit that determines whether a data transmission request from the first task satisfies a predetermined condition. The management means is further provided corresponding to the queue buffer, and prohibits the transfer of the transmission data of the data transmission request by the first transfer means when the determination means determines that the predetermined condition is satisfied. A plurality of transmission request buffers that temporarily hold the data transmission request, the reception request processing means further comprising: when a reception request is received, a transmission request matching the reception request is stored in the transmission request buffer. And a direct transfer unit for directly transferring data from the first task to the second task. 7. The task control device according to claim 3, wherein the data storage unit includes a plurality of queue buffers provided for each task and storing data in a first-in first-out manner. For each queue buffer, manage the stored data size and free data size, the data transmission request includes designation of a data transmission destination task, and the data reception request includes a data reception source task designation, The vacancy determining means determines whether or not there is the vacancy in the queue buffer corresponding to the task specified in the data transmission request, the size determining means, in the queue buffer corresponding to the task of the data reception request source, A task control device for determining whether there is data having a size equal to or larger than the received data size. 8. The task control device according to claim 7, wherein the management unit is provided corresponding to a queue buffer,
A plurality of reception request buffers for temporarily storing data reception requests for which data larger than the reception data size has not been stored by the size determination unit, wherein the transmission request processing unit further includes a first task When a transmission request is received from the server and a reception request matching the transmission request is stored in the reception request buffer, the transfer by the first transfer unit is prohibited, and data is transferred from the first task to the second task. A task control device comprising direct transfer means for performing direct transfer. 9. The task control device according to claim 7, wherein the transmission request processing unit further includes a determination unit that determines whether a data transmission request from the first task satisfies a predetermined condition. The management means is further provided corresponding to the queue buffer, and prohibits the transfer of the transmission data of the data transmission request by the first transfer means when the determination means determines that the predetermined condition is satisfied. A plurality of transmission request buffers that temporarily hold the data transmission request, the reception request processing means further comprising: when a reception request is received, a transmission request matching the reception request is stored in the transmission request buffer. And a direct transfer unit for directly transferring data from the first task to the second task. 10. A task control device used in a system having a plurality of processors, comprising a same number of task control units corresponding to the processors, and controlling data communication between tasks of the processors. A data storage unit having an area for temporarily storing data to be transmitted by a task; receiving a data transmission request from a first task of its own processor, and transmitting the data to a task of another processor; A processor determining means for determining whether the data is transmitted to another task; and
Transmission request processing means for transferring the data to be transmitted of the first task to the data storage means, and when it is determined that the data is to be transmitted to the task of another processor,
A data delivery means for delivering the transmission data to the data storage means of the other processor; a management means for managing the size of each data stored in the data storage means; Upon receiving a data reception request from the second task and referring to the management means, if data having a size equal to the reception data size required by the second task is stored in the data storage means, the reception data size And a reception request processing unit for transferring data having a size equal to the data size from the data storage unit to the second task. 11. The task control device according to claim 10, wherein the reception request processing means includes: a reception size table holding a reception data size for each task of the own processor; and a second task of the own processor. When a data reception request is received, a size determination unit that determines whether or not data having a size equal to the reception data size is stored in the data storage unit by referring to the reception size table and the management unit; When it is determined that data of a size equal to the data size is stored, a second transfer unit for transferring data of a size equal to the received data size from the data storage unit to the second task is provided. Task control device. 12. The task control device according to claim 11, wherein the transmission request processing means includes: a transmission size table for storing a transmission data size for each task of the own processor; When it is determined that the data is to be transmitted to the task, the transmission data size of the task is read from the transmission size table, and a vacancy determination unit that determines whether the data storage unit has the vacant data size. A first transfer unit for transferring transmission data to a data storage unit. 13. The task control device according to claim 12, wherein said data storage means has a plurality of queue buffers for storing data in a first-in first-out manner, and said management means is stored for each queue buffer. Managing the size of the data and the data size of the free space, the data transmission request includes a designation of a queue buffer of a transmission data storage destination, the data reception request includes a designation of a queue buffer of a reception data request destination, The vacancy determining means determines whether or not there is the vacancy in the queue buffer specified by the data transmission request, and the size determining means determines whether the received data size is in the queue buffer specified by the data reception request. A task control device for determining whether there is data of the same size. 14. A task control device used in a system having a plurality of processors, comprising a same number of task control units corresponding to the processors, and controlling data communication between tasks of the processors, wherein each task control unit comprises: A data storage unit having an area for temporarily storing transmission data between tasks; and a transmission for receiving a data transmission request from a first task of its own processor and transferring the transmission data from the first task to the data storage unit. Request processing means; managing means for managing the size of data stored in the data storage means; receiving a data reception request from a task of its own processor; receiving data from a task of another processor; A processor determining means for determining whether the data is received from the task; and a determination that the data is received from the second task of the own processor. When the data having the size equal to the reception data size required by the task is stored in the data storage unit with reference to the management unit, the data having the size equal to the reception data size is stored in the data storage unit. Receiving request processing means for transferring to a task of the other processor;
A data acquisition unit for acquiring data to be received from the data storage unit of the other processor. 15. The task control device according to claim 14, wherein the reception request processing unit includes: a reception size table that holds a reception data size for each task of the own processor; When it is determined that the data is received from the second task, whether or not data having a size equal to the received data size of the second task is stored in the data storage means by referring to the reception size table and the management means. And a second determining means for transferring data of a size equal to the received data size from the data storage means to the second task when it is determined that data of a size equal to the received data size is stored. A task control device comprising: a transfer unit. 16. The task control device according to claim 15, wherein the transmission request processing means includes: a transmission size table holding a transmission data size for each task of its own processor; and data transmission from a task of its own processor. Upon receiving the request, read out the transmission data size of the task from the transmission size table and determine whether there is enough free space in the data storage means. A first transfer unit for transferring the data to a data storage unit. 17. The task control device according to claim 16, wherein said data storage means has a plurality of queue buffers for storing data in a first-in first-out manner, and said management means stores the data for each queue buffer. The data transmission request includes a designation of a queue buffer of a transmission data storage destination, and the data reception request includes a designation of a queue buffer of a reception data request destination. The vacancy determining means determines whether or not the queue buffer specified by the data transmission request has a vacancy equal to or larger than the transmission data size read from the transmission size table; In the queue buffer specified in, there is data larger than the reception data size read from the reception data size table Task control unit and judging whether the. 18. A task control device used in a system having a plurality of processors, comprising a same number of task control units corresponding to the processors, and controlling data communication between tasks of the processors, wherein each task control unit comprises: Data storage means having an area for temporarily storing transmission data between tasks; receiving a data transmission request from a task of its own processor and transmitting it to a task of another processor or transmitting it to a task of its own processor Processor determination means for determining whether the transmission is to the task of its own processor, transmission request processing means for transferring transmission data from the task of the transmission request source to the data storage means, and a task of another processor. If it is determined to be sent to
A specific task execution unit for transferring the transmission data from the transmission requesting task to the data storage unit of the other processor by executing the specific task of the other processor; Receiving a data reception request from a task of its own processor and managing the size, and referring to the management means, data having a size equal to the reception data size required by the task is stored in the data storage means. And a reception request processing unit for transferring data having a size equal to the reception data size from the data storage unit to the task. 19. The task control device according to claim 18, wherein said reception request processing means includes: a reception size table for holding a reception data size for each task of its own processor; and a second task of its own processor. When a data reception request is received, a size determination unit that determines whether or not data having a size equal to the reception data size is stored in the data storage unit by referring to the reception size table and the management unit; When it is determined that data of a size equal to the data size is stored, a second transfer unit for transferring data of a size equal to the received data size from the data storage unit to the second task is provided. Task control device. 20. The task control device according to claim 19, wherein the transmission request processing unit includes: a transmission size table for storing a transmission data size for each task of the own processor; When it is determined that the data is to be transmitted to the task, the transmission data size of the task is read from the transmission size table, and a vacancy determination unit that determines whether the data storage unit has the vacant data size. A first transfer unit for transferring transmission data to a data storage unit. 21. The task control device according to claim 20, wherein the data storage unit has a plurality of queue buffers for storing data in a first-in first-out manner, and the management unit stores the data for each queue buffer. The data transmission request includes a designation of a queue buffer of a transmission data storage destination, and the data reception request includes a designation of a queue buffer of a reception data request destination. The vacancy determining means determines whether or not the queue buffer specified by the data transmission request has a vacancy equal to or larger than the transmission data size read from the transmission size table; Whether there is data in the queue buffer specified in, which is larger than the received data size read from the received size table Task control unit and judging. 22. A computer-readable storage medium storing a task control program for controlling data communication between tasks, the task control program receiving a data transmission request from a task, and buffering transmission data of the task. Transmission request processing means stored in the memory, management means for managing the size of data stored in the buffer memory, received data request from the task, received data size required by the task by referring to the management means If data of a size equal to is stored in the buffer memory,
A storage medium, which is realized by executing, by a computer, reception request processing means for transferring data having a size equal to the received data size from a buffer memory to the task. 23. A storage medium for use in a computer system having a plurality of processors, comprising a same number of task control programs as processors and storing a program for controlling data communication between tasks of the processors. The program receives a data transmission request from a task of its own processor, and determines whether the program is to be transmitted to a task of another processor or to a task of its own processor. Transmission request processing means for transferring transmission data from the task of the transmission requester to the buffer memory when transmission is determined; and transmission determination for transmission to a task of another processor,
Data delivery means for delivering transmission data from the task of the transmission request to the buffer memory of the other processor; management means for managing the size of the data stored in the buffer memory; and a data reception request from the task of its own processor. Then, if data having a size equal to the reception data size required by the task is stored in the buffer memory with reference to the management means, the data having the size equal to the reception data size is read from the buffer memory. A storage medium, which is realized by executing, by a computer, a reception request processing unit that transfers the request to a task. 24. A storage medium for use in a computer system having a plurality of processors, comprising a same number of task control programs as the processors and storing a program for controlling data communication between tasks of the processors. The program receives a data transmission request from a task of its own processor, and transmits transmission request processing data to the buffer memory from the task; a management means for managing the size of data stored in the buffer memory; A processor determination unit that receives a data reception request from a task of the processor of the processor and determines whether the data is received from a task of another processor or a task of the processor itself, and is determined to be reception from a task of the processor itself. Received by the task, refer to the management When data of a size equal to the data size is stored in the buffer memory, reception request processing means for transferring data of a size equal to the received data size from the buffer memory to the task, and reception of data from a task of another processor. When determined,
A storage medium characterized by being executed by a computer executing data acquisition means for acquiring data to be received from a buffer memory of another processor. 25. A storage medium for use in a computer system having a plurality of processors, comprising a same number of task control programs as the processors and storing a program for controlling data communication between tasks of the processors. The program receives a data transmission request from a task of its own processor, and determines whether the program is to be transmitted to a task of another processor or to a task of its own processor. Transmission request processing means for transferring transmission data from the task of the transmission requester to the buffer memory when transmission is determined; and transmission determination for transmission to a task of another processor,
By executing a specific task of the other processor, a specific task executing means for transferring the transmission data from the task requesting the transmission to the buffer memory of the other processor, and increasing the size of the data stored in the buffer memory. When a data receiving request is received from a task of its own processor and a data receiving request from the task of its own processor is referred to, and data of a size equal to the received data size required by the task is stored in the buffer memory, A storage medium, which is realized by executing, by a computer, reception request processing means for transferring data having a size equal to the received data size from a buffer memory to the task.