Responding to service requests using minimal system-side context in a multiprocessor environment

• US 5,390,329 A
• Filed: 07/20/1994
• Issued: 02/14/1995
• Est. Priority Date: 06/11/1990
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: CRAY Incorporated (Hewlett-Packard Enterprise Company)
• Inventors: Gaertner, Gregory G., Wengelski, Diane M., Thompson, Keith J.
• Primary Examiner(s): Harrell, Robert B.
• Application Number:
  US08/277,776
• Time in Patent Office: 209 Days
• Field of Search: 364/DIG. 1 MS File, 364/DIG. 2 MS File, 395/200, 395/275, 395/375, 395/400, 395/425, 395/650, 395/700, 395/800
• US Class Current: 718/108
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/08 in hierarchically structured memory systems, e.g. virtual memory systems
• CPC Class Codes: G06F 12/12 Replacement control
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• CPC Class Codes: G06F 8/445 Exploiting fine grain parallelism, i.e. parallelism at instruction level run-time instruction scheduling G06F9/3836
• CPC Class Codes: G06F 8/45 Exploiting coarse grain parallelism in compilation, i.e. parallelism between groups of instructions
• CPC Class Codes: G06F 9/461 Saving or restoring of program or task context

Abstract

A method of providing fast and efficient kernel functions including those usually performed by kernel daemons and other kernel processes such as those which service interrupts. The method consists of using minimal-context processes that carry only the system-related information needed to do the work they are created to do. Compared to the full-context processes presently used to do kernel functions, minimal-context processes are created quickly and switch economically. If associated with a work queue, the minimal-context process performs a series of tasks within a single active session. If no queue is used, a minimal-context process can wake up and accomplish a single task rapidly. The method generally relates to kernel-based operating systems.

Claims

1. In a data processing and handling system having one or more processing units coupled to a multiplicity of sharable components, all operable in conjunction with both a system-side context and a user-side context, for performing data processing and handling tasks in response to service-requesting events which have priority level information associated therewith, and wherein the system has a temporary data storing means including a plurality of separately addressable data storage areas, a method for responding to occurrences of service-requesting events comprising the steps of:

designating one of the data storage areas as a zero level storage area having a higher priority level than all remaining data storage areas;

responding to an occurrence of a service-requesting event by moving service-handling program code having minimal system-side context to said zero level storage area, said minimal system-side context containing information identifying a task associated with said service-requesting event, as well as an assigned priority associated with said service-requesting event;

suspending a first process in a receiving processing unit whenever said zero level storage area is loaded;

preserving a minimal system-side context of said first suspended process which is less than an entire context of said suspended first process into said sharable system components in order that said receiving processing unit is ready to handle said minimum system-side context of said service-handling program code;

determining whether said priority level assigned to said service-requesting event is higher than a priority level assigned to said first suspended process;

saving said entire context of said first suspended process in order to commence processing of tasks of said service-requesting event in response to a result of said determining step indicating that said priority level assigned to said suspended processing is not higher than said priority level assigned to said service-requesting event; and

placing a service request indicator in a storage area different from said zero level storage area in response to a result of said determining step indicating that said priority level assigned to said first suspended process is higher than said priority level assigned to said service-requesting event.

2. The method according to claim 1 including a further step of establishing a program for creating code for determining said minimal system-side context in response to an occurrence of said service-requesting event depending on which type of service-requesting event occurred.

3. The method in accordance with claim 2 which includes the steps of:

creating said minimal system-side context code prior to said occurrence of said service-requesting event; and

storing said created minimal system-side context code.

said responding step including the step of retrieving said stored minimal system-side context code for moving to said zero level storage area.

4. The method according to claim 3, wherein said minimal system-side context code is an executable daemon.

5. The method in accordance with claim 1 wherein said suspending step includes the step of generating an acknowledgment signal to indicate that handling of the service requesting-event is initiated.

6. A method to process service requests in a data processing system including a plurality of general processing units comprising the steps of:

supplying a signal identifying a requested service to be processed;

suspending execution of a first program being executed on a receiving processing unit to which said identifying signal is supplied;

starting execution of a service process corresponding to said service request by said receiving processing unit;

transferring control of said execution of said service process to an available processing unit in said system that is executing a lower priority program;

resuming execution of said first program by said receiving processing unit when said transfer of said service process is complete;

executing the service process by said available processing unit; and

resuming execution of said lower priority program by said available processing unit when execution of said service process is complete.

7. The method according to claim 6 wherein the invoking step includes additional steps of:

determining a minimum system-side context needed to identify a type and priority of said service to be processed;

generating program code to perform said service process using said minimum system-side context; and

storing said generated program code in a predetermined storage location.

8. The method according to claim 7 wherein the executing step includes the steps of:

storing a minimum system-side context of said lower priority program being executed by said available processing unit as determined by the determining step of said invoking step; and

loading a minimum system-side context of said service process; and

wherein the resuming step includes a step of retrieving the minimum system-side context of the lower priority program.

9. The method according to claim 6 wherein the transferring step includes the steps of:

comparing the priority level of said service to be processed to priority levels of programs being executed on processing units of the system; and

designating as said available processing unit a processing unit in said system which is processing a lower priority program.