Dynamic function replacement for streams framework

• US 5,815,707 A
• Filed: 10/19/1995
• Issued: 09/29/1998
• Est. Priority Date: 10/19/1995
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Krause, Michael R., Ishijima, Yoshihiro
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US08/545,561
• Time in Patent Office: 1,076 Days
• Field of Search: 395/681
• US Class Current: 719/321
• CPC Class Codes: G06F 9/4486 Formation of subprogram jump address
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

An extension to the STREAMS framework, referred to as dynamic function replacement, uses data structures that contain function pointers which allow STREAMS to execute various module or driver functions without requiring framework modification, or understanding what these functions actually do beyond their rudimentary classifications. This provides a simple, yet elegant, mechanism for replacing these function definitions and, hence, changing the execution behavior of STREAMS modules and drivers without requiring the modules or drivers to be rewritten or modified.

Claims

1. A data structure implemented in a computer system that provides a bidirectional data path between a user process, a module which is an intermediate processing element that can be dynamically added to, or removed from, said data path, and a device driver, said device driver being resident in a system kernel and controlling a peripheral device to transfer data between said kernel and said device, where data written by said user process travel downstream toward said driver, and where data received by said driver from said device travel upstream to be retrieved by a user, the data structure comprising:

a normal function that implements a specific module or driver instance;

at least one alternative function that implements an optional module or driver instance; and

a controller for generating a control command that remaps addresses of said normal function and said at least one alternative function to define new function addresses that dynamically replace said normal function with said at least one alternative function, thereby implementing said optional module or driver or instance to dynamically change the execution behavior of said data structure, while either still executing an original execution path or executing a new execution path, and without requiring any modification to said module and said driver.

2. The data structure of claim 1, further comprising:

an alternative function that customizes system tracing facilities to trace only specific events or under specific conditions.

3. The data structure of claim 1, further comprising:

an alternative function that provides support facilities for applying custom failure catchers to target specified system problems.

4. The data structure of claim 1, further comprising:

an alternative function that applies a patch on a per instance basis.

5. The data structure of claim 1, further comprising:

an alternative function that allows testing to a single data path and that allows increased flexibility and control of data path execution.

6. The data structure of claim 1, further comprising:

an alternative function that allows replacement of either all module or driver instances or replacement on a per instance basis.

7. The data structure of claim 1, wherein said system is implemented in a STREAMS framework.

8. The data structure of claim 7, wherein each module or driver defines a streamtab structure that contains pointers to qinit structures.

9. The data structure of claim 8, wherein said qinit structures are for read, write, read multiplexor, and write multiplexor queues which are created by said STREAMS framework.

10. The data structure of claim 8, wherein said qinit structures contain function addresses for open, close, put, service, and administrative functions which are invoked by said STREAMS framework on behalf of a module or driver.

11. The data structure of claim 8, wherein functions defined within said qinit structures are automatically executed by said STREAMS framework based on a current application execution path, and wherein said controller generates control commands that remap addresses of said structures to alternative streamtabs and qinit structures that define new function addresses.

12. The data structure of claim 11, wherein all contents of said qinit structures of an default alternative streamtab are identical to those of a normal streamtab except for put routines.

13. The data structure of claim 8, said controller further comprising:

at least one STREAMS ioctl command that is used to alternate dynamically STREAMS module'"'"'s/driver'"'"'s streamtab'"'"'s.

14. The data structure of claim 13, said controller further comprising:

an ioctl command that is used to alter active instances of a module.

15. The data structure of claim 13, said controller further comprising:

an ioctl command that is used to alter future instances of a module.

16. A data structure implemented in a computer system that provides a bidirectional data path between a user process, a module which is an intermediate processing element that can be dynamically added to, or removed from, said data path, and a device driver, said device driver being resident in a system kernel and controlling a peripheral device to transfer data between said kernel and said device, where data written by said user process travel downstream toward said driver, and where data received by said driver from said device travel upstream to be retrieved by a user, said system being implemented in a STREAMS framework in which each module or driver defines a streamtab structure that contains pointers to qinit structures, the data structure, comprising:

a normal function that implements a specific module or driver instance;

at least one alternative function that implements an optional module or driver instance; and

a controller for generating a control command that remaps addresses of said normal function and said at least one alternative function to define new function addresses that dynamically replace said normal function with said at least one alternative function, thereby implementing said optional module or driver or instance to dynamically change the execution behavior of said data structure, while either still executing an original execution path or executing a new execution path, and without requiring any modification to said module and said driver.

17. The data structure of claim 16, further comprising:

an alternative function that customizes system tracing facilities to trace only specific events or under specific conditions.

18. The data structure of claim 16, further comprising:

an alternative function that provides support facilities for applying custom failure catchers to target specified system problems.

19. The data structure of claim 16, further comprising:

an alternative function that applies a patch on a per instance basis.

20. The data structure of claim 16, further comprising:

an alternative function that allows testing to a single path and that allows increased flexibility and control of path execution.

21. The data structure of claim 16, further comprising:

an alternative function that allows replacement of either all module or driver instances or replacement on a per instance basis.

22. A method for implementing a data structure in a computer system that provides a bidirectional data path between a user process, a module which is an intermediate processing element that can be dynamically added to, or removed from, said data path, and a device driver, said device driver being resident in a system kernel and controlling a peripheral device to transfer data between said kernel and said device, where data written by said user process travel downstream toward said driver, and where data received by said driver from said device travel upstream to be retrieved by a user, said system being implemented in a STREAMS framework in which each module or driver defines a streamtab structure that contains pointers to qinit structures, the method comprising the steps of:

providing a normal function that implements a specific module or driver instance;

providing at least one alternative function that implements an optional module or driver instance; and

generating, with a controller, a control command that remaps addresses of said normal function and said at least one alternative function to define new function addresses that dynamically replace said normal function with said at least one alternative function, thereby implementing said optional module or driver or instance to dynamically change the execution behavior of said data structure, while either still executing an original execution path or executing a new execution path, and without requiring any modification to said module and said driver.

23. The method of claim 22, wherein said qinit structures are for read, write, read multiplexor, and write multiplexor queues which are created by said STREAMS framework.

24. The method of claim 22, wherein said qinit structures contain function addresses for open, close, put, service, and administrative functions which are invoked by said STREAMS framework on behalf of a module or driver.

25. The method of claim 22, further comprising the steps of:

automatically executing functions defined within said qinit structures by said STREAMS framework based on a current application execution path; and

generating a control command to remap addresses of said structures to alternative streamtabs and qinit structures that define new function addresses.

26. The method of claim 22, wherein all contents of said qinit structures of an default alternative streamtab are identical to those of a normal streamtab except for put routines.

27. The method of claim 22, further comprising the step of:

using at least one STREAMS ioctl command to alternate dynamically STREAMS module'"'"'s/driver'"'"'s streamtab'"'"'s.

28. The method of claim 27, further comprising the step of:

using an ioctl command to alter active instances of a module.

29. The method of claim 27, further comprising the step of:

using an ioctl command to alter future instances of a module.