← Back to Patent Explorer
EP0257348A2 Expired / Lapsed EP ⏱️ 0.0 years remaining

Multiprocessor interrupt rerouting mechanism

Assignee: Bull HN Information Systems Inc
•
Filing: 1987-07-31
•
Granted: —
•
Expires: 2007-07-31
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A multiprocessor interrupt rerouting mechanism and method is disclosed for rerouting messages intended for a first processor to a second processor. In a fault tolerant computer system having several processors or LANs under the control of a single controller, when the controller completes a communication task requested by one of the processors, it will send an interrupt request to the requesting processor which then notifies the application process for which the communication task was performed, information regarding the status of the communication task. If for any reason the requesting processor being interrupted is inoperative or too busy to handle the interrupt request, the application process is then notified as to the status of the communication task by rerouting the interrupt request from the controller so that another processor can handle it.

Inventors

  • 👤 Kin C. Yu
  • 👤 Allen C. Hirtle

Bibliographic Details

Application Number —
Jurisdiction EP
Data Source google_patents
Last Synchronized 2026-10-27 19:00
CPC Classifications
H; H04; H04L; H04L5/00; G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/48; G06F9/4806; G06F9/4812; H04L12/00; H04L12/28; H04L12/46; H04L12/4604; H04L12/462; H04L12/4625; H04L69/00; G06F11/00; G06F11/07; G06F11/16; G06F11/20; H04L69/30; H04L69/32; H04L69/321

Claims Analysis

