JPS61183768A - Controlling method of non-response confirming interface - Google Patents

Abstract

PURPOSE:To prevent an insignificant processing from being executed repeatedly by energizing continuously a response by a response side device, detecting a fact that a response line has been energized, by a request side device, and suppressing the generation of a data transfer request. CONSTITUTION:When a transfer indicating signal S19 is energized, an input signal S20 of OR gates 14, 17 is de-energized. When a request trigger signal S11 is generated, an FF circuit 11 is energized, an FF circuit 13 is energized, an inbound tag S14 is energized, and an FF circuit 11 is returned to an initial state. In a channel device, when it is detected that the inbound tag S14 has been energized, an FF circuit 51 is set, and an outbound tag S52 is energized. In order to reserve a request in the channel device, the outbound tag S52 is de-energized by resetting the FF circuit 51 at the time point whent the reservation has become unnecessary, in case when it cannot meet the inbound tag S14 which is sent in the next time.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to an interface for data transfer of an information processing device. In particular, the present invention relates to a method of controlling a non-response confirmation interface between a channel device and a control device.

〔overview〕

In the non-response confirmation interface of an information processing device, the present invention provides a method for responding to a data transfer request from a requesting device when the responding device receives a data transfer request from the requesting device but cannot respond to the next data transfer request. When the line is continuously energized and the requesting device detects that the response line is continuously energized, it controls the next data transfer request to be suppressed, thereby eliminating the situation in which data transfer cannot be performed. This is to prevent unnecessary transfer requests from occurring at certain times.

[Conventional technology]

FIG. 4 is a block diagram of the channel interface, and is an overall diagram for explaining the signal system of the input/output interface. FIG. 4 shows an interface provided between the channel device 50 and the control device 10,
Between the channel device 50 and the control device 10, data S is sent from the channel device 50 to the control device 10. bus out jl'so is the data bus to which the data S from the control device 10 to the channel device 50 is sent. Bus in 11° and bus out l, which are the data buses to which are sent. and bus in l,. The data S, which is being sent to. , Sl. Outbound tag vAist is sent from the channel device 50 to the control device 1 as a tag that refers to the outbound tag SS2, and inbound tag line 1 is sent from the control device 10 to the channel device 50 by the inbound tag SL4.
14 are connected.

FIG. 5 is a time chart of the response confirmation interface. In FIG. 5, the control device 10 shown in FIG. 4 energizes the inbound tag 314, and the channel device 50 receives data S,. When receiving (in the case of reading) or sending out (in the case of writing), the outbound tags S and Z are energized, the control device 10 deactivates the inbound tag S14, and the channel device 50 deactivates the outbound tag SSZ. and the data bus line 11°, l. Data S1゜, S,. is sent or received. Therefore, if the channel device 50 cannot respond to a request from the control device 10 (activation of the inbound tag S14), the activation state of the inbound tag SI4 will only be extended, and the outbound tag S, 2 of the channel device 50 will be activated. The transfer is restarted by activation, and the channel device 50 can suspend the transfer.

However, in order to improve the data transfer speed, a non-response confirmation interface is used in which the next request is made without confirming the response to the data transfer request. FIG. 6 is a time chart of a conventional non-response confirmation interface, in which the control device 10 shown in FIG. Activation of outbound tag SSZ)
Inbound tag SI4 to make the next request without waiting for
perform the annihilation of Even if the channel device 50 tries to suspend some of the requests, the requests continue to be made, so it is theoretically impossible for the channel device 50 to suspend the requests.

[Prior art]

[Problems to be Solved by the Invention] However, in such a non-response confirmation interface, data transfer is executed without confirming the response of the request as described above, so if the response is not confirmed due to the circumstances of the responding device. If the response is delayed, many requests will be put on hold, and a large amount of hardware will be required to deal with this hold-up, so there is a drawback that it is virtually impossible to delay the response due to circumstances on the response side.

The present invention solves the above-mentioned drawbacks, and is capable of suppressing the generation of unnecessary transfer requests when the responding device cannot perform data transfer, and is capable of preventing non-response with less increase in hardware amount. The purpose is to provide a method for controlling the confirmation interface.

[Means for solving problems]

The present invention is connected between a requesting device that makes a data transfer request and a responding device that responds to the data transfer request, and the responding device energizes a response line and deactivates it after a predetermined time to respond. control of a non-response confirmation interface that energizes the request line from the requesting device, de-energizes it after a predetermined period of time, issues a data transfer request, and issues the next data transfer request even if the response line is not energized; In the method, the responding device suppresses deactivation of the response line after activation when data transfer is impossible, and the requesting device detects that the response line is continuously activated. The feature is that the data transfer request is detected and the occurrence of the data transfer request is suppressed.

