System and method for emulating multi-tasking pipelines in a single tasking environment

Abstract: A control system emulates a multi-tasking environment using a single tasking processor A number of predefined tasks are provided in a task library. When a host application (120) needs processed data from a data source (12), the host application (120) creates a pipeline (40) of initialized instantiations of one or more of the tasks (40A,40B,40C) from the task library. When the host application (120) invokes the pipeline (40), the data request is made from the host application (120) to a downstream-most section (40C) of the pipeline. The data request ripples upstreamwardly to the upstream-most instantiation of one of the tasks (40A) from the task library. The upstream-most instantiation of a task obtains data from a data source (12) and returns it downstreamwardly to the host application (120), each instantiation of a task from the task library further operating on the data.

Description: This invention relates to processing data in a single-processing environment by emulating a multi-processing environment. In particular, this invention relates to an object-oriented system employing a library of predefined objects or data structures which can be linked between a host application and a data source to create a stream-oriented data processing structure emulating a UNIX®-like pipeline data structure. The use of data processing pipelines in true multi-processing environments is well known. Examples of known multi-processing environments include both multiple-processor systems and high level systems where a single processor is able to support true multiprocessing. The UNIX® operating system is often used in such multi-processing systems. In such multi-processing environments, data processing pipelines are extremely useful for processing large, highly structured data blocks, such as those associated with image processing, database processing, or spreadsheet processing. In such data blocks, various data processing operations must be performed on each data element of the data blocks. Further, the various data processing operations are performed in a specific order. In a multi-processing environment, data processing pipelines provide a very efficient method for processing the data blocks. In these data processing pipelines, each separate data processing operation is defined as a section of the pipeline. Each section is linked to one or both of the sections (the upstream and downstream sections) to which it is adjacent. The data processing operation thus form a chain of linked pipeline sections between a data source and a host application. In a computer having a number of independent processors, each pipeline section corresponds to one of the processors. In this case, each processor works independently, and the computer operating system controls the flow of data between processors and the memory allocation. While this efficiently processes the data, the overhead necessary to control the processors and the memory consumes a significant proportion of the system resources. Likewise, in a computer having a single processor which can simultaneously run a number of different independent processing operations, or processes, each pipeline section corresponds to one of the independently-running processes. In this case, the operating system allocates the run-time of each process, the flow of data between each process and memory and the memory allocation. The overhead necessary to control the computer in this case consumes an even larger proportion of the system resources, as each process and its data must be swapped into and out of the processor each time it is run. Additionally, since the processes communicate through the operating system, dynamically altering the pipeline is difficult, if not impossible. In general, the source of data for the pipeline can be, for example: 1) a spreadsheet providing financial information; 2) the records within a data base file providing database information; and 3) image data generated by a conventional image scanner from an original document, a computer generated image, or the like. In contrast, the host application could be a graphics program for producing pie charts, bar charts or the like from processed financial data; an inventory, accounting, or merging program which uses processed database data; or an image forming apparatus for forming an image from the processed image data. Regardless of the particular source of data or ultimate host application, the first, or upstream-most, section of the data processing pipeline is generally the data source for the pipeline. Alternately the data source for this first pipeline can be a second pipeline. In this case, a special branching or "fan-out" pipeline section of the second pipeline can be used to supply data to both the first pipeline and the downstream sections of the second pipeline. In either case, the first pipeline section obtains a data element for the pipeline from the source of data and makes the data element available to the immediately downstream, or second, pipeline section. The second pipeline section sequentially receives the data element from the first pipeline section, processes the data element, and passes it downstream to the next immediately downstream or third pipeline section. Simultaneously, in a true multi-processing environment, the first pipeline section obtains the next data element from the source of data and outputs it to the second pipeline section while the second or downstream-adjacent section of the data pipeline processes the data element received from the first pipeline section and outputs it to the third section of the data processing pipeline. Accordingly, as each data element is processed by one of the pipeline sections, it is output to the next downstream section until it is output to the host application. In this way, the data can be efficiently and quickly processed in the multi-processing environment by associating one processing operation or processor with each section of the pipeline. This ensures that the pipeline is able to process the data block with the data throughput being limited only by the least efficient pipeline section and the inefficiencies caused by the overhead. In contrast, in a single-processing environment, a variety of methods for processing the data are available, although all them are extremely inefficient. For example, each data processing operation is applied to every data element of the data block before any other data processing operation is applied to any data element of the data block. That is, every element of the data block must be processed before the next data processing operation is performed on any of the already-processed data elements. Thus, the efficiency of the single tasking data processing operation is proportional to the efficiency of each data processing operation. Therefore, because data elements continually move from one data processing section of a pipeline in a multi-processing environment, the necessary overhead required to manage the memory allocation of the data block is small in comparison to a single-processing environment, where each data element must be repeatedly read from and written to memory. That is, the overhead required to manage the necessary memory is substantial in a single-processing environment. EP-A-357,444 discloses a dynamically configurable data processing pipeline having a set of stages, each carrying out a separate data processing operation. The pipeline is demand driven in that stages obtain input data by calling preceding stages, and when called each stage processes its input data to produce output data returned to its caller. A stage determines which other stage or stages to call by inspecting one or more entries in the pipeline description table containing pointers to the other stages. The pipeline controller responds to input commands requesting various types of pipeline data processing operations by adjusting the pointers in the pipeline description table so that only stages necessary to execute the command are called. Accordingly, this invention provides for a control system for emulating a multi-processing data processing pipeline using a single-processing processor according to claim 1 of the appended claims. The invention further provides a method for defining and operating a data processing pipeline in a single application processor, according to claim 2 of the appended claims. The invention further provides a control system for operating a single processing computer to emulate a multi-processing computer, according to claim 3 of the appended claims. The invention further provides a control means for pipelined data processing, according to claim 4 of the appended claims. In particular embodiments of the method of this invention, a library of data processing operations is provided. Each data processing operation, or function, in the library is a class or subclass in an object-oriented system. Each section of the pipeline is an instantiated function, or task, and comprises one or more data processing functions and sufficient data structure to self-define the state of the task. In operation, when a host application requires processed data input from a source of data, a data processing pipeline is formed from the source of data to the host application. The data processing pipeline is formed by calling one of the functions in the data processing library and initializing the called function to form a task. This task becomes the first or upstream-most section of the pipeline. The first pipeline section obtains a data element from the source of data. The source of data can be a data generating device, such as a scanner, a facsimile machine, a remote computer, a sensor or the like, which outputs a serial or parallel data signal, or a block of stored data in a ROM, a portion of a RAM, or a disk in a disk drive. The data element can also be directly generated by the first pipeline section itself. In this last case, the data element can be obtained from the value of an initialized variable, from the state of the first pipeline section, or the like. When it first initialized, the backward or upstream link of the host application is set to the first pipeline section. Presumably, a second pipeline section is needed to process the data element obtained by the first pipeline section. Therefore, the host application creates another task by initializing one of the functions in the library. When this second pipeline section is created, it is automatically linked to the first pipeline section. Additionally, the link of the host application is set to the second pipeline section. If no other data processing operation is required, backward link of the host application remains between the portion of the host application which requires the processed data and the second pipeline section. Alternately, should the pipeline require additional sections, the host application makes additional calls to the function library to create more tasks or pipeline sections. The newly created tasks become the third, fourth, etc. sections of the data processing pipeline. As each additional pipeline section is created, the backward link between each additional pipeline section and the immediately upstream pipeline section is formed. Again, after the last section of the pipeline is created, the backward link of the host application remains set to the last section of the pipeline. In this way, access to each pipeline section is controlled and maintained by the immediately downstream pipeline section (or the host application for the last pipeline section) rather than by the operating system. Thus, the overhead necessary to maintain the memory is minimal and to schedule the execution of the tasks is non-existant. Thus, the control system of the present invention combined the advantages of efficient processing, from the multi-processing environment, with the advantage of minimal overhead, from the single-processing environment, while avoiding the disadvantages of these environments. Further, the single-processing application can therefore be run on a single-tasking processor, a single-processor, multi-tasking system using automatic timesharing, or a true multi-tasking system, while maintaining the advantages indicated above. That is, since the host application, rather than the operating system, creates, maintains, and controls, and ends the pipeline, the pipeline structure is independent of the type of process or running the host application. Therefore, the host application can be one of a number of independent applications being run on a single-processor multi-tasking system. At the same time, the host can be running a pipeline from a scanner using this pipeline system without using the operating system to schedule the pipeline or allocate, maintain, and deallocate memory for the pipeline. Thus, the disadvantages normally associated with running a pipeline using the operating system can be avoided. To begin processing the data block, the host application requests data from the last section of the pipeline. Each section of the pipeline requests, in turn, data from the upstream pipeline section to which it is linked. This is done by making a procedure call from the downstream pipeline section to invoke the upstream pipeline section. This is analogous to pushing the downstream pipeline section onto a stack. As data is requested from each upstream pipeline section, the single-processing processor stops processing the downstream pipeline section and begins processing the upstream pipeline section. Once the first pipeline section is reached, the first pipeline section obtains or generates a data element and returns the data element to the second pipeline section. Once the first pipeline section returns the data element, the CPU ceases running the first pipeline section and begins running the second pipeline section. That is, the downstream pipeline section is returned to from the procedure call which invoked the upstream pipeline section. This is analogous to popping the downstream pipeline section off the stack. Once the second pipeline section has processed the data element, the data element is returned to the third pipeline section. Then, the third pipeline section performs its data processing operation(s) on the processed data element received from the second pipeline section, returns the processed data element to the fourth pipeline section and stops operating. The data element is similarly processed in each pipeline section. After the last pipeline section processes the data element, it returns the fully processed data element to the host application. Then, if the host application wants (or needs) another processed data element, it again requests a processed data element from the last pipeline section. In this way, the processed data ripples down the pipeline in a highly efficient and low overhead manner. In addition, the efficiency of the data processing pipeline depends only on the least efficient link of the pipeline. This invention will be described relative to the following drawings, in which like reference numbers refer to like elements, and wherein: Figure 1 shows a block diagram of the system of the present invention; Figure 2 shows a block diagram of a pipeline of the present invention; Figure 3 shows a block diagram of a flow of data in the pipeline of the present invention; Figure 4 shows a diagram of a linked pipeline for an exemplary data processing program; Figure 5A and 5B show an exemplary code listing for a sample task; Figure 6 shows a code listing for an exemplary host application which calls the tasks from the library to form the pipelines; Figure 7 shows a listing of the outputs of the pipelines shown in Figure 4 and listed in Figures 5A, 5B and 6; Figure 8 is a flow chart of the main routine; Figure 9 is a flow chart of the function initialization routine; Figure 10 is a flow chart of the invoking and processing routine; Figure 11 shows the controller of this invention; and Figure 12 shows a generalized task means of this invention. As shown in Figure 1, a computer 100 has a single-processing controller (CPU) 20. The computer 100 also has an input/output interface (I/O interface) 22, a ROM 24, and a RAM 26. The CPU 20 sends control signals to the I/O interface 22, ROM 24, and RAM 26 through control lines 28, and sends and receives data from the I/O interface, ROM 24, RAM 26 through a data bus 30.. A task library 10, a data source 12, a display 14, a keyboard 16, a mouse 18, and a disk drive 19 are connected to the CPU 20 through the I/O interface 22. The mouse 18 represents any secondary pointing device, such as a mouse, a trackball, a light pen, a touchscreen, a touchpad or the like. The disk drive 18 represents any non-volatile storage device, such as a hard drive, a hard card, a floppy disk and floppy disk drive, a CD-ROM and CD-RAM disk drive, a flash memory or the like. The CPU 20 is a single-processing processor. That is, the CPU is able to actively process data for at most one application at a time, and is able to already run and perform only a single data processing operation at any one time. The I/O interface 22 connects the CPU 20 through either a serial data port (not shown) or a parallel data port (not shown) to serial or parallel data input sources or data output sources. These sources of data of course include the disk drive 19 and the mouse 18, as well as the keyboard 16 and the data source 12. The data source 12, as noted above, includes a scanner, a facsimile machine or the like, a remote computer, a sensor or the like. The I/O interface 22 also comprises the hardware necessary for driving the display 14 and for inputting signals from the keyboard 16, the mouse 18 and the disk drive 19. The ROM 24 stores all the basic operating programs for the CPU 20, including bootstrap programs and the like. The RAM 26 comprises a large number of randomly accessible memory locations. The RAM 26 can be divided into blocks of allocatable memory, such as blocks 26a, 26b, 26c, 26d, 26e and 26f. The blocks of allocatable memory 26a-26f store a host application and one or more instantiations of the data processing data structures forming the tasks, (i.e., the sections of the data processing pipeline). The display 14 outputs visual information, while the keyboard 16 is used to input information to the computer 100. The function library 10 stores a library of uninitialized data processing structures or objects which form the data processing functions called by the CPU 20. While the function library 10 is shown as an independent element accessed through the I/O interface 22, it is understood that the function library 10 can be stored in the ROM 24 or on a nonvolatile memory device accessed through the disk drive 19. Further, newly written data processing objects or functions which have not yet been stored to the non-volatile memory device in the disk drive 19 or to the function library 10 can be stored in the RAM 26. Likewise, the data source 12 is shown as being external to the computer 100 and accessed through the I/O interface 22. However, it is understood that the data source 12 can be data stored in the ROM 24, the RAM 26, on the non-volatile memory device in the disk drive 19 or within a register counter or internal memory of the CPU 20. The data source 12 can comprise data input through the keyboard 16. Finally, as noted above, the first pipeline section can generate the data elements itself, rather than obtaining them from some external source. As shown in Figure 11, the controller 20 of the present invention comprises a host application means 50, a library means 10, a memory management means 56, a last task means 60, at least one intermediate task means 62 and a first task means 64. The controller may also include a data source means 66. However, the controller 20 need not include the data source means 66. In this case, the first task means 64 also performs the function of the data source means 66. A plurality of links 70 connect the first task means 64, the at least one intermediate means 62 and the last task means 60 in a data processing pipeline 80 connected by a link 70 to the host application means. Of course, it should be understood that simple pipelines 80 may include only the first task means 64 and the last task means 60. Finally, a data input link 72 connects the data source means 66 to the first task means 64. The host application means 50 includes a data processing means 58 for further processing data received from the data processing pipeline 80. Initially, the controller 20 includes only the host application means 50 the library means 10, and the memory management means 56. The host application means 50 operates the controller 20 according to instructions contained within the host application means 50. The controller 20 can be a single-tasking controller, a single-CPU, multi-tasking controller or a true multi-CPU, multi-tasking controller. In any case, the host application means 50 itself creates a single-tasking environment within the controller 20. When the host application means 50 determines that it needs processed data from the data source 66, it creates and invokes the data processing pipeline 80. The host application means 50 thus includes an initializing means 52 and an invoking means 54. The initializing means accesses the library means 10 to obtain a function and initialize the function to create a task. That is, the library means 10 stores a number of data processing functions. The data processing functions are classes or subclasses of objects within an object-oriented system when in the library, the functions are uninitialized. The initializing means 52 accesses the library means 10 to obtain one of the uninitialized functions. The initializing means 52 then initializes the obtained function to create an instantiated function or task in the controller 20. The instantiated function, or task, is linked to the host application means 50 or another previously created task. If the task is linked to the host application means, it is the last task 60. If the task is linked to another task, and another task is linked to it, it is an intermediate task 62. If the task is linked to another task, and obtains data from the data source means 66, or generates data itself, it is the first task 64. In initializing the function to create a task, the initialization means 52 works with the memory management means 56 of the controller to allocate one of the memory blocks 26a-26f of the memory 26 to store the task. After all of the desired tasks are initialized by the initializing means 52, the invoking means 54 invokes the pipeline 80 by requesting data from the last task means 60. The request from the invoking means 52 ripples in an upstream direction of the pipeline 80 towards the first task means 64. When the request reaches the first task means 64, the first task means obtains data from the data source 66 or generates the data itself. Then, the first tasking means 64 returns the data in the downstream direction to the intermediate task means 62. The intermediate task means 62 processes the data and returns it to the last task means 60 The last task means 60 processes the data and returns it to the host application means. Then, if more data is needed by the host application means, the invoking means 54 again invokes the pipeline 80. Once the host application 50 has all of the desired data, the invoking means 54 again invokes the pipeline 80 to shut down and clean-up any errors arising from the pipeline 80, by requesting error codes from the pipeline. The request ripples upstream as before. Each tasking means determines if it generated any error codes and returns them. Once the error codes are returned, the initializing means 52 signals the memory management means 56 to release the memory allocated to the task means 60-64 of the pipeline 80. Figure 12 shows a generalized task means 68, which represents any of the task means 60-64. The generalized task means 68 comprises a link means 82, at least one channel means 84. a data processing means 86, a data analyzing means 88, a task state means 90, an error code generating means 92, an external port means 94 and a reconfiguring means 96. Of course it should be understood that the actual tasks means 60-64 may have different combinations of these elements, lacking one or more of them. Further, the first task means 64 will also include a data obtaining/generating means 98 for obtaining or generating data for the pipeline 80. The link means 82 links the generalized task means 68 to a next or upstream task means 68 when a forward link is used, or a previous or downstream task means 68 when a backward link is used. Of course both links can be used at once. The generalized task means 68 receives data returned from the next task means 68 through the channel means 84. The data is then processed using the data processing means 86 before it is returned to the previous task means 68 through the channel means 84. The task state means 90 maintains the state of the task means 68. The task state means 90 also controls all of the other means of the task means 68. The data analyzing means 88 determines if the data received from the next task means 68 is suitable for the data processing means 86. If the data is not suitable, the data analyzing means has two alternate possible responses. In a first type of response, a simplified task means 68 simply returns an error code generated by an error code generating means 92, instead of the data, to the previous task means. When the host application means 50 receives the error code instead of data, the application means 50 uses an error handling system to determine the nature (and cause) of the error. The host application means 50 can then gracefully exit or attempt to recover from the error by reconfiguring and/or reinitializing the pipeline 80. In a second type of response, a complex task means 68 includes a reconfiguring means 96, which attempts to dynamically reconfigure the pipeline 80 to recover from the error. The reconfiguring means 96 does this by dynamically initializing additional task means 68 and inserting them into the pipeline 80. The reconfiguring means does this by accessing other tasking means 68 through the external port means 94. The external port means permit a variety of access modes to the tasking means 68. These modes include examining and/or altering the task state means 90, examining the error code generating means 92, altering the link means 82, or the like. Of course, even if the task means 68 has a sophisticated reconfiguring means 96, unrecoverable or hard errors may still occur. In this case the task means again uses the error code generating means 92 to generate the error code. Finally, in a second embodiment, the link means 82 can link, instead of the task means 68 itself, the channel means 84. That is, the link means 82 links the channel means 84 directly to the next or previous task means 68. Therefore, if a task means 68 has a number of channel means 84a, 84b, 84c, each channel means 84a-84c can be linked to a different next or previous task means 68. In contrast, in the first embodiment, because the link means 82 linked task means 68, all of the channels 84a-84c of the task means 68 would be linked to the same next task means 68. As shown in Figure 2, each initialized function, or task, can be visualized as a section 40a, 40b and 40c of the pipeline 40 running between the data source 12 and the host application 120. The host application is the application currently being run by the CPU 20 (and stored in the RAM 26). Each section 40a, 40b and 40c of the pipeline 40 comprises one or more data processing channels 42, a data structure 44 defining the state of the pipeline section and zero, one or more external ports 46. Each pipeline section 40b and 40c and the host application also comprises a backward link 48 which links the pipeline section 40b, 40c or the host application 120 to the the immediately upstream pipeline sections 40a, 40b or 40c, respectively. Alternately, each pipeline section 40a, 40b and 40c has a forward link 48' to the immediately downstream pipeline section 40b and 40c or the host application 120. Finally, both the backward links 48 and the forward links 48' can be provided. In the preferred embodiment of the control system, the pipeline comprises "intelligent" pipeline sections. These intelligent pipeline sections are able to dynamically reconfigure the pipeline as it is operated from the host computer, without needing any intervention by the host application. For example, the pipeline section 40b is able to determine if it is able to process the data element returned by the pipeline section 40a. If pipeline section 40b is not able to process the data element, pipeline section 40b dynamically calls the function library 10 and creates a new pipeline section 40d. The pipeline section 40d is linked to the pipeline section 40a. The pipeline section 40b then alters its own link, to point to the pipeline section 40d rather than the pipeline section 40a. Alternately, if the pipeline section 40b determines that it is not able to process the data, (even if it reconfigures the pipeline), then it returns an error code indicating the hard error. An error handling means in the host application determines, from the library, the nature of the error. In one embodiment, the host application will determine if it can re-create the pipeline to recover from the error. If so, it will re-initialize the pipeline. However, if the host application is not able to recover from the error, or is not provided with the capability to do so, the host application will gracefully exit. Such a non-recoverable error can occur, for example, in processing an image. If the header indicated that there are 1000 scanlines in the image, but no scanline image data element was returned on the 998 th call to the first pipeline section, the system will encounter a hard error. This error cannot be recovered from, regardless of the ability of the pipeline to reconfigure itself, as there is simply no data to process. In this case, the first pipeline section will return an "ERR" error code. The host application will then use the error handling means to determine the reason for the error code. After determining the nature of this error, the host application will gracefully exit, as any reconfiguring or re-initializing of the system is pointless. Then, the pipeline section 40b requests data from the pipeline section 40d. The pipeline section 40d requests data from the pipeline section 40a, which re-returns the data element. However, the pipeline section 40a now returns the data element to the pipeline section 40d rather than the pipeline section 40b. Alternately, the pipeline section, when calling the function library 10, can provide the data element, so that the pipeline section 40d has the data element as soon as it is created. Then, when the pipeline section 40b requests data from the pipeline section 40d, the pipeline section 40d can immediately process and return the data element. Further, if the forward link 48' is provided, the intelligent pipeline section can include, in their data structures, means for determining if the data element needs to be processed by this pipeline section. If not, the pipeline section can dynamically reconfigure the pipeline, without any involvement by the host application, to remove itself from the pipeline. The forward link is necessary, so that this pipeline section knows which downstream pipeline section to alter, so that it is linked to the proper upstream pipeline section. The external ports 46 are used to examine the current state of a pipeline section, to write data to the data structure 44 of a pipeline section, to change that pipeline section's current state or to dynamically alter the linkage 48 of the pipeline section(s) to dynamically add sections to or delete sections from the pipeline 40. In general, the external ports 46 are used to control the pipeline 40, independently of the data channels 42, which only process the data elements. That is, the data channels 42 are used solely to process the data received from an upstream pipeline section and output the processed data to a downstream pipeline section. The external ports 46 allow access to the data structure 44 of the pipeline section without affecting the operation of the data channels 42. Thus, in an alternate embodiment, if it becomes necessary, for example, after the pipeline 40 is created, to add the pipeline section 40d between the pipeline section 40a and the pipeline section 40b, this is accomplished using the external ports 46. In this example, the pipeline section 40c has, as a part of its data structure, a structure for testing the data in the channels. If the form of data is, for example, incompatible with the form necessary for the proper operation of pipeline section 40c, but the data must be altered before, for example, pipeline section 40b, the pipeline section 40c dynamically initializes the new pipeline section 40d and inserts it between the pipeline sections 40a and 40b. The pipeline section 40c does this by accessing, through an external port 46 in the pipeline section 40b, the data structure 44 of the pipeline section 40b. The pipeline section 40c alters the link 48 of the pipeline section 40b, to change the link 48 from the pipeline 40a to the new pipeline section 40d. Likewise, the data structure 44 of the new pipeline section 40d is accessed to ensure it is properly initialized and linked to the pipeline section 40a. In operation, when a host application, such as the application shown in Figure 6, requires data from the data source 12, the host application first forms the pipeline 40 by calling and initializing functions from the function library 10. In the example shown in Figure 6, the variables "i", "n", "add_value", and "mul_value" are initialized in line 5 of the host application. In line 6, the first task 40a is defined as a "null" task. While the first task can be connected to obtain data elements from the data source 12, it is possible to indicate, using the "null" command, that the first task 40a also serves as the data source 12. In line 7 of Figure 6, the number of tasks in the pipeline 40 is determined by the command line, shown in Figure 7, which initiated the host application. In general, the length and constituents of the pipeline 40 will be dynamically determined as the host application runs. Alternately, the length and constituents of the pipeline 40 are expressly set forth in the host application. Finally, even when the initial length and constituents of the pipeline 40 are either dynamically determined or expressly set forth, the pipeline 40 can dynamically reconfigures itself depending upon the data received from the data source 12. In the example shown in Figure 6, as shown in line 7, the length of the pipeline 40 is expressly set forth in the command line initiating the program. In this case, the length of the pipeline is 5, as shown in Figure 7. As shown in lines 8 and 9 of Figure 6, each function is called and initialized, extending from the data source to the host application. In this case, as shown in line 6 of Figure 6, the first task 40a also acts as the data source. Further, as indicated in line 9, each task in the pipeline 40 is a different instantiation or task of the same function. As indicated in line 9 of Figure 6 and line 17 of Figure 5A, when the function in this example "Math Task" is initialized, its data structure contains two channel data buffers, each set to the current value of "i", and a pointer pointing to the upstream task in the pipeline. Additionally, if there is no upstream task in the pipeline, the pointer is set to "null". As the functions in the function library 10 are defined as objects in an object-oriented language, each time a function is initialized in the example shown in Fig. 6, it is in fact a different instantiation of the same function. Thus, a single pipeline 40 may have multiple copies of any single function. Each copy of the function is thus a different instantiation of the base function stored in the library and acts as a different task or section of the pipeline 40. Thus, the functions in the function library 10 are recursive, as they can be used more than once in any single pipeline. After each task in the pipeline is created, in lines 8 and 9, the channels of the initialized tasks, in this case two, are executed in lines 10 and 11. Once the host application shown in Figure 6 receives the final data from the tasks through the channels executed in lines 10 and 11, the output shown in Figure 7 is printed, as set forth in lines 12 and 13 of Figure 6. As indicated above, in lines 8 and 9, in the host application of Figure 6, the pipeline comprises a number of independent instantiations of the function "MathTask". Figures 5A and 5B show the library object "MathTask" which is called by the host application in lines 8 and 9 of Figure 6, to form each instantiation necessary for the pipeline formed by the host application, as shown in Figure 6. In lines 1-6 of the "MathTask" function shown in Figure 5A, the primary data structure is defined. As shown in lines 1-6, the data structure includes two channels, channel 1 and channel 2, and a backward or upstream link. Next, in lines 7-12, the data structure particular to this function, "aval" and "mval", for the first and second channels, respectively, are defined. Next, in line 17, the instantiation procedure for the task "MathTask" is defined, with the data requests "avalue" for channel 1 and "mvalue" for channel 2 and the upstream link "link". In lines 18-20, the variables "avalue" and "mvalue", for channel 1 and channel 2, respectively, and the link are defined. Finally, in line 21, the procedure for creating a task of the function "MathTask" and for allocating a memory block of the RAM 26 is defined. Next, as shown in lines 28-37 of Figure 5B, the data processing procedure and data structure associated with channel 1 is defined. The channel 1 data processing procedure obtains a number from the immediately upstream task. Additionally, as indicated in line 6 of Figure 6, the first task in the pipeline is a "null" task. The result arising from the "null" status for the first task is defined in line 32, which defines the initial value of "val" as zero. In line 33, if a backward link exists, the value "val" is set, in line 34, to the channel 1 output of the upstream task. Then, in line 35, the value "val" is updated by adding the channel 1 addend "aval" of the current pipeline section to it. The channel 1 addend value "aval" for each pipeline section was set in line 25 to the state parameter "avalue" of the pipeline section, which was set in line 9 of Fig 6. Finally, the channel 1 data processing procedure ends by returning the new value "val" to the immediately downstream pipeline section. Similarly, in lines 38-47 of Figure 5B, the channel 2 data processing procedure is defined. The only differences occur in line 39, which uses the channel 2 procedure initialized in line 23 of Figure 5A rather than the channel 1 processing procedure initialized in line 22 of Figure 5 A. Further, in line 42 the value "val" is preset to one to account for a "null" data source for first pipeline section. In line 45 the new value "val" is equal to the old value "val" multiplied by the channel 2 multiplicand, which was set to the state parameter "mvalue" in line 26 of Figure 5A, which was set in line 9 of Fig. 6. In operation, the host application, shown in Figure 6 in lines 8 and 9, calls the function "MathTask" an indicated number of times. The first instantiation of the function "MathTask" is set up as a null task, unconnected to a data source. By looping again through lines 8 and 9, a second instantiation of the function "MathTask" is formed with a backward link to the previous instantiation of the task "MathTask". Thereafter, for each loop through lines 8 and 9 of Figure 6, a further instantiation of the function "MathTask" is formed. Once the last loop through lines 8 and 9 of the host application shown in Figure 6 is completed, the backward link from the host application to the last one of the tasks "MathTask" remains set. Figure 4 shows a three-section pipeline initialized in this manner. Then, in lines 10 and 11, the host application requests data from channel 1 and channel 2 of the last instantiation of the function "MathTask". The last task turns around and requests data from the task immediately upstream of it. This continues until the first instantiation of the "MathTask" receives a request for data through channel 1 and channel 2. Figure 3 shows an example of this type of data flow. After the host application involves the pipeline in lines 10 and 11 of Fig 6, the last pipeline section invokes each channel, in lines 34 and 44 of Fig. 5b of the pipeline section to which it is linked. Then, in turn, each invoked pipeline section invokes the upstream pipeline section to which it is linked. When the first pipeline section is reached, it obtains the data element from the data source 12, or, in this case, self-generates the data element. The first pipeline section then returns the data element to the pipeline section which called it, as described above. The first instantiation of the function "MathTask" then performs the data processing procedures defined for channel 1 and channel 2. The first instantiation returns a value of 1, equal to 0+1, for channel 1 and a value of 1, equal to 1x1, for channel 2, to the second or instantiation of the function "MathTask". In turn, each instantiation of the function "MathTask" adds a first number to the value held in channel 1 and multiplies the number held in channel 2 by a second number. In the example shown in Figs. 5A and 5B, the first and second numbers are the addend and the multiplicand initialized when the pipeline was created in line 9 of Fig. 6. However, the numbers could have been generated dynamically. Accordingly, the processed data in channels 1 and 2 ripples downstream towards the host application. Eventually, the downstream-most instantiation of the function "MathTask" provides the requested data to the host application. When the CPU 20 runs the host application shown in Figure 6, it stores the host application in memory block 26a of RAM 26. The host application is actually a data structure stored in the allocatable memory block 26a. The data structure itself comprises a template over the designated memory locations, the template defining the flow of control operations of the CPU 20. In a first section of the allocated memory block 26a, various memory locations are defined and/or allocated as variables. The data block 26a also contains various memory locations defining the state of the host application, and various memory locations acting as buffers for storing data requested by the host application or data being processed by the host application. Similarly, when the host application calls the function library 10 to initialize, for example, an instantiation of the function "MathTask", another data block 26b is allocated to that task or pipeline section. Like the host application, the initialized pipeline section is actually a data structure in the allocated memory block 26b comprising a template over the allocated memory block 26b. The allocated memory block includes buffers for storing data being processed, various memory locations for defining types of data, procedure pointers indicating from where this task receives its data from, various memory locations storing data defining the state of the task and one or more data buffers for storing the processed data received from an immediately upstream instantiation of the function "MathTask". The allocated data block 26b also includes the data structures defining the data processing operations for channels 1 and 2. The data structure in the allocated data block 26b alternately includes look up tables for performing the data processing or as a pointer look up table to other functions in the function library 10. In general, each task, as it is initialized and allocated to one of the data blocks 26a-26f, automatically allocates buffers sufficient for the data inputs, data outputs, task state and various data processing procedures performed by the task. Figures 8-10 show generalized flow charts for the control routine implementing this method. As shown in Fig. 8, after starting, the host application is run by the single processing CPU 20 in step S10. In step S20, the controller checks to see if a data processing pipeline is needed in the current operation of the computer 100. If not, the control routine returns to step S10. However, if a pipeline is needed, the control routine continues to step S30, which calls a function from the function library. Then, in step S40, the called function is initialized to form a first task or first pipeline section. Then, in step S50, the controller checks to see if any additional pipeline sections are needed. If so, the control routine returns to step S30 to call the next function from the library. Accordingly, the control routine loops through steps S30-S50 until no further tasks are needed. At this point the control routine continues to step S60. At step S60, the pipeline is invoked. In step S70, the pipeline returns the processed data element to the host application. Then, in step S80, the controller determines if any additional data is needed. If so, the control routine returns to step S70 to again invoke the pipeline However, if no further data is needed, the control routine continues to step S90, where the pipeline is de-initialized by de-allocating the memory allocated to the various pipeline sections. In step S100, the next command of the host application is run. Then, in step S110 the controller determines if any further pipelines of the host application need to be run. If so, the control routine returns to step S30. However, if a pipeline is not needed at this point, the control routine continues to step S120, where the controller determines if the host application is finished. If so, the control routine stops. Otherwise, the control routine returns to step S100. Figure 9 shows the flowchart for the initializing step S40. After entering the initializing routine in step S40, the control routine continues to step S200, where the primary data structure for the task is created. Then, in step S210, the portion of the data structure specific to this task is created. Then, in step S220 the channel data structures are created, and in step S230 the backward link is created. If a forward link is necessary, its data structure is defined, but it will not be finished until the pipeline is invoked, as the downstream task to which the forward link links has not yet been created. The link comprises a procedure pointer for calling the linked pipeline section. Then, in step S240, the control routine returns to step S40. Figure 10 shows the flow chart for the invoking routine of step S60. Starting from step S60, the control routine continues to step S300 where the host application requests data from the last pipeline section. Then, in step S310, the current pipeline section requests data from the next upstream pipeline section. In step S320, the controller determines if the next pipeline section is the first pipeline section. If not, the control routine returns to step S310. However, if the next pipeline section is the first pipeline section, the control routine continues to step S330. In step S330, the controller determines if the first pipeline section is a "null" section. If not, the control routine continues to step S340, where the first pipeline section obtains the data element from an external source. If the first pipeline section is a "null" section, the control routine continues to step S350, where the first pipeline section self-generates the data element In either case, after either steps S340 and S350, the control routine continues to step S360, where the first pipeline section returns the data downstream to the second, or next pipeline section. In step S370, the next pipeline section processes the data. Then, in step S380, if the next pipeline section is the last pipeline section, the processed data is returned to the host application in step S390. However, if the next pipeline section is not the last pipeline section, the data is returned to a new next pipeline section and the data element is processed, as shown by the loop back to step S360. This "looping" continues until the last pipeline section is reached and the data is returned to the host application in step S390. The control routine then returns to step S60. In a second embodiment of the data processing pipeline of this invention, a forward link, either replacing or in addition to the previously defined backward link is provided. In this case, after the backward link from the current downstream-most instantiation of one of the task of the task library is defined, a forward link from the immediately upstream task to the downstream-most task is defined. Alternately, only a forward link need be provided. However, in this case, the pipeline sections are initialized from the host application upstream towards the data source of data, it it exists, and are invoked from the data source downstream to the host application. In a further embodiment, rather than providing a single forward link or a single backward link between tasks, when each task has two or more data processing channels, the channels themselves are linked together by the forward and/or backward links. In this case, each channel could be backward or forward linked to any other corresponding channel of any one of the instantiations of the tasks from the task library. Thus, one of the channels of a first pipeline section is linked to the corresponding channel of a second pipeline section, while another channel of the first pipeline section is linked to the corresponding channel of a third pipeline section. In yet another embodiment of the present invention, special "fan-in" and "fan-out" pipeline sections are provided. In these pipeline sections, two or more upstream pipeline sections are linked to a single downstream pipeline section using a fan-in branching pipeline section. Similarly, a single upstream pipeline section is connected two or more downstream pipeline sections using a fan-out branching pipeline section.