Total Claims: 13
Claim 1
Independent Claim 336 words
In a local area network (LAN) system having a computer system comprised of at least one bus, a plurality of CPUs coupled to said bus for executing application processes, each CPU having a memory associated to it, said LAN also having at least one controller coupled to said bus and including at least one controller memory, said LAN system further including resources coupled to said bus, and additional LANs coupled to said at least one controller, and means for creating LAN control blocks (LCBs) within any of said memories, said LCBs for transferring information to/from said memories, resources, controller and LANs, said controller capable of effecting the interruption of any of said CPUs, a multiprocessor interrupt rerouting mechanism for rerouting messages intended for any one of said plurality of said processors to a different one of said plurality of said processors: (a) first means for requesting communication service from said controller on behalf of a first process executing on any one of said plurality of CPUs wherein said controller is interrupted by said any one of said plurality of said CPUs; (b) second means in said controller for creating queues of LCBs for said any one of said processors interrupting said controller, when said controller cannot immediately service a request for communication service; (c) third means in said controller for interrupting said any one of said plurality of said CPUs to provide a status message to said first process executing on said any one of said plurality of said CPUs; and, (d) fourth means in said controller for rerouting said status message to said first process by interrupting a different one of said plurality of said CPUs to provide the status message to said first process, whereby when said any one of said plurality of said CPUs is unable to receive an interrupt from said controller and notify said first process of the status of its request, said first process is notified via an alternate route through a different one of said plurality of said CPUs.
Claim 2
Dependent Claim 336 words
In a local area network (LAN) system having a computer system comprised of at least one bus, a plurality of CPUs coupled to said bus for executing application processes, each CPU having a memory associated to it, said LAN also having at least one controller coupled to said bus and including at least one controller memory, said LAN system further including resources coupled to said bus, and additional LANs coupled to said at least one controller, and means for creating LAN control blocks (LCBs) within any of said memories, said LCBs for transferring information to/from said memories, resources, controller and LANs, said controller capable of effecting the interruption of any of said CPUs, a multiprocessor interrupt rerouting mechanism for rerouting messages intended for any one of said plurality of said processors to a different one of said plurality of said processors: (a) first means for requesting communication service from said controller on behalf of a first process executing on any one of said plurality of CPUs wherein said controller is interrupted by said any one of said plurality of said CPUs; (b) second means in said controller for creating queues of LCBs for said any one of said processors interrupting said controller, when said controller cannot immediately service a request for communication service; (c) third means in said controller for interrupting said any one of said plurality of said CPUs to provide a status message to said first process executing on said any one of said plurality of said CPUs; and, (d) fourth means in said controller for rerouting said status message to said first process by interrupting a different one of said plurality of said CPUs to provide the status message to said first process, whereby when said any one of said plurality of said CPUs is unable to receive an interrupt from said controller and notify said first process of the status of its request, said first process is notified via an alternate route through a different one of said plurality of said CPUs.
Claim 3
Dependent Claim 37 words
The LAN system as recited in Claim 1 including fifth means for creating a rerouting table in the controller memory for each queue created by said controller for each CPU interrupting said controller to request service therefrom.
Claim 4
Dependent Claim 67 words
The LAN system as recited in Claim 2 wherein said rerouting table is characterized in that it is accessed by said controller by a queue number and the contents of the table comprise a CPU address which is utilized to interrupt said any of said plurality of said CPUs in order to provide status information to application processes executing on said any of said plurality of CPUs.
Claim 5
Dependent Claim 47 words
The LAN system as recited in Claim 3 including means in said controller for determining when any of said CPUs does not accept an interrupt request from said controller, because said any of said plurality of CPUs being sent an interrupt request is either inoperative or overloaded.
Claim 6
Dependent Claim 61 words
The LAN system as recited in Claim 4 including seventh means coupled to said sixth means for substituting a different CPU address for the address of said any of said plurality of CPUs in the queue of said any of said plurality of CPUs maintained by said controller, when said any of said plurality of said CPUs becomes inoperative or overloaded.
Claim 7
Dependent Claim 26 words
The LAN system as recited in Claim 4 including eighth means coupled to said seventh means for storing said different CPU address in a predetermined format.
Claim 8
Dependent Claim 58 words
The LAN system as recited in Claim 6 wherein said eighth means is characterized in that it includes a CPU number which will be substituted for the address of said any of said plurality of CPUs, and a queue number of a queue maintained by said controller of pending interrupts for said any of said plurality of CPUs.
Claim 9
Dependent Claim 303 words
In a computer system comprising at least one bus, at least a first CPU and a second CPU coupled to said bus for executing first and second processes respectively thereon, each of said first and second CPUs having first and second memories respectively coupled to said bus, said computer system also including resources coupled to said bus, and further including a controller coupled to said bus, said controller including a controller memory and being capable of interrupting said first and second CPUs, a multiprocessor interrupt rerouting mechanism for rerouting by said controller first messages intended to be delivered by said first CPU to said first process so that the said first messages are delivered to said first process by said second CPU comprising: (a) first means for requesting service by said first process from said controller by interrupting said controller by said first CPU; (b) second means in said controller for requesting service by said second process from said controller by interrupting said controller by said second CPU; (c) third means in said controller for creating first and second queues of interrupt messages for said first and second CPUs, when said controller cannot immediately service said first or second processes; (d) fourth means in said controller for interrupting said first CPU to provide a first status message to said first process executing on said first CPU; and, (e) fifth means in said controller for rerouting said first status message to said first process by interrupting said second CPU to deliver said first status message to said first process, whereby when said first CPU is disabled or overloaded and cannot receive a first status message to relay to said first process, said second CPU is interrupted by said controller and said first status message is delivered to said first process by said second CPU.
Claim 10
Dependent Claim 303 words
In a computer system comprising at least one bus, at least a first CPU and a second CPU coupled to said bus for executing first and second processes respectively thereon, each of said first and second CPUs having first and second memories respectively coupled to said bus, said computer system also including resources coupled to said bus, and further including a controller coupled to said bus, said controller including a controller memory and being capable of interrupting said first and second CPUs, a multiprocessor interrupt rerouting mechanism for rerouting by said controller first messages intended to be delivered by said first CPU to said first process so that the said first messages are delivered to said first process by said second CPU comprising: (a) first means for requesting service by said first process from said controller by interrupting said controller by said first CPU; (b) second means in said controller for requesting service by said second process from said controller by interrupting said controller by said second CPU; (c) third means in said controller for creating first and second queues of interrupt messages for said first and second CPUs, when said controller cannot immediately service said first or second processes; (d) fourth means in said controller for interrupting said first CPU to provide a first status message to said first process executing on said first CPU; and, (e) fifth means in said controller for rerouting said first status message to said first process by interrupting said second CPU to deliver said first status message to said first process, whereby when said first CPU is disabled or overloaded and cannot receive a first status message to relay to said first process, said second CPU is interrupted by said controller and said first status message is delivered to said first process by said second CPU.
Claim 11
Dependent Claim 32 words
The computer system as recited in Claim 8 including sixth means in said controller for creating a rerouting table in the controller memory for said first and second queues of interrupt messages.
Claim 12
Dependent Claim 272 words
In a computer system comprising at least one bus, at least a first CPU and a second CPU coupled to said bus for executing first and second processes respectively thereon, each of said first and second CPUs having first and second memories respectively coupled to said bus, said computer system also including resources coupled to said bus, and further including a controller coupled to said bus, said controller including a controller memory and being capable of interrupting said first and second CPUs, the method of rerouting first messages intended to be delivered by said first CPU to said first process so that said first messages are delivered to said first process by said second CPU comprising: (a) requesting service by said first process from said controller by interrupting said controller by said first CPU; (b) requesting service by said second process from said controller by interrupting said controller by said second CPU; (c) creating first and second queues in said controller of interrupt messages for said first and second CPUs, when said controller cannot immediately service said first or second processes; (d) interrupting said first CPU to provide a first status message to said first process executing on said first CPU; and, (e) rerouting said first status message to said first process by interrupting said second CPU to deliver said first status message to said first process, whereby when said first CPU is disabled or overloaded and cannot receive a first status message to relay to said first process, said second CPU is interrupted by said controller and said first status message is delivered to said first process by said second CPU.
Claim 13
Dependent Claim 272 words
In a computer system comprising at least one bus, at least a first CPU and a second CPU coupled to said bus for executing first and second processes respectively thereon, each of said first and second CPUs having first and second memories respectively coupled to said bus, said computer system also including resources coupled to said bus, and further including a controller coupled to said bus, said controller including a controller memory and being capable of interrupting said first and second CPUs, the method of rerouting first messages intended to be delivered by said first CPU to said first process so that said first messages are delivered to said first process by said second CPU comprising: (a) requesting service by said first process from said controller by interrupting said controller by said first CPU; (b) requesting service by said second process from said controller by interrupting said controller by said second CPU; (c) creating first and second queues in said controller of interrupt messages for said first and second CPUs, when said controller cannot immediately service said first or second processes; (d) interrupting said first CPU to provide a first status message to said first process executing on said first CPU; and, (e) rerouting said first status message to said first process by interrupting said second CPU to deliver said first status message to said first process, whereby when said first CPU is disabled or overloaded and cannot receive a first status message to relay to said first process, said second CPU is interrupted by said controller and said first status message is delivered to said first process by said second CPU.

References Cited (Backward Citations)

No citation records indexed.

USPTO Annuity & Maintenance Windows

Maintenance schedule is calculated for granted US utility patents.

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag