Talk:Pipeline (computing)

message: There is a lot of duplication and insconsistency among pages related to filters and pipelines:
* Pipeline
* Pipeline (Unix)
* Filter (Unix)
* Pipes and filters
* pipe (computing)
* pipeline (Unix)
* ... more
I will try to condense these pages into a sensible set, if no one does it first.Jorge Stolfi 16:45, 3 Dec 2004 (UTC)
thread_title: Duplications and inconsistencies

message: I would prop suggest removing the assembly line analogy and replace it with a more detailed description of a pipeline in a computing context.
11:08, 5 October 2006 (UTC)
thread_title: Assembly line analogy

message: * As of 14:10, 12 December 2016 (UTC)
thread_title: Assembly code missing

message: Changed the description of software pipelines. It originally stated that these used the output stream of one process to feed the next process, and linked to the [process (computing)] article. The term 'operation' is a better description as a process is not necessarily what is being called, even if you can invoke an operation that requires a new process. In Unix it is often  just a simple operation that completes within the current shell process that is having its output redirected to the input of the next operation. Other software implementations might not even use 'processes', so the term operation provides a more generic/abstract idea with which to describe this. :) Theshowmecanuck (talk) 02:21, 28 January 2010 (UTC)
thread_title: Software pipelines

message: The "Design considerations" explanation doesn't make any sense. It seems to have tried to simplify pipelining to the point of either making unclear assumptions, or it doesn't understand how it works. Please fix.  — Preceding unsigned comment added by 75.72.74.25 (talk) 22:48, 23 December 2016 (UTC)
thread_title:  "Design considerations" is gooblygook 

message: I removed the following material because it was not clearly explained, seemed to be relevant only for some very specific pipelines, and had no supporting cictations.  Indeed it seems to be "original research".
: 4.1 Graphical tools To observe the scheduling of a pipeline (be it static or dynamic), reservation tables are used.
: 4.1.1 Reservation tableA reservation table for a linear or a static pipeline can be generated easily because data flow follows a linear stream as static pipeline performs a specific operation. But in case of dynamic pipeline or non-linear pipeline a non-linear pattern is followed so multiple reservation tables can be generated for different functions.
: The reservation table mainly displays the time space flow of data through the pipeline for a function. Different functions in a reservation table follow different paths.
--Jorge Stolfi (talk) 06:20, 14 May 2018 (UTC)
thread_title:  Removed "Graphical tools"  section 

message: As the authors of QtMips and QtRVSim educational simulators with pipeline and cache simulators we offer illustration graphics for the article under any license selected proposed by Wikipedia community. The template SVG  
The simulator allows to visualize real conditions and export it to vector PDF which can be transformed to SVG so some interesting situation documenting for example forwarding and stall after LW isntruction can be provided. See the situations on slide 34 or our B35APO Pipeling lecture. Online simulator version . Ppisa (talk) 09:33, 16 April 2022 (UTC)
thread_title:  Classical 5-stage Pipeline Graphics