[Effect]

According to the present invention, in response to a data transfer request from a requesting device requesting data transfer, a responding device transmitting data in response to the data transfer request deactivates the response line after activating it. When the requesting device detects that the response line is continuously energized, it suppresses the generation of a transfer request. It is also possible to prevent the generation of meaningless data transfer requests.

〔Example〕

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

FIG. 1 is a block diagram of a control device for a non-response confirmation interface according to an embodiment of the present invention. In FIG. 1, the request trigger signal Sll is connected to the set signal S of the flip-flop 11. In FIG.

Here, the feature of the present invention is the transfer request suppression portion surrounded by a dashed line. That is, flip-flop 1
An output signal Sl□ from the output Q of 1 is connected to one input of an AND gate 12. Output signal S of AND gate 12
I3 is connected to the set input S of the flip-flop 13. Output signal SI4 from output Q of flip-flop 13
is sent to a channel device SO (not shown). Also, the output signal S1 of the flip-flop 13. is connected to one input of the OR gate 14 and the input of the one shot 15. The output signal SI5 of the OR gate 14 is the flip-flop 11
The output signal SI□ of the flip-flop 11 is inactivated. The output signal SI6 of the one shot 15 is connected to the input of the one shot 16 after a predetermined time.

Here, it is assumed that one-shot inputs with a circle mark added are triggered at the fall of the input signal, and those without a circle mark are triggered at the rise of the input signal. Output signal Sl of one shot 16? is or gate 17
is connected to one input of the OR gate 17, and the output signal S of the OR gate 17 is
18 is connected to the reset input R of the flip-flop 13. The output signal SI4 of flip-flop 13 is deactivated.

On the other hand, a transfer instruction signal SI9 from outside the figure is connected to the input of an inverter 18, and an output signal S2° of the inverter 18 is connected to the other input of the OR gate 14.17.

When the transfer instruction signal SI9 is generated, the output signal S2° is deactivated, the reset of the flip-flop E1.13 is deactivated, and the setting becomes possible.

Further, an outbound tag S52 from a channel device 50 (not shown) is connected to the input of the data input D1 one-shot 20 of the flip-flop 19 and the input of the inverter 22. The output signal SI9 of the one shot 20 is connected to the input of the one shot 21 after a predetermined time, and the output signal SI9 of the one shot 2
1 output signal S2° is connected to the clock input CP of the flip-flop 19. Output signal S2 of inverter 22
z is connected to the reset input R of the flip-flop 19. If the outbound tag SSZ remains activated, the -output signal 52ff of the flip-flop 19 remains deactivated, and the inbound tag 314 is not activated.

When the outbound tag SSZ is deactivated, the output signal SZ3 of the flip-flop 19 is activated, and the inbound tag SI4 is activated.

FIG. 2 is a block diagram of a channel device of a non-response confirmation interface according to an embodiment of the present invention. In Figure 2,
A response trigger signal SSI is connected to the set input S of the flip-flop 51. An output signal SSt from the output Q of the flip-flop 51 is connected to a control device 10 (not shown).

Further, the output signal S52 of the flip-flop 51 is connected to the input of the one-shot 52. The output signal SS3 of the one shot 52 is connected to the input of the one shot 53 after a predetermined time.

Here, the feature of the present invention is the response line degeneration suppressing portion surrounded by a dashed line. That is, one shot 53
The output signal, 4, is connected to one input of AND gate 54. The response permission signal SSS is connected to the other input of the AND gate 54, and the output signal SS& of the AND gate 54 is connected to one input of the OR gate 55.
The output signal 5S11 of the flip-flop 51 is connected to the reset input R of the flip-flop 51, and the output signal SS2 of the flip-flop 51 is inactivated. Further, the response restart signal SSt is connected to the other input of the OR gate 55, and deactivates the output signal S52.

