JP2001216170A - Operation method incorporating exclusive polling processing, operating system incorporating exclusive polling processing - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce stand-by time for saving of data and startup of writing, etc., attended with interruption in an O/S. SOLUTION: In this operating system to perform a multi-task processing to control an I/O driver by the interruption, a step to prohibit an interruption request to a driver after completion of a driver processing to a device on the basis of the interruption request, a step to investigate a state of the device by polling and to perform the processing and a step to release prohibition of the interruption request after polling is performed for prescribed period are provided.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to interrupt processing of an operating system of an information processing apparatus, and more particularly to a method and an apparatus for reducing a response time to an interrupt from an I / O device.

[0002]

2. Description of the Related Art As a conventional interrupt processing of an information processing apparatus, for example, there has been one as disclosed in Japanese Patent Application Laid-Open No. 6-236287. FIG. 22 is a diagram showing a configuration for performing such an interrupt process.

[0003] In this configuration, a thread management table 1703, an I / O queue 1704, and a thread management table 1703 are provided so that an operating system (OS) can perform I / O processing in multiple threads regardless of whether it is a multitask or a single task.
It has a ready queue 1705, a scheduler 1708, and a dispatcher 1709, and has functions necessary for performing multi-thread processing in its configuration. This allows the device driver to perform multi-thread processing independently of the OS function. When an interrupt is received from the device,
The scheduler 1708 determines the thread to execute, and the dispatcher 1709 context switches to the next thread to execute. The thread management table 1703 has context information necessary for context switching.

[0004] In such interrupt processing of the information processing apparatus, the OS can perform multi-thread I / O processing irrespective of multitasking or single tasking. Perform the operation. Then, in the case of an I / O process in which interrupts frequently occur in a very short time, such as an I / O request for a high-speed network, overhead for context switching between multi-threads occurs. This context switch process is a process of saving the processor information and thread information of the currently executing thread and writing and returning the processor information and thread information of the newly activated thread to the vacant area. The same processing is also performed when performed within the mechanism of the prior art, and a certain processing time depending on the memory performance, for example, 20 μsec is required in accordance with the save and write start, and when the OS shifts to another processing. And another 20 μs. Of course, in addition to this, for example, 100 μsec is required to execute the interrupt processing itself.

[0005]

The conventional OS operates as described above. In addition to the substantial execution time (for example, 100 .mu.sec), the conventional OS saves information from the memory area for a large number of interrupts and starts writing. The time before and after (total, e.g.
Second), and there is a problem that the processing time becomes longer.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problem. First, an I / O driver in an I / O driver is provided.
After the processing routine completes the I / O processing, the processing is performed by polling the status register of the I / O device for a certain period of time in place of its own interrupt, and therefore, the processing time is shortened without saving and starting of writing.

[0007]

A dedicated polling processing embedded operating method according to the present invention provides a device based on an interrupt request in an operating system which performs a multitask process for controlling an I / O (input / output) driver by an interrupt. Prohibiting the interrupt request to the driver after completing the driver processing to the driver, checking the status of the device by polling and processing, and releasing the interrupt request after polling for a predetermined period And the step of performing.

[0008] Further, whether or not polling is possible is determined according to the actual result of the interrupt interval.

Further, priority information is determined, and whether or not polling is permitted is determined based on the priority information.

Further, the load status of the operating system is checked, and if the load status is equal to or less than a predetermined value, polling is performed.

Alternatively, in an operating system that performs a multitask process for controlling an I / O driver by an interrupt, after executing the process corresponding to the interrupt request, if there is no other interrupt request in the idle state, the specific device And polling the driver to check the status of this device.

Still further, a specific device is registered in a plurality of lists, and in a polling process step, when the operating system is idle, the plurality of registered devices are polled in a predetermined order and each device is polled. This is a step of checking the state of the device and performing processing.

