Jerry J Chu

US Patent:

8463971, Jun 11, 2013

Filed:

Aug 1, 2006

Appl. No.:

11/497884

Inventors:

Ethan Solomita - San Francisco CA, US
Sunay Tripathi - Palo Alto CA, US
Jerry Hsiao-Keng Chu - Palo Alto CA, US

Assignee:

Oracle America Inc. - Redwood Shores CA

International Classification:

G06F 13/24
G06F 9/46

US Classification:

710267, 710260, 718105

Abstract:

A method and apparatus for distributing multiple interrupts among multiple processors is disclosed. According to one embodiment, an interrupt daemon monitors the interrupt load among the processors that results from an initial mapping of the interrupts to the processors. The interrupt daemon determines whether there is a sufficient imbalance of the interrupts among the processors. If so, the interrupt daemon triggers a reassignment routine that generates a new mapping of the interrupts among the processors, and if not, the interrupt daemon goes to sleep for a specified time period. If the new mapping produces a sufficient improvement in the distribution of interrupts among the processors, based on the same criteria used to detect the imbalance, the new mapping is used by the central hub for subsequent distribution of interrupts to the processors. However, if the new mapping does not provide a sufficient improvement, the original mapping continues to be used.

US Patent:

20030037282, Feb 20, 2003

Filed:

Aug 15, 2001

Appl. No.:

09/931083

Inventors:

Jerry Berg - Hayward CA, US
Jerry Chu - Fremont CA, US
Chin-Te Chen - San Jose CA, US

International Classification:

H04L001/22

US Classification:

714/011000

Abstract:

A method and system for performing software versioning between multiple controllers in a fault tolerant system. The fault tolerant system includes a storage system and multiple redundant controllers that provide access to the storage system. The storage system has stored thereon a preferred version of software to be used by the controllers. This software may be updated. The controllers each contain non-volatile memory. On boot, a controller compares the software version in its non-volatile memory to the preferred version in the storage system. If they are different (e.g., the software on the storage system was updated or the controller was updated with a non-preferred software version), then the controller copies the storage system version into its non-volatile memory and then re-boots. One controller is typically left operational while the other is re-booted for redundancy. Computer controlled versioning allows (1) lockstep software updates between the controllers based on a software version that may be associated with the storage system as a whole and (2) provides a central store from which the controllers may obtain the preferred software version. A special flash update mechanism is also described with respect to an implementation that uses flash memory as the non-volatile memory.