Claims: A method for emulating multi-processing pipeline data processing using a single-processing processor, wherein a host application creates a pipeline of linked data processing tasks for supplying processed data to the host application, then requests data from the pipeline, comprising the steps of: running a host application on the single-processing processor; the host application creating a data processing pipeline of linked data processing tasks to supply the host application with processed data from a data source; the host application invoking the pipeline by requesting data from the pipeline; and deleting the pipeline when the host application no longer needs data from the pipeline; wherein the step of creating the pipeline comprises the steps of: (a) instantiating a first function selected from a plurality of predefined functions as a first task; (b) defining a link from the host application to the first task; (c) instantiating a second function selected from the plurality of predetermined functions as a second task; (d) defining a link from the first task to the second task and redefining the link from the host application to the second task; (e) repeating steps (c) and (d) for subsequent tasks, the host application being linked to a last instantiated task, each task being stored in a memory, each task controlling the processor when processing data; and wherein the step of invoking the pipeline comprises the steps of: (f) requesting data from the last task by the host application, each task in turn requesting data from an upstream task to which it is linked; (g) obtaining data by the first task from a data source; (h) processing data obtained in step (g); (i) returning the processed data to the next downstream task in the pipeline; (j) processing the data in the downstream task; and (k) repeating steps (i) and (j) until the data is returned to the host application; wherein steps (f)-(k) are repeated for each data request by the host application. A method of creating and operating a data processing pipeline of linked data processing tasks in a single application processing environment that simulates a data processing pipeline of a multiprocessing environment, the data processing pipeline receiving data from a data source, processing the received data, and providing processed data to the host application, the method comprising the steps of: running a host application on a single application processor; creating a data processing pipeline of linked data processing tasks; and operating the data processing pipeline to provide processed data to the host application; wherein the step of creating the data processing pipeline comprises the steps of: instantiating a first data processing task for receiving data from a data source, processing the received data, and providing the processed data to one of a downstream task in the pipeline and the host application, determining if the data that will be provided by the first task requires additional processing before it can be used by the host application, and instantiating at least one additional data processing task for further processing the processed data provided by the first task when the processed data provided by the first task requires additional processing before it can be used by the host application, each at least one additional task being linked to at least one of an upstream task of the pipeline, a downstream task in the pipeline and the host application, the host application being linked to the last instantiated task, wherein the first data processing task and the at least one additional task are stored in a memory and each comprise: state defining means for defining the state of the task, at least one data processing channel, means for accessing a data processing function stored in a memory, and link means for linking the task to at least one of an upstream task in the pipeline, a downstream task in the pipeline and the host application; and wherein the step of operating the data processing pipeline comprises the steps of: requesting data from the last instantiated task by the host application, each task in the pipeline in turn requesting data from a next upstream task until the data request is received by the first task, receiving data from a data source in the first task, the first task providing data to one of a next downstream task in the pipeline and the host application, processing received data in at least one additional task, each at least one additional task providing processed data to one of a next downstream task in the pipeline and the host application when the at least one additional task has been instantiated, and receiving processed data at the host application from the last instantiated task: wherein each of the tasks of the pipeline control the single application processor to accomplish their data processing so that the data processing pipeline simulates a data processing pipeline of a multiprocessing environment. A control system for operating a single application processing computer to emulate a multi-application processing computer, comprising: a single application processing processor; a memory; a host application comprising a first control means for operating the processor; and a data processing pipeline comprising a plurality of linked pipeline sections stored in the memory, each pipeline section comprising second control means operating the processor, each pipeline section further comprising a plurality of data buffers, data defining a current state of the pipeline section, a process pointer for linking the pipeline section to another pipeline section, and data defining a processing operation; wherein, when the host application requests data from the data processing pipeline, the data request is passed up the pipeline from section to section until the data request is passed to a first pipeline section, the first pipeline section receiving data from a data source, processing the data, and providing the processed data to an adjacent downstream pipeline section, and wherein each of the intermediate pipeline sections processes the provided data and provides the processed data to the adjacent downstream pipeline section until the processed data is provided to the host application; wherein each pipeline section controls the processor to accomplish its data processing so that the single application processing computer simulates a multi-application processing computer; and wherein the host application creates the data processing pipeline before requesting data from the pipeline by instantiating data processing functions to form a plurality of linked pipeline sections. A control means for pipelined data processing in a single application processing environment, comprising: a memory; a single application processing processor; function library means for storing data processing functions; and a controller for controlling the processor, the controller comprising: memory management means for allocating and deallocating memory blocks of the memory; host application means for operating the processor in a single application environment; and a data processing pipeline, the pipeline comprising a first task means and at least one additional task means for operating the processor to process data, the pipeline obtaining data from the data source, processing the obtained data, and providing processed data to the host application means, one end of the pipeline being linked to the host application means; wherein the host application means comprises: instantiating means for creating the data processing pipeline by instantiating the data processing functions stored in the function library means to form the plurality of linked task means, each task means of the pipeline being stored in a memory block of the memory, and invoking means for invoking the data processing pipeline after the instantiating means has created the pipeline by requesting data from the task means of the pipeline linked to the host application means, each of the additional task means requesting data from an immediately upstream task of the pipeline until the request for data reaches the first task means of the pipeline, the first task means obtaining or generating data and passing the data to the immediately downstream task means, each of the additional task means processing the data and passing the processed data to an immediately downstream task means until the last task means processes the data and passes it to the host application means; and wherein each of the plurality of linked task means of the pipeline controls the processor to accomplish data processing and comprises: link means for linking at least two task means together, at least one channel means for passing data between linked task means, data processing means for processing data received via each at least one channel means, and task state means for controlling the task means; wherein the data processing pipeline is created by the host application means before the invoking means of the host application means invokes the data processing pipeline. The control means of claim 4, wherein the task means further comprises external port means for allowing external access to the task means. The control means of claim 4 or 5, wherein the task means further comprises data analyzing means for determining whether the data is suitable for processing by the task means. The control means of claim 6, wherein the task means further comprises reconfiguring means for reconfiguring the pipeline in response to a negative determination by the data analyzing means, the reconfiguring means preferably comprising means for instantiating additional functions stored in the function library means to form additional task means and inserting the additional task means into the pipeline so that the data received by each task means of the pipeline can be processed by the task means. The control means of claim 7, wherein the reconfiguring means initializes additional functions stored in the function library means to form additional task means and inserts the additional task means into the pipeline. The control means of any of claims 4 to 8, wherein a first task means (1) obtains data for the pipeline from an external data source, (2) generates data for the pipeline internally, and/or (3) obtains data for the pipeline from another pipeline. The control means of any of claims 4 to 9, wherein the data processing pipeline alternatively comprises a most downstream task means, a most upstream task means, and at least one intermediate task means, each of the task means operating the processor to process data, each of the task means being stored in the memory, and the invoking means is alternatively adapted for requesting data from the most downstream task means in the pipeline, each intermediate task means requesting data from an immediately upstream task means until the data request reaches the most upstream task means, the most upstream task means responding to the data request by obtaining or generating data and passing it to an immediately downstream task means, each intermediate task means processing data passed to it and passing the processed data to an immediately downstream task means until the most downstream task means passes the processed data to the host application; and wherein each task means further comprises: error code generating means for indicating whether the task means has successfully obtained and processed the data; and wherein the instantiating means instantiates a data processing pipeline before the invoking means invokes the data processing pipeline.

Inventors: VENABLE DENIS A, VENABLE, DENIS A.
Applicants: XEROX CORP, XEROX CORPORATION
Application year: 1994
Main classification: G06F9
IPC codes: G06F9, G06T1