Still further, the method further comprises a step of recording, for each device, a ratio or the number of times the actual processing by the polling has been executed, and if the ratio or the number of executions per unit time is equal to or more than a predetermined value, the subsequent polling is continued. I made it.

An operating system incorporating a dedicated polling process according to the present invention is an operating system which performs a multitask process for controlling an I / O driver by an interrupt. A program that prohibits an interrupt request to the driver, checks the status of the device by polling, processes the device, performs polling for a predetermined period of time, and then releases the prohibition of the interrupt request to the driver.

Alternatively, in an operating system which performs a multitask process for controlling an I / O driver by an interrupt, after executing a process corresponding to an interrupt request, an idle thread which operates preferentially when there is no other interrupt request in an idle state. This idle thread checks the device status by polling the driver of a specific device and performs processing.

[0016]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 First, a description will be given of a first embodiment of the present invention in which a program for performing necessary processing by looking at a device status register by polling in an OS is incorporated. FIG. 1 is a configuration diagram of a part relating to interrupt processing of an operating system according to Embodiment 1 of the present invention. In the figure, reference numeral 101 denotes an information processing apparatus, 102 denotes an I / O device connected to the information processing apparatus, and in the present embodiment, a network controller is used as an example. An operating system 110 controls and manages the information processing apparatus. Reference numeral 111 denotes an interrupt dispatch table in the operating system. When an interrupt is received from an I / O device or the like, an interrupt handler 1 of the I / O driver corresponding to the interrupt type is provided.
13 is a table for calling. Reference numeral 112 denotes a network driver as an example of an I / O driver in the present embodiment. I / O for each I / O device 102
An O driver 112 exists, and the I / O driver 112 has an interrupt handler 113 that performs interrupt processing. Also I /
The O driver operates in a normal thread context to control the I / O device and send and receive data.
It has an / O processing routine 114. I / O device 102
Has a status register 121 for notifying the status of the I / O device such as the occurrence of an interrupt or an error.

The operation of the OS according to the first embodiment of the present invention will be described with reference to FIG. In the first embodiment, steps S104 (hereinafter step descriptions are omitted) to S104
The part up to 108 is new. First, when an interrupt is received from an I / O device, the operating system context switches to a common interrupt handler of the operating system in step S101 as in the related art, refers to the interrupt dispatch table, and determines the corresponding I / O from the interrupt type.
Call the interrupt driver of the O driver. In the present embodiment, a network controller will be described as an example of the I / O device 102 that raised the interrupt, and a network driver will be described as an example of the corresponding I / O driver 112. S
At 102, an interrupt handler 113 of the network driver
Executes the interrupt processing. I / O after completion of this interrupt processing
The processing routine 114 is called. Next, in S103, the I / O processing routine of the network driver performs I / O processing corresponding to the interrupt, for example, processing for receiving data from the network. The processing from S101 to S103 is the same as the conventional operation.

After completion of S103, in S104, an interrupt from the I / O device corresponding to the interrupt, here, the network controller is prohibited. This is the corresponding I / O
This is to detect the occurrence of an interrupt from the device by polling. Further, in S105, the status register of the network controller is polled to check whether an interrupt from the network controller has arrived. S1
The polling of 05 is continued for a specified number of times or for a specified time. If an interrupt is detected in S105, the I / O processing routine 114 remains in the context of the I / O processing routine 114 in S107 and S10
An interrupt process for the same network controller as the process performed in step 2 is performed. Then, the process returns to S103, where the I / O processing of the network driver corresponding to the next interrupt is performed again. If the arrival of the interrupt is not detected by the specified number of times or the specified time in S106, the polling is abandoned, the prohibition of the interrupt from the network controller is released in S108, and the process returns to the conventional processing in S109. When an interrupt from another I / O device occurs during the polling in S105 and S106, the inhibition of the interrupt from the network controller is released in S110, and the conventional interrupt processing is performed on the other device that generated the interrupt. . As described above, processes other than the polling I / O device are performed on an interrupt basis as in the related art.