The operation of such a non-response confirmation interface will be explained. FIG. 3 is a time chart of non-response confirmation according to the present invention. In FIG. 3, the symbols on the left side of each waveform indicate the signal waveform of each part in FIGS. 1 and 2. First, the initial state is the transfer instruction signal SI9 and the request trigger signal Sl shown in FIG.
outbound tag S5□, response trigger signal Ss+ shown in FIG. 2, response restart signal SS4, response permission signal S%,
and outbound tags 552 are all inactive. When the transfer instruction signal S19 is activated, the OR gate 14.
The output signal S2° input to 17 becomes inactive. When the request trigger S11 occurs, the flip-flop 11 is activated and the flip-flop 19 is in the reset state, so the output signal SZZ is activated, and therefore the AND gate 1 is activated.
2 is activated, the output signal 311 activates the flip-flop 13, and the inbound tag S14 is activated. When the inbound tag Sla is energized, the flip-flop 11 is reset and the flip-flop 11 is returned to its initial state. When the inbound tag SI4 is activated, the washer H6 operates after the time determined by the one shot 15, so the output signal SI7 resets the flip-flop 13 and deactivates the inbound tag Sta. Subsequently, the request trigger signal S
11, an inbound tag 314 is generated for a certain period of time similarly to the above operation, and a non-response confirmation interface is formed. On the other hand, when the channel device 50 detects activation of the land tag S14, the response trigger signal S
s+ is generated, the outbound tag Sst is energized by setting and turning the flip-flop tube 51, and is deactivated after a certain period of time in the same manner as the deactivation of the inbound tag SI4. However, in order to perform the request suspension in the channel device 50, which is a feature of the present invention, the deactivation of the inbound tag SSM is delayed until the next inbound tag SSM is sent.
If it is not possible to respond to ea, the AND gate SSS is not executed by deactivating the response permission signal SSS, and when there is no need to hold it, the reset of the flip-flop 51 is activated by activating the response restart signal SSt. The outbound tag SS2 is energized. In the control device 10, the one shot 52 is activated by the energization of the outbound tag SSZ.
Since the one shot 53 operates after a certain period of time, when the outbound tag SSZ continues for a certain period of time determined by the one shot 52 or more, the flip-flop 19 is set and the output signal S23 is deactivated. This means that by suppressing and gate 12, the next inbound tag 5ea
O bias is suppressed. Outbound tag S5Z
energization resets the flip-flop 19, stops inhibiting the AND gate 12, and restarts the request. Note that it is possible that the next inbound tag SI4 may be received while the outbound tag S5□ is being suppressed from being deactivated in the channel device 50, but in this case, a response to the received inbound tag 514 will be made after restarting. This must be taken into consideration as it may inevitably occur in non-response confirmations.

[Effect of invention□]

As explained above, the present invention continuously activates the response in the responding device, detects that the response line is activated in the requesting device, and suppresses the occurrence of data transfer requests. This eliminates repeated execution of meaningless processes, reduces the burden on the control device, and has the excellent effect of making the hardware and software of the device more economical.

[Brief explanation of drawings]

FIG. 1 is a block diagram of a control device for a non-response confirmation interface according to an embodiment of the present invention. FIG. 2 is a block diagram of a non-response confirmation interface no-channel device according to an embodiment of the present invention. FIG. 3 is a time chart of the non-response confirmation interface of the present invention. FIG. 4 is a block diagram of a channel interface. FIG. 5 is a time chart of the response confirmation interface. FIG. 6 is a time chart of a conventional non-response confirmation interface. 10...control device, 50...channel device, 11.
13.19.51...Flip-flop, 12.54
...and gate, 14.17.55...or gate, 15.16.20.21.52.53...one shot, 18.22...inverter, 1.0...bus in, 114 ...Inbound tag line, j! s.・
・・Bus out, S5□・・Outbound tag line,
S. ,S. ...Data, 3+1...Request trigger signal, S14...Inbound tag, Si2...Transfer instruction signal, SSI'...Response trigger signal, SSZ...
・Outbound tag, SSS...Response permission signal, S
S? ...Response restart signal, SIX~S13.3 l5-
3 + s, S20~SZ3, SS3, SS4, S s
I S ss...Output signal.

Claims (1)

[Claims] (1) Connected between a requesting device that makes a data transfer request and a responding device that responds to this data transfer request, the responding device energizes a response line and de-energizes it after a predetermined period of time to respond. control of a non-response confirmation interface that energizes the request line from the requesting device, de-energizes it after a predetermined period of time, issues a data transfer request, and issues the next data transfer request even if the response line is not energized; In the method, the responding device suppresses deactivation of the response line after activation when data transfer is impossible, and the requesting device detects that the response line is continuously activated. A control method for a non-response confirmation interface, characterized in that the generation of a data transfer request is suppressed by