Multi-task processing system
Abstract
PURPOSE:To realize the multi-channel mechanism by a communication emulator by registering a request in an event list and actuating a dispatcher when some request is generated in the course of application operation, selecting a task to be executed from tasks in a ready state, and setting it to an operating state, and switching the task. CONSTITUTION:In the course of application operation, when a task A calls a service routine 41, this request is informed to an event manager 45 through a keyboard manager 44. The event manager 45 registers its request in an event list 47, informs it to a dispatcher 42, and the dispatcher 42 shifts the task which comes to a ready state earliest among the tasks of a ready state registered in a task list 46, to an executing state. Also, the task A in which an event is generated is registered as an event end waiting task. The task which comes to the executing state operates until a request to keyboard, a pipe and communication is issued, and switches the task. In such a way, a multi-channel mechanism can be realized by a communication emulator.
Term
Term ended
Projected expiry passed 6 July 2009, 17.2 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
1 claim: 1 independent, 0 dependent
- 1[Claim(s)] 【特許請求の範囲】 To a single task processing system which contains an operating system which can operate only by a single task only by it, A multiple processor which performs multiple managements of a task of operation is added, and it is the above-mentioned multiple processor, A keyboard manager who performs input management of a keyboard, and a pipe manager who notifies an event manager of event generating and an end per file, and performs communication between tasks, An interface for a driver who controls external optional equipment, If an event manager who manages systematically a demand from application to each above-mentioned manager is comprised and a certain demand occurs during application operation, A multitasking processing system the above-mentioned event manager registers the demand into an event list, and starts a dispatcher, and a dispatcher's choosing a task which should be performed from a task which is in a lady state, setting it as an operating state, and performing a task change. それのみではシングルタスクでしか動作できないオペレーティングシステムを内蔵するシングルタスク処理システムに、複数タスクの動作管理を行うマルチプルプロセッサを付加し、上記マルチプルプロセッサは、キーボードの入力管理を行うキーボードマネージャと、ファイルにつきイベント発生、終了をイベントマネージャに通知してタスク間通信を行うパイプマネージャと、外部オプション装置を制御するドライバのためのインターフェースと、上記各マネージャに対するアプリケーションからの要求を統一的に管理するイベントマネージャとから成り、アプリケーション動作中ある要求が発生すると、上記イベントマネージャは、その要求をイベントリストに登録してディスパッチャを起動し、ディスパッチャは、レディ状態となっているタスクより実行すべきタスクを選択して動作状態に設定しタスク切替えを行うことを特徴とするマルチタスク処理システム。
6 paragraphs, as filed
[Detailed Description of the Invention]
The object Co of [invention (Field of the Invention) This invention relates to the multitasking processing system which realizes multitasking operation on single task OS (operating system). (PRIOR ART) Conventionally, a communication terminal has many which perform a plurality of logical channel (henceforth, multi-channel) processings, and the example of the simple processing at the time of trying to perform an emulation for this on single O8 is shown in Drawing 2. Numerals A are the checks of a key buffer among a figure, when key human power suits, transmitting processing of a key code is performed to a host device, and that is told when there is nothing. Numerals B are extraction processing of a receive buffer, and are processed by the F I F O (First In First 0ut) buffer. There is a field which the thing to which logical channel can identify in receiving data. Numerals C are multiplexers and are divided by the identifier of the receiving data mentioned above in processing for every channel. (Object of the Invention) If the above-mentioned conventional example is followed, to the part which is treating each channel as an equivalent right of priority, it is satisfactory, but when a right of priority has a difference by each channel, a buffer management top problem arises. It is on extension of processing of each channel, when there is key human power processing, it is a problem, and further, when a priority occurs in the key processing, it becomes a problem increasingly and multi-channel correspondence is required. This invention is made in light of the above-mentioned circumstances, processing of each channel is respectively considered as one task, and it aims at providing the multitasking processing system which realizes the multi-channel mechanism in a communication emulator. Also let it be the object to provide the environment which can create Program in multitasking on single O8 without task management required for multitasking, resource control, etc.
[Elements of the Invention] (A means for solving problem and operation) Present invention, To a single task processing system which contains an operating system which can operate only by a single task only by it, A multiple processor which performs multiple managements of a task of operation is added, and it is the above-mentioned multiple processor, A keyboard manager who performs human power management of a keyboard, and a pipe manager who notifies an event manager of event generating and an end per file, and performs communication between tasks, An interface for a driver who controls external optional equipment, If an event manager who manages systematically a demand from application to each above-mentioned manager is comprised and a certain demand occurs during application operation, The above-mentioned event manager registers the demand into an event list, and starts a dispatcher, and a dispatcher chooses a task which should Long life from a task which is in a lady state, and sets it as an operating state, and it considers it as composition which performs a task change. By this, it becomes realizable [ a multi-channel mechanism in a communication emulator ]. That is, it becomes possible to consider processing of each channel as one task respectively. (EXAMPLE) Hereinafter, a present invention example is described using a drawing. Drawing 1 is a block diagram showing an example of the present invention. In a figure, 1 is an application program and task 1~4 processes each logical channel. 2 is an option board part and consists of a driver who controls a board and a board. A driver has an interface over an application program. 3 is the hardware on a machine on which the present invention functions. 4 is a multiple processor added by the present invention, and comprises the following components. Numerals 41 are service routines, notify a demand (event) from a driver of application program 1 and option board part 2 to each functional block, and return the status to a demand person at the time of an end of an event. 42 is a dispatcher, and an event is completed and it makes an operating state a task registered into task list 42 in the state of the lady. 43 is a pipe manager and notifies event manager 45 of generating about an event about a pipe, an end, etc. 44 is a keyboard manager and notifies event manager 45 of generating about an event about a keyboard input, an end, etc. 45 is an event manager and registers with event list 47 about an event which occurred newly. When an event is completed, elimination from an event list and a notice to dispatcher 42 are performed. Are a task Control blotter and EVB of inside TCB of a figure is an event block. Hereinafter, operation of a present invention example is explained. Application is explained as a communication emulator as an example. First, option board 2 turns into a communication board which connects a circuit physically. A certain moment under application operation is taken for an example. At this time, task A presupposes that other tasks were registered with evening Sfrist 46 in the state of the lady by a run state. If service routine 41 is called since task A has a user's key human power at this time, event manager 5 will be notified of this demand via Keyboard manager 44. As a waiting event for key human power in which the demand is not ended, event manager 45 registers with event list 47, and notifies to Dispuncture 42. Dispatcher 42 puts into a run state a task which changed into a lady state earliest among tasks of a lady state registered into task list 46. A task (in this case, task A) which generated an event is registered as a task of event End Wait. A task which was in a run state operates until it publishes a demand to a keyboard, a pipe, and communication. This serves as a change of a task. Then, when task A registered into event list 47 as a waiting event for a key in upper example as to how an event is ended is taken for an example, it is in this state until a user inputs a key. If human power of the key is carried out, an interrupt will occur from a keyboard. This interruption routine notifies event manager 45, and is removed from event list 47. Dispatcher 42 changes task A into a lady state. Since this operation is performed by interruption, it is carried out also where other tasks are performed. In the case of a communication board, a driver reports that an interrupt occurred via a service routine. reading conversely and receiving a demand, when it reads to a demand of writing and a demand occurs via a service routine about a pipe -- Tori of an end of an event of a write request -- it becomes. Multitasking operation is performed by the above.
[Effect of the Invention] According to the present invention, it becomes realizable [ the multi-channel mechanism in a communication emulator ] like explanation above. That is, it becomes possible to consider processing of each channel as one task respectively. The environment which can create a program in multitasking by this on O8 without task management required for multitasking, resource control, etc. can be provided.
[Brief Description of the Drawings]
The block diagram in which Drawing 1 shows the example of the present invention, and Awesome 2 figure are flow charts which show operation of the communication emulator in a conventional example. 1 ... application program, 2 ... option board part, 3 ... hardware, 4 ... multiple processor, 41 ... service routine, 42 ... dispatcher, 43 ... pipe manager, 44 ... keyboard manager, 45 ... event manager, 46 ... task list, 47 ... event list.
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| JP2001022498A | Cited by | Japan | Search report |
| JP2004362564A | Cited by | Japan | Examiner |
| US8271997B2 | Cited by | United States of America | Applicant |
| US7962568B2 | Cited by | United States of America | Applicant |
| US8621487B2 | Cited by | United States of America | Applicant |
| US8087034B2 | Cited by | United States of America | Applicant |
3 priority claims, no other members on record
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 17442989 | Japan | A | |
| 1174429 | – | – | – |
| JP19890174429 | – | – | – |
Numbers
- Publication
- 3-40035
- Publication, DOCDB
- H0340035
- Publication, EPODOC
- JPH0340035
- Application
- 1174429
- Application, DOCDB
- 17442989
- Application, EPODOC
- JP19890174429
Titles2
- English
- MULTI-TASK PROCESSING SYSTEM
- Japanese
- 【発明の名称】マルチタスク処理システム
Classification
- IPC, 2
- G06F9 46
- G06F9 54