According to the interrupt processing of the operating system according to the first embodiment, the I / O driver
After the I / O processing routine completes the I / O processing, the I / O processing routine
Since the status register of the / O device is polled and the next interrupt is awaited, in an environment where a large number of interrupts are generated in a short time, the interrupt processing is delayed by the context switch between the interrupt handler and the I / O processing. Can be reduced.

If the I / O processing is required for each polling and the polling interval is less than twice the sum of the time required for the saving by the interruption and the start of the writing, the merit of this method can be used. The setting of the polling time is obtained, for example, by the configuration shown in FIG. That is, FIG. 3 shows the operating system 110 in addition to the configuration of FIG.
have. The context switch time information 211 is transmitted from the operating system 110 to the information processing apparatus 101.
The time required to perform the context switch is measured or the result of the setting is stored. The interrupt interval time information table is a table corresponding to each interrupt entry of the interrupt dispatch table 111, and measures a time interval from the last interrupt occurrence to the present interrupt occurrence, and has a mode value.

The operation of the configuration shown in FIG. 3 will be described with reference to FIG.
The process (step) having the same number as that in FIG.
Means that the processing described in the above section is performed. When an interrupt is received from an I / O device, first, in step S201, an interrupt interval time is obtained from the time at which the previous interrupt was received from the corresponding I / O device and the current interrupt time. By updating, the mode value of the interrupt interval time is obtained. The mode value of the interrupt interval time is set in an entry of the interrupt interval time information table corresponding to the I / O device. Thereafter, the processes of S101, S102, and S103 are performed in the same manner as in FIG.
After the completion, in S203, the mode of the interrupt interval time is newly obtained by referring to the entry of the interrupt interval time information 212 corresponding to the I / O device, and is compared with the context switch time information 211. By these two times, I
It is determined whether to wait for an interrupt by polling the / O device.

In FIG. 4, for example, when the mode value of the interrupt interval time is larger than twice the context switch time, the process proceeds to S109 without waiting for the polling of the interrupt, and it is determined that the process returns to the normal process. This is because, as described above, it is considered that the processing by polling is faster if the number is less than twice. If the mode value of the interrupt interval time is less than twice the context switch time in S203, S
An interrupt wait is performed by polling of 105. If an interrupt is detected during this time, the interrupt process is performed in S107 in the context of the I / O processing routine. If the arrival of the interrupt is not detected by the polling twice as long as the context switch time in S204, the polling is abandoned.
Execute S108 and S109 and return to the conventional processing.

Embodiment 2 FIG. Processing by polling
This is effective when interrupts from a specific device controller occur frequently. However, a system that appropriately switches between the original interrupt and the subsequent save and write start processing according to the priority and the load status of the OS from the viewpoint of the OS is further required. It is valid. FIG. 5 is a configuration diagram of an interrupt processing portion of the operating system according to the embodiment of the present invention.
In the present embodiment, in addition to the first embodiment, a case where the communication packet 311 of the network has the priority information 312 or the priority information 313 of the application that has made the processing request is included, and the I / O driver Priority information 31
It is determined whether polling for an interrupt is to be performed with reference to the process priority 2 and the processing priority 313.

The operation of the configuration of this embodiment will be described with reference to FIGS. Note that, in the subsequent steps as well, steps having the same numbers as those in the preceding figures perform the same corresponding operations. In FIG.
When an interrupt is received, I / O processing corresponding to the interrupts in S101, S102, and S103 is performed. Then newly S30
In step 2, the CPU refers to the priority information 312 in the received packet received by the corresponding interrupt, and determines whether the priority is larger than a value preset in the system. This set value is a threshold value for determining whether to wait for the arrival of a packet by polling in order to perform high-speed reception processing. Here, it is expected that a high-priority packet to be received at a high speed subsequently arrives after a high-priority packet. If a high-priority packet is received in S302 based on this assumption, polling is performed in S105, and the next network packet reception interrupt is awaited. Polling continues for a specified time or a specified number of times. The method of Embodiment 1 can be used for the method of determining the polling time. If the priority of the received packet is low in S302, it is determined that high-speed reception is not necessary, and the process returns to the conventional process without polling.

