Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
JP2818521B2 - Task communication method - Google Patents
[go: Go Back, main page]

JP2818521B2 - Task communication method - Google Patents

Task communication method

Info

Publication number
JP2818521B2
JP2818521B2 JP15164992A JP15164992A JP2818521B2 JP 2818521 B2 JP2818521 B2 JP 2818521B2 JP 15164992 A JP15164992 A JP 15164992A JP 15164992 A JP15164992 A JP 15164992A JP 2818521 B2 JP2818521 B2 JP 2818521B2
Authority
JP
Japan
Prior art keywords
transmission
task
queue
data
notification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
JP15164992A
Other languages
Japanese (ja)
Other versions
JPH05342020A (en
Inventor
春樹 若狭
Original Assignee
日本電気ソフトウェア株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気ソフトウェア株式会社 filed Critical 日本電気ソフトウェア株式会社
Priority to JP15164992A priority Critical patent/JP2818521B2/en
Publication of JPH05342020A publication Critical patent/JPH05342020A/en
Application granted granted Critical
Publication of JP2818521B2 publication Critical patent/JP2818521B2/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Description

【発明の詳細な説明】DETAILED DESCRIPTION OF THE INVENTION

【0001】[0001]

【産業上の利用分野】本発明はタスク間通信方、特に
複数のタスクがキューイング(待行列)方式によってデ
ータの受け渡しを行なうマルチタスクシステムのタスク
間通信方に関する。
The present invention relates to a inter-task communication how, passing about the task communication how multitasking system for data in particular by a plurality of tasks queued (queue) scheme.

【0002】[0002]

【従来の技術】従来、この種のタスク間通信方は、図
2にデータの流れを示すように、タスクA21はタスク
B22の待行列23に通信を示すデータを追加すること
によって、タスクB22への送信を完了する。タスクB
22は待行列23からタスクA21が入力したデータを
取出すことによって、タスクA21からのデータを受信
するようになっている。
BACKGROUND OF THE INVENTION Conventionally, inter-task communication how this type, to indicate the flow of data in FIG. 2, the task A21 by adding the data indicating the communication in queue 23 of the task B22, task B22 Complete sending to. Task B
22 receives the data from the task A21 by extracting the data input by the task A21 from the queue 23.

【0003】[0003]

【発明が解決しようとする課題】上述した従来のタスク
間通信方は、送信側タスクが受信側タスクによる受信
の完了を待合せるという同期型の通信を行なう場合に、
送信側タスクは受信側タスクがデータを待行列から取出
すタイミングを知ることができないため、受信側タスク
から送ったデータを受取ったという応答を待たなければ
ならないという欠点がある。また一旦、待行列に入力し
たデータは、入力直後に取消す必要が生じた場合でも、
容易に取消すことができないという欠点がある。
SUMMARY OF THE INVENTION An object of the conventional inter-task communication how described above, if the sending task communicates synchronous that waits for the completion of reception by the receiving task,
Since the transmitting task cannot know the timing when the receiving task takes out the data from the queue, it has a disadvantage that it has to wait for a response indicating that the data sent from the receiving task has been received. Also, once data entered in the queue needs to be canceled immediately after input,
There is a disadvantage that it cannot be easily canceled.

【0004】[0004]

【課題を解決するための手段】本発明のタスク間通信方
は、複数のタスクがキューイング方式によってデータ
の受け渡しを行なうマルチタスクシステムのタスク間通
信方において、送信側タスクはデータの送信に先立っ
て待行列に送信予告通知を追加し、受信側タスクはこの
送信予告通知を受けデータ格納領域を確保して待行列に
受信準備完了通知を追加し、この受信準備完了通知を受
けた前記送信タスクは受信準備完了通知により知らされ
たデータ格納領域に送信データを格納した後に待行列に
送信データ格納通知を追加することによりデータの送信
を完了し、送信側タスクが待行列に前記送信予告通知を
追加した後でデータの送信を取止めるときに、送信側タ
スクは待行列に送信取消通知を追加し、この送信取消通
知を受けた受信側タスクは送信側タスクから受けた前記
送信予告通知はなかったものとすることを特徴とする
SUMMARY OF THE INVENTION An inter-task communication method according to the present invention.
Law, in multiple tasks task communication how multitasking system for transfer of data by queuing method, the sending task adds a transmission advance notice queue prior to transmission of the data, receiving task the transmission advance notice to ensure accept data storage area to add the reception preparation completion notification to the queue, the data stored being informed by the transmission task reception preparation completion notification receiving the reception preparation completion notification When data transmission is completed by adding a transmission data storage notification to the queue after storing the transmission data in the area, and when the transmitting task stops transmitting data after adding the transmission advance notification to the queue. Then, the transmitting task adds a transmission cancellation notification to the queue, and the receiving task that has received the transmission cancellation notification does not receive the transmission advance notification notification received from the transmitting task. Characterized in that it is assumed that Tsu.

【0005】[0005]

【実施例】次に、本発明について図面を参照して説明す
る。
Next, the present invention will be described with reference to the drawings.

【0006】図1(a)は本発明の一実施例を説明する
ための図で、送信側タスクが受信側タスクによる送信デ
ータの受信を待合せる場合を示している。図1(a)の
実施例はタスク1,タスク2,タスク1が入力する待行
列3,タスク2が入力する待行列4を有し、送信予告通
知101,受信準備完了通知201,送信データ格納通
知102の3種のデータが用いられる。
FIG. 1A is a diagram for explaining an embodiment of the present invention, in which a transmitting task waits for reception of transmission data by a receiving task. The embodiment of FIG. 1A has a task 1, a task 2, a queue for inputting task 1, and a queue 4 for inputting task 2, and has a transmission advance notice 101, a reception preparation completion notification 201, and transmission data storage. Three types of data of the notification 102 are used.

【0007】タスク1は送信予告通知101を待行列3
へ追加し、タスク2からの受信準備完了通知201が待
行列4に追加されるのを待つ。タスク2からの受信準備
完了通知201を待行列4から取出したタスク1は、そ
の受信準備完了通知201に指定された領域に送信デー
タを格納し、送信データ格納通知102を待行列3に追
加する。一方、タスク2は、タスク1からの送信予告通
知101を待行列3から取出したとき、送信データを格
納する領域を確保し、その領域を示す情報を付加した受
信準備完了通知201を待行列4へ追加し、タスク1か
らの送信データ格納通知102が待行列3に追加される
のを待つ。
[0007] The task 1 is to send the transmission advance notice 101 to the queue 3
And waits for the reception preparation completion notification 201 from the task 2 to be added to the queue 4. The task 1 that has taken out the reception preparation completion notification 201 from the task 2 from the queue 4 stores the transmission data in the area designated by the reception preparation completion notification 201, and adds the transmission data storage notification 102 to the queue 3. . On the other hand, when the task 2 takes out the transmission notice notice 101 from the task 1 from the queue 3, it reserves an area for storing the transmission data, and sends the reception preparation completion notice 201 to which information indicating the area is added, in the queue 4. And waits for transmission data storage notification 102 from task 1 to be added to queue 3.

【0008】図1(b)は一実施例を説明するための図
で、送信タスクが送信を取消す場合を示している。この
場合は図1(a)の構成において、送信取消通知103
のデータが追加され、送信データ格納通知102は用い
られず、受信準備完了通知201は用いられないか、用
いられても捨てられる。
FIG. 1B is a diagram for explaining one embodiment, showing a case where a transmission task cancels transmission. In this case, in the configuration of FIG.
Is added, the transmission data storage notification 102 is not used, and the reception preparation completion notification 201 is not used or discarded even if used.

【0009】タスク1が送信予告通知101を待行列3
に追加した後に、その送信を取消す場合には、タスク1
は待行列4に入力された受信準備完了通知201を取出
すことなく、送信取消通知103を待行列3へ追加す
る。タスク2はタスク1からの送信予告通知101に続
くタスク1からの送信取消通知103を待行列3から取
出した時点で、タスク1からの送信予告通知101は無
かったものとして破棄する。またタスク2が受信準備完
了通知201を待行列4へ追加した後で、タスク1から
の送信取消通知103を待行列3から取出した場合に
は、タスク2は送信データ格納通知102を待つことを
止め、タスク1からの送信予告通知101は無かったも
のとする。なお、タスク1は待行列3に送信予告通知1
01を追加する前に、待行列4に受信準備完了通知20
1があるかどうかを調べ、有る場合には事前に取出して
破棄する。
[0009] Task 1 sends the transmission advance notice 101 to the queue 3
If you cancel the transmission after adding it to Task 1,
Adds the transmission cancellation notification 103 to the queue 3 without taking out the reception preparation completion notification 201 input to the queue 4. When the task 2 takes out the transmission cancellation notice 103 from the task 1 following the transmission announcement notice 101 from the task 1 from the queue 3, the task 2 discards the transmission announcement notice 101 from the task 1 as if it did not exist. Further, if task 2 adds reception ready completion notification 201 to queue 4 and then removes transmission cancellation notification 103 from task 1 from queue 3, task 2 waits for transmission data storage notification 102. It is assumed that the transmission advance notice 101 from the task 1 is not received. Note that task 1 is sent to queue 3 and sent
01 is added to the queue 4 before the reception preparation notification 20 is added.
It is checked whether 1 exists, and if it exists, it is taken out and discarded in advance.

【0010】[0010]

【発明の効果】以上説明したように本発明は、送信予告
通知を待行列に入力し、送信データの格納領域が指定さ
れた受信準備完了通知を受けて、送信データを格納する
ことにより、同期型の通信において受信側からの応答を
不要とし、送信取消通知を待行列に入力することで、送
信予告通知の待行列への入力後も送信の取消しを容易に
できるという効果がある。
As described above, according to the present invention, a transmission advance notice is input to a queue, a reception preparation completion notification in which a transmission data storage area is designated is received, and transmission data is stored. By eliminating the need for a response from the receiving side and inputting the transmission cancellation notification to the queue in the type of communication, the transmission can be easily canceled even after the transmission advance notice is input to the queue.

【図面の簡単な説明】[Brief description of the drawings]

【図1】本発明の一実施例を説明するための図である。FIG. 1 is a diagram for explaining an embodiment of the present invention.

【図2】従来のタスク間通信方のデータの流れを示す
図である。
2 is a diagram showing a flow of data of a conventional inter-task communication how.

【符号の説明】[Explanation of symbols]

1,2 タスク 3,4 待行列 101 通信予告通知 102 送信データ格納通知 103 送信取消通知 201 受信準備完了通知 1, 2, 3, 4 Queue 101 Communication Notice 102 Transmission Data Storage Notification 103 Transmission Cancel Notification 201 Reception Ready Completion Notification

フロントページの続き (56)参考文献 特開 平4−97436(JP,A) 特開 平2−208734(JP,A) 特開 平2−234234(JP,A) 特開 昭59−178049(JP,A) 特開 昭63−157243(JP,A) 特開 平2−51761(JP,A) 特開 昭63−296533(JP,A) 特開 平1−216651(JP,A) 特開 平2−249036(JP,A) 特開 昭58−169274(JP,A) 特開 平2−253448(JP,A) (58)調査した分野(Int.Cl.6,DB名) G06F 9/46 G06F 13/00 G06F 13/38 G06F 15/163 H04L 11/00 H04L 13/08Continuation of the front page (56) References JP-A-4-97436 (JP, A) JP-A-2-208734 (JP, A) JP-A-2-234234 (JP, A) JP-A-59-178049 (JP, A) JP-A-63-157243 (JP, A) JP-A-2-51761 (JP, A) JP-A-63-296533 (JP, A) JP-A-1-216651 (JP, A) 2-249036 (JP, A) JP-A-58-169274 (JP, A) JP-A-2-253448 (JP, A) (58) Fields investigated (Int. Cl. 6 , DB name) G06F 9/46 G06F 13/00 G06F 13/38 G06F 15/163 H04L 11/00 H04L 13/08

Claims (1)

(57)【特許請求の範囲】(57) [Claims] 【請求項1】 複数のタスクがキューイング方式によっ
てデータの受け渡しを行なうマルチタスクシステムのタ
スク間通信方において、送信側タスクはデータの送信
に先立って待行列に送信予告通知を追加し、受信側タス
クはこの送信予告通知を受けデータ格納領域を確保して
待行列に受信準備完了通知を追加し、この受信準備完了
通知を受けた前記送信タスクは受信準備完了通知により
知らされたデータ格納領域に送信データを格納した後に
待行列に送信データ格納通知を追加することによりデー
タの送信を完了し、送信側タスクが待行列に前記送信予
告通知を追加した後でデータの送信を取止めるときに、
送信側タスクは待行列に送信取消通知を追加し、この送
信取消通知を受けた受信側タスクは送信側タスクから受
けた前記送信予告通知はなかったものとすることを特徴
とするタスク間通信方
1. A plurality of tasks task communication how multitasking system for transfer of data by queuing method, the sending task adds a transmission advance notice queue prior to transmission of the data, reception Side task
Click adds a reception preparation completion notification to the queue to ensure accept data storage area of the transmission advance notice, the transmission task which has received the reception preparation completion notification was informed by the reception preparation completion notification data After the transmission data is stored in the storage area, the transmission of the data is completed by adding the transmission data storage notification to the queue, and the transmitting task stops the transmission of the data after adding the transmission advance notification to the queue. sometimes,
The transmitting task adds a transmission cancellation notification to a queue, and the receiving task receiving the transmission cancellation notification does not receive the transmission advance notification received from the transmitting task. Law .
JP15164992A 1992-06-11 1992-06-11 Task communication method Expired - Fee Related JP2818521B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP15164992A JP2818521B2 (en) 1992-06-11 1992-06-11 Task communication method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP15164992A JP2818521B2 (en) 1992-06-11 1992-06-11 Task communication method

Publications (2)

Publication Number Publication Date
JPH05342020A JPH05342020A (en) 1993-12-24
JP2818521B2 true JP2818521B2 (en) 1998-10-30

Family

ID=15523187

Family Applications (1)

Application Number Title Priority Date Filing Date
JP15164992A Expired - Fee Related JP2818521B2 (en) 1992-06-11 1992-06-11 Task communication method

Country Status (1)

Country Link
JP (1) JP2818521B2 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0877024A (en) * 1994-09-06 1996-03-22 Nec Corp Message transfer system
JP3882760B2 (en) 2003-02-18 2007-02-21 株式会社デンソー Inter-task communication method, program, recording medium, electronic device

Also Published As

Publication number Publication date
JPH05342020A (en) 1993-12-24

Similar Documents

Publication Publication Date Title
JPH06309252A (en) Interconnection interface
JPH0816540A (en) Message communication method for parallel computers
JPH07311750A (en) Parallel computer
JP2818521B2 (en) Task communication method
EP0578496B1 (en) Job execution method in multi-CPU system
JPH055414B2 (en)
JPS62126457A (en) Distributed data processing system
JPH09259051A (en) Alarm notification processing method
JP3216879B2 (en) Deletion of transfer data and status display device in delay type transfer function
JPS597987B2 (en) Data transmission control method between arithmetic control elements
JP3133413B2 (en) Task omission control method
JP2752456B2 (en) Channel device
JP2610106B2 (en) Page request processing system and method
JPS61141063A (en) Suspension resumption system of file transfer
JPH02118841A (en) Input queue control system
JPS62235898A (en) Remote supervisory and controlling slave station equipment
JPH05303503A (en) Synchronous message communication device
JPH10320345A (en) Bus controller
JPS6110345A (en) Transmission waiting control system in loop communication system
JPH09200292A (en) Data transmission method and apparatus
JPH0628287A (en) Synchronous message communication method and synchronous message communication device
JPH04113442A (en) Inter-processor communication system
JPH0235500B2 (en)
JPH0235850A (en) Exclusivecontrol system for pre-communication processor
JPH06326717A (en) Bus type communication equipment

Legal Events

Date Code Title Description
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 19980721

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

S531 Written request for registration of change of domicile

Free format text: JAPANESE INTERMEDIATE CODE: R313531

R350 Written notification of registration of transfer

Free format text: JAPANESE INTERMEDIATE CODE: R350

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20070821

Year of fee payment: 9

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20080821

Year of fee payment: 10

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20080821

Year of fee payment: 10

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20090821

Year of fee payment: 11

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20090821

Year of fee payment: 11

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20100821

Year of fee payment: 12

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20110821

Year of fee payment: 13

LAPS Cancellation because of no payment of annual fees