Interrupting node for providing interrupt requests to a pended bus

• US 5,428,794 A
• Filed: 03/03/1994
• Issued: 06/27/1995
• Est. Priority Date: 05/01/1987
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Digital Equipment Corporation (HP Inc.)
• Inventors: Williams, Douglas D.
• Primary Examiner(s): Lall, Parshoiam S.
• Assistant Examiner(s): MOHAMED, AYNI Y
• Application Number:
  US08/206,109
• Time in Patent Office: 481 Days
• Field of Search: 395/325, 395/725
• US Class Current: 710/268
• CPC Class Codes: G06F 13/24 using interrupt G06F13/32 takes precedence
• CPC Class Codes: G06F 15/17 using an input/output type connection, e.g. channel, I/O port

Abstract

An interrupting node for providing interrupt requests to a pended bus. The interrupting node provides to the pended bus an interrupt request message including ID data for identifying the interrupting node as the source of an interrupt request. An interrupt servicing node provides interrupt acknowledge messages including destination data specifying a particular interrupting node at times when the interrupt servicing node is ready to service an interrupt request message. The interrupting node detects whether an interrupt acknowledge message on the bus includes destination data specifying that interrupting node, and provides an interrupt vector message to the bus in response.

Claims

1. An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising:

means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request; and

means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node.

2. An interrupting node in accordance with claim 1, in which the interrupting node is an input/output device.

3. An interrupting node in accordance with claim 1 in which the interrupt request message providing means includes means for providing, the interrupt request message with destination data for specifying the interrupt servicing node.

4. An interrupting node in accordance with claim 3 in which the interrupt request message providing means includes means for providing destination data for specifying a plurality of interrupt servicing nodes.

5. An interrupting node in accordance with claim 1 in which the interrupt request message providing means includes means for providing the interrupt request message with priority level data specifying a priority level of the interrupt request message.

6. An interrupting node in accordance with claim 5 in which the interrupt acknowledge message detecting means includes means for extracting from the interrupt acknowledge message priority level data specifying a priority level of the interrupt request being serviced.

7. An interrupting node in accordance with claim 6 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.

23. An interrupting node in accordance with claim 5 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.

8. An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising:

means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request;

means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node; and

means for providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message.

9. An interrupting node in accordance with claim 8 in which the interrupt vector providing means includes means for providing, in response to the detection of an interrupt acknowledge message including source data identifying the interrupt servicing node, the interrupt vector message with the source data identifying the interrupt servicing node.

10. An interrupting node in accordance with claim 8 in which the interrupting node is an input/output device.

11. An interrupting node in accordance with claim 8 in which the interrupt request message providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.

12. An interrupting node in accordance with claim 11 in which the interrupt request message providing means includes means for providing destination data for specifying a plurality of interrupt servicing nodes.

13. An interrupting node in accordance with claim 8 in which the interrupt request message providing means includes means for providing the interrupt request message with priority level data specifying a priority level of the interrupt request message.

14. An interrupting node in accordance with claim 9 in which the interrupt request message providing means includes means for providing the interrupt request message with priority level data specifying a priority level of the interrupt request message.

15. An interrupting node in accordance with claim 13 in which the interrupt acknowledge message detecting means includes means for extracting from the interrupt acknowledge message priority level data specifying a priority level of the interrupt request being serviced.

16. An interrupting node in accordance with claim 15 in which the interrupt vector message providing means includes means for selecting one of a plurality of interrupt vector messages in accordance with the priority level data extracted from the interrupt acknowledge message.

17. An interrupting node in accordance with claim 9 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.

18. An interrupting node in accordance with claim 13 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.

19. An interrupting node in accordance with claim 14 in which the interrupt request providing means includes means for providing the interrupt request message with destination data for specifying the interrupt servicing node.

20. A method for an interrupting node having a unique ID to provide interrupt requests to a pended bus for transferring messages between the interrupting node and an interrupt servicing node, the method comprising the steps of:

providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request;

monitoring interrupt acknowledge messages on the bus, and detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node; and

providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message.

21. An interrupting node having a unique ID for providing interrupt requests to an interrupt servicing node, and coupled to a pended bus for transferring messages between the interrupting node and the interrupt servicing node, the interrupting node comprising:

means for providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request, destination data for specifying the interrupt servicing node, and priority level data specifying a priority level of the interrupt request message;

means for monitoring interrupt acknowledge messages on the bus, and for detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node, by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node, and source data identifying the interrupt servicing node; and

means for providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message including the source data identifying the interrupt servicing node.

22. A method for an interrupting node having a unique ID to provide interrupt requests to a pended bus for transferring messages between the interrupting node and an interrupt servicing node, the method comprising the steps of:

providing to the bus an interrupt request message including ID data corresponding to the unique ID of the interrupting node for identifying the interrupting node as the source of the interrupt request, destination data for specifying the interrupt servicing node, and priority level data specifying a priority level of the interrupt request message;

monitoring interrupt acknowledge messages on the bus;

detecting as a response to one of the interrupt requests of the interrupting node an interrupt acknowledge message including destination data specifying the interrupting node, by comparing the destination data in the interrupt acknowledge message with the unique ID of the interrupting node, and source data identifying the interrupt servicing node; and

providing to the bus, in response to the detection of the interrupt acknowledge message including destination data specifying the unique ID of the interrupting node, an interrupt vector message including the source data identifying the interrupt servicing node.