In the case of an I / O processing request from an application, it operates as shown in FIG. The application is
In step S303, an I / O processing request is issued, and a completion notification interrupt is awaited. At this time, the processing priority 313 of the application is referred to in S304, and it is determined whether the processing priority is larger than a specified value set in the system. If a processing request is received from a process having a higher priority than the set threshold value and higher priority in S304, an interrupt from the corresponding I / O device is prohibited in S305, and the status register of the corresponding I / O device is polled in S306. Wait for interrupt completion. When an interrupt is detected in this way, the I / O processing routine performs completion processing in S308, and cancels the inhibition of the interrupt from the corresponding I / O device in S309. If the completion interrupt is not received during the polling for the designated time in S307, the polling is abandoned, and the inhibition of the interrupt is released in S309.

As described above, the interrupt processing of the operating system according to the present embodiment is performed based on the received packet of the network and the priority information of the application.
Since it is determined whether or not to perform polling waiting for an interrupt, the response time to an interrupt is reduced by polling only high-priority processing, and unnecessary CPU processing by polling is eliminated for low-priority processing. be able to.

An example in which polling is performed when the load on the OS is low will be described. FIG. 8 is a configuration diagram showing an interrupt processing portion of another operating system according to the second embodiment. In the configuration of FIG. 8, in addition to the first embodiment, the operating system has a table of CPU load information 411. The CPU load is a value determined by a CPU usage rate, a queue length of executable processing, and the like. In the configuration shown in the figure, it is determined whether or not polling for an interrupt is to be performed by referring to the CPU load information 411.

The operation of the configuration shown in FIG. 8 will be described with reference to FIG. Steps S101, S102 and S103 are executed. Thereafter, in S402, the current CPU load information is referred to, and C
It is determined whether the PU load value is larger than a value set in the system. This set value is a threshold value for determining whether or not to stop polling in order to prevent performance degradation due to a high load on the CPU. If the CPU load value is lower than the set value in S402, an interrupt is awaited by polling.
If the CPU load value is equal to or larger than the set value in S402, the polling is not performed, and the process returns to the conventional state.

According to the interrupt processing of the operating system according to the flow of FIG. 9, it is determined whether or not to perform polling for waiting for an interrupt on the basis of the load state of the CPU. This can prevent a problem that would cause the system to have a higher load.

Embodiment 3 The OS does not always perform processing. On the other hand, during a certain period, there is a case where continuous processing for a specific device is completely performed. A case will be described in which such continuous processing is performed at a high speed, and when the OS is in an empty state where there is no interrupt from another device, a specific device is polled to perform the high-speed processing. FIG. 10 is a configuration diagram of an interrupt processing portion of the operating system according to the present embodiment. As a new element compared to the configuration in each of the previous figures, 5
Reference numeral 11 denotes an operating system scheduler for controlling the operation order of the threads. Reference numeral 512 denotes a list in which executable threads referred to by the scheduler 511 are registered, and a ready queue of the operating system. Reference numeral 513 denotes an idle thread that operates when there is no executable processing in the system.
In the present embodiment, polling for interruption is performed for a specific I / O device designated by the idle thread 513. The idle thread 513 has an address of the status register 121 of the I / O device to be polled by the idle thread and an I / O processing routine 514 to be performed when an interrupt is detected.

FIG. 1 shows the operation of the configuration according to the present embodiment.
This will be described with reference to FIG. In this embodiment, the operation to the driver is performed by the scheduler 511 and the idle thread 51.
3 is realized by two components. Unlike the previous embodiments, in the fifth embodiment, the I / O driver itself does not perform any special operation. FIG. 11 shows the operation of the scheduler. The scheduler is invoked when an event that requires scheduling, such as an interrupt or semaphore post, occurs. First, in step S501, the scheduler saves and saves the context of the currently executing process. Next, in step S502, an executable process is selected with reference to the ready queue 512. In step S503, the context of the process to be executed next is returned, and the process is executed. S501 to S50
Up to 3 is the operation of the conventional scheduler. In this embodiment, when there is no new process to be executed in S502, the process proceeds to S504. The interrupt from the I / O device specified in S504 is prohibited. Then, the idle thread 513 is executed in S505. When the next scheduling event returns from the idle thread,
In step S506, the interrupt inhibition of the corresponding I / O device is released.
Returning to step S501, the scheduling process for the next thread to be executed is started.

FIG. 12 shows the operation of the idle thread 513. Conventionally, an idle thread is an empty loop that does not perform any processing.
Poll the status register of the / O device. That is, the parts of S511 and S512 are new. S511
The polling of the status register of the I / O device specified by (1) is performed to check whether an interrupt has arrived from the I / O device. The idle thread continues S511 until the next scheduling event occurs. If a scheduling event occurs during polling, the process returns to the scheduler and executes S506. When the arrival of the interrupt is detected by the polling in S511, the idle thread executes the corresponding I / O processing routine 514 to execute the necessary I / O processing.
/ O processing is performed. As a result, the I / O processing is performed in the context of the idle thread.

According to the interrupt processing of the operating system according to this embodiment, the idle thread executed when the system enters an idle state where there is no processing to be executed polls the status register of the specified I / O device. In addition, when an interrupt is detected, I / O processing is performed in the context of an idle thread.
By effectively utilizing the idle state of the system, it is possible to reduce the occurrence of delay at the time of interruption. Further, there is no need to change the processing of each I / O driver.

There may be a plurality of device controllers that perform a specific polling. FIG. 13 shows such multiple I
FIG. 3 is a diagram illustrating a configuration for polling an / O device. In the configuration shown in the figure, in addition to the configuration shown in FIG. 10, a polling process list 611 is provided in an idle thread.
The polling processing list 611 indicates the I to be polled.
Each entry corresponds to an I / O device in a table including a polling register having an address of a status register of the / O device and an address of an I / O processing routine to be executed correspondingly. The idle thread performs polling with reference to the polling processing list 611. The configuration of FIG. 13 is different from that of FIG. 10 in that the I / O processing routine 514 to be executed when an interrupt is detected is not provided in the idle thread 513b, and each I / O processing routine 514 is provided.
The I / O processing routine 114 of the driver is called.

The operation of the configuration shown in FIG. 13 will be described with reference to FIGS. FIG. 14 shows the operation of the scheduler 511b. The operations in S501, S502, and S503 are the same as those in FIG. If there is no process to be executed in S502, the process proceeds to S601. In step S601, the polling process list is referenced, and interrupts from all registered I / O devices are prohibited. Then, the idle thread 513 is executed in S602. When returning from the idle thread due to the next scheduling event, S60
In step 3, the interrupt prohibition of all the I / O devices for which the interrupt is prohibited in step S601 is released, and the process returns to step S501 to start the scheduling process for the next thread to be executed.

FIG. 15 shows the operation of the idle thread 513b. The idle thread 513b refers to the polling processing list 611 and performs polling on the status registers of all registered I / O devices. S611
To get an entry in the polling list. Next, S61
Poll the status register of the I / O device set in the polling register of the entry obtained in step 2,
Check whether an interrupt has arrived from the corresponding I / O device. If the interrupt has not arrived, the pointer is advanced to the next entry in the polling processing list in S613, and S61 is executed.
Return to 1 to obtain an entry corresponding to the next I / O device. If the arrival of the interrupt is detected in S612, the process proceeds to S61.
In step 4, the idle thread calls the I / O processing routine 114 registered in the polling processing list, and
Perform processing. If the last entry of the polling processing list has been reached in S611, the pointer is returned to the first entry in S615, and the polling is continued. Polling continues until the next scheduling event occurs. If a scheduling event occurs during polling, the process returns to the scheduler and executes S603.

Embodiment 4 FIG. As described above, polling is effective in reducing the processing time in the case of a continuous interrupt from a specific device. Here, a case will be described in which means for registering and canceling polling are provided, and only appropriate I / O devices are polled at all times. FIG. 16 is a configuration diagram of an interrupt processing portion of the operating system in the embodiment of the present invention. In the present embodiment, in addition to the above components, the polling process list 611 is added to the application 713 operating on the operating system.
Has a registration I / F 711 for registering a newly polled I / O device and a deletion I / F 712 for deleting a registered I / O device. The processing called from these I / Fs operates the entry of the polling processing list.

FIG. 1 shows the operation of the configuration according to the present embodiment.
7 and FIG. The scheduler 511b and the idle thread 513b perform the same operation as in the third embodiment. In addition, the registration I /
The entry registration process called from F performs the operation of FIG. In the entry registration process, the address of the polling status register of the I / O device to be registered and the address of the I / O processing routine to be executed when an interrupt is received are received as arguments. First, an entry is obtained by referring to the polling process list 611 in S701. Next, in S702, it is confirmed whether the I / O device is not registered in the entry and is free. If the entry has already been used, the pointer is advanced to the next entry in the polling processing list in S703, and the process returns to S701. If an empty entry is found in S702, the process moves to S705, and the address of the status register of the I / O device passed by the argument is stored in the polling register column of the entry.
The address of the processing routine is registered in the I / O processing routine column of the entry. This completes the entry registration process. If the last entry in the polling process list has been reached in S701, it is determined that there is no empty entry in S704, an error is set, and the entry registration process ends.

The entry deletion processing called from the deletion I / F to the polling processing list performs the operation shown in FIG.
In the entry deletion processing, the address of the polling status register of the I / O device to be deleted and the address of the I / O processing routine to be executed when an interrupt is received are received as arguments. First, in S711, the polling processing list 6
11 and obtain an entry. Next, in S712, the polling register column and the I / O processing routine column of the entry are checked, and the status register address and I
Check whether the address of the / O processing routine is the same. If not, the pointer is advanced to the next entry in the polling process list in S713, and the process returns to S711. S7
If an entry corresponding to the I / O device passed as an argument is found in step S12, the process proceeds to step S715, and the entry is set to be empty. This completes the entry deletion process. If the last entry of the polling processing list has been reached in S711, it is determined that there is no entry corresponding to the argument specified in S714, an error is set, and the entry deletion processing ends.

According to the interrupt processing of the operating system in the present embodiment, an I / O that polls the polling processing list from an application operating on the operating system during system execution.
Since the entry of the device can be registered and deleted, the I / O device to be polled by the idle thread can be flexibly changed according to the execution status, load and configuration of the system.

It is effective to determine whether to perform polling based on past polling results. Here, a case will be described in which polling is continued / canceled based on such results. FIG. 19 is a configuration diagram of an interrupt processing portion of another operating system according to the present embodiment. In this configuration, the polling processing list 811 has an interrupt detection count column. The number of times of interrupt detection records the number of times an interrupt can be detected by polling the corresponding I / O device. That is, the number of times polling is effective is stored. Further, it has a polling effect confirmation process 812. The polling effect confirmation processing 812 refers to the number of interrupt detections in the polling processing list 811 and confirms whether the waiting of the processing by polling is effective.
It starts as a request from an application or a timer process that is executed periodically.

FIG. 2 shows the operation of the configuration according to the present embodiment.
0 and FIG. The operation of the scheduler 511b is the same as in FIG. 14 of the third embodiment. FIG. 20 shows the operation of the idle thread 513c. The polling operation for the I / O device of the idle thread is the same as that of the third embodiment. However, in the present embodiment, an interrupt is newly detected by polling and the corresponding I / O process is called.
After 614, S801 is added to count up the number of interrupt detections in the polling processing list. In this way, when an interrupt is detected by polling, the interrupt detection frequency column of the polling processing list is counted up.

The operation of the polling effect confirmation processing 812 is shown in FIG. The polling effect confirmation process is called as a request from an application or a timer process started periodically. When the polling effect confirmation processing is called, first, an entry of the polling processing list is obtained in S811. Next, referring to the interrupt detection count of the entry acquired in S812, it is determined whether or not the unit time conversion value is larger than the set value set in the system. This set value is a threshold value for determining an I / O device that does not actually detect an interrupt even when polling is performed because the interrupt frequency is low. If the interrupt detection count is greater than the set value in S812, the entry is left as it is and polling is continued. In this case, in step S813, the number of interrupt detections is reset for the next polling effect confirmation processing,
In S814, the pointer is advanced to the next entry in the polling processing list, and the process returns to S811 to perform the processing for the next entry. If the interrupt detection count is equal to or less than the set value in S812, the polling for the corresponding I / O device is stopped, and the corresponding entry is invalidated in S815. Then, the process moves to S814 and proceeds to the next entry. S81
If the last entry of the polling processing list is reached in 1, the polling effect confirmation processing is completed. Note that the setting and detection of the unit time conversion may be a ratio at which the effective execution process for polling has been performed.

According to the interrupt processing of the operating system in the present embodiment, the number of interrupt detections is confirmed by the polling effect confirmation processing, and the polling is continued by focusing on the only valid I / O devices. Can be enhanced.

[0045]

As described above, according to this method or configuration, a part of the processing from the OS to the device is performed by polling, so that the processing can be executed in a shorter time than the processing time by the context switch. There is.

Furthermore, the execution of polling is performed by priority or O
S is selected and executed depending on the load of S.
There is an effect that the operation of S and the continuous processing of the specific device can be performed in a well-balanced manner.

Alternatively, since the polling processing is performed during the idle time of the OS, there is an effect that the processing of the computer can be used effectively.

Further, since the polling is continued based on the result of the valid polling, the processing time is further increased.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an interrupt processing portion of an OS according to a first embodiment of the present invention.

FIG. 2 is a flowchart showing an operation of an OS according to the first embodiment.

FIG. 3 is a configuration diagram of an interrupt processing portion of another OS according to the first embodiment.

FIG. 4 is a flowchart showing an operation of another OS in the first embodiment.

FIG. 5 is a configuration diagram of an interrupt processing portion of an OS according to a second embodiment of the present invention.

FIG. 6 is a flowchart showing an operation of an OS according to the second embodiment.

FIG. 7 is a flowchart showing an operation of another OS according to the second embodiment.

FIG. 8 is a configuration diagram of an interrupt processing part of another OS according to the second embodiment.

FIG. 9 is a flowchart showing an operation of another OS in the second embodiment.

FIG. 10 is a configuration diagram of an interrupt processing portion of an OS according to a third embodiment of the present invention.

FIG. 11 is a flowchart showing an operation of a scheduler according to the third embodiment.

FIG. 12 is a flowchart showing an operation of an idle thread according to the third embodiment.

FIG. 13 is a configuration diagram of an interrupt processing part of another OS according to the third embodiment.

FIG. 14 is a flowchart showing an operation of another scheduler according to the third embodiment.

FIG. 15 is a flowchart showing an operation of another idle thread in the third embodiment.

FIG. 16 is a configuration diagram of an interrupt processing portion of the OS according to the fourth embodiment of the present invention.

FIG. 17 is a flowchart showing an operation of an entry registration process in the fourth embodiment.

FIG. 18 is a flowchart showing an operation of entry registration deletion according to the fourth embodiment.

FIG. 19 is a configuration diagram of an interrupt processing portion of another OS according to the fourth embodiment.

FIG. 20 is a flowchart showing an operation of an idle thread according to the fourth embodiment.

FIG. 21 is a flowchart showing an operation of a polling effect confirmation process according to the fourth embodiment.

FIG. 22 is a diagram showing a configuration of a conventional device for performing multitask interrupt processing.

[Explanation of symbols]

101 information processing device, 102 network controller, 110 operating system (OS), 1
11 Interrupt dispatch table, 112, 112
b network driver, 113 interrupt handler, 114, 114b I / O processing routine, 121
Status register, 211 context switch time information (table), 212 interrupt time interval information table, 311 communication packet, 312 priority information, 31
3 processing priority information (table), 411 CPU load information (table), 511, 511b scheduler,
512 ready queue, 513, 513b, 513c idle thread, 611 polling information list, 71
1 Polling registration I / F, 712 Polling delete I
/ F, 713 application, 811 polling process list, S104 interruption prohibition step, S105
Step of detecting the state by polling, S106 Polling count check step, S108 Interrupt release step, S201 Interrupt time information table update step, S204 Time comparison step, S302, S
304 Priority information reference step, S402 CPU load value reference step, S505 idle thread execution step, S511 polling state detection step, S512 I / O processing execution step, S601 idle thread execution step, S611 polling processing list check step, S612 Step of detecting state by polling, S705 registration step, S71
5 Step of deleting from entry, S801 Valid polling count detection step, S812 Comparison with specified value.

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B014 FA05 FA09 FA16 FB04 5B098 AA05 BA01 BB01 BB06 BB12 DD06 GA02 GA04 GA07 GD07 GD14

Claims (9)

[Claims] 1. An operating system for performing a multitask process for controlling an I / O (input / output) driver by an interrupt, comprising: completing a driver process for a device based on the interrupt request; Prohibiting, interrupting, checking the status of the device by polling, and releasing the interrupt request after performing the polling for a predetermined period of time. Polling processing Embedded operating method. 2. The operating method according to claim 1, wherein whether or not polling is possible is determined based on the actual interruption interval of the target. 3. The dedicated polling processing embedded operating method according to claim 1, wherein priority information is determined, and whether polling is permitted or not is determined based on the priority information. 4. The operating method according to claim 1, wherein the load status of the operating system is checked and polling is performed when the load status is equal to or less than a predetermined value. 5. An operating system for performing a multitask process for controlling an I / O driver by an interrupt, wherein after executing the process corresponding to the interrupt request, if there is no other interrupt request in the idle state, the specific device A dedicated polling process built-in operating method, comprising a step of polling a driver to check the status of the device and processing the device. 6. A polling processing step of registering a specific device in a plurality of lists and polling the plurality of registered devices in a predetermined order when the operating system is in an idle state. 6. The operating method according to claim 5, further comprising the step of examining the state of the program and performing processing. 7. A step of recording, for each device, a ratio or the number of times the actual processing by polling has been executed, and when the ratio or the number of executions per unit time is equal to or more than a predetermined value, continue polling thereafter. 6. The operating method according to claim 1, wherein said dedicated polling process is incorporated. 8. An operating system for performing a multitask process for controlling an I / O (input / output) driver by means of an interrupt, comprising: completing a driver process for a device based on the interrupt request; A program that checks the status of the device by polling, processes the device, performs the polling for a predetermined period, and then cancels the prohibition of the interrupt request to the driver. Polling processing Embedded operating system. 9. An operating system for performing a multitasking process for controlling an I / O driver by an interrupt, wherein after executing the process corresponding to the interrupt request, the idle operation which preferentially operates when there is no other interrupt request in an idle state. A dedicated polling processing embedded operating system comprising a thread, wherein the idle thread checks the status of the device by polling a driver of the specific device and performs processing.