|
The Data Stream Page http://data-streams.org |
|
|
Reconfigurable Computing (RC) pages @ TU Kaiserslautern These Reconfigurable Computing pages are about a route to Reinvent Compting. This term is not new. See the keynote by Burton Smith (former Cray CTO).
Why Reinvent Compting?
Pse, study Thomas Sterling's interview entitled: 'I Think We Will
Never Reach Zettaflops'. See
HPCwire. Thomas Sterling takes us through
some of the most critical developments in high performance computing, explaining
why the transition to exascale is going to be very different than the ones in
the past. I agree. However, I believe, we will reach
Zetaflops --- by
Reconfigurable Computing.
|
|
|
to learn more about Datastreams: don't miss the RC education workshop ! |
|
|
|
Data-stream-based Computing
Computing sciences
distinguish
a dichotomy of basic computing paradigms: instruction-stream-based
computing
(von Neumann paradigm) versus data-stream-based
computing (anti
machine paradigm). For terminology see table 1.
Reconfigurable Computing goes into every application
|
| Search Google (for the number of hits see
the line "Web ... Results" ) |
Search Yahoo (for the number of hits see
the line "Search Results" ) |
| "Reconfigurable Computing" | FPGA & "oil and gas" | FPGA & "automotive" | FPGA & "medical" | FPGA & "chemical" | FPGA & "bio" | FPGA & "defense" | FPGA & "physics" | FPGA & "molecular" | FPGA & "supercomputing" | FPGA & "HPC" | FPGA & "high performance computing" | | "Reconfigurable Computing" | FPGA & "oil and gas" | <FPGA & "automotive" | FPGA & "medical" | FPGA & "chemical" | FPGA & "bio" | FPGA & "defense" | FPGA & "physics" | FPGA & "molecular" | FPGA & "supercomputing" | FPGA & "HPC" | FPGA & "high performance computing" | |
Why data-stream-based computing is going mainstreamData-stream-based
machines do
not have a von Neumann bottle neck and have much less overhead
phenomena than von Neumann machines. For data-intensive very high
performance
applications data-stream-based computing is the drastically
more
promising solution than von Neumann. This is the reason, why data-stream-.based
computing goes mainstream - additionally stimulated by the
break-through
of reconfigurable computing. Datastream-based
computing
is also a reason for the fast advance of embedded-memory-related
markets and R&D (see flowware page). Table no. 1: toward a consensus on basic terminology:
Acronyms: r = reconfigurable | FP = field-programmable | GA = gata array | DPU = DataPath Unit | DPA = DPU array | The von Neumann machine modelThe von Neumann machine is instruction-stream-based and uses a CPU which can sequence only a single instruction stream by means of a program counter. The CPU includes a datapath unit (DPU) and a single inctruction sequencer (see fig. 1). The memory of a von Neumann machine has no sequencers, since the memory addresses are delivered by the CPU.
The anti machine modelThe anti machine is
data-stream-based
and uses only a DPU, i. e. without a sequencer, or, a DPU
array (DPA) without sequencers (see fig. 1).
The
anti machine model locates sequencers as part of the memory.
State
register is the data counter, the address generator located within
memory (see left side of fig. 3). A
single
anti machine may have one or multiple data counters and may be
driven
by a single data stream or multiple data-streams (see left side
of fig.
3). For the anti machine the data streams have to be programmed to
determine, which data item has to meet which DPU port or DPA port at
which
time (fig. 2). Such data-stream-based program
sources
we call flowware, in contrast to traditional
instruction-stream-driven software.
No dataflow machineThe anti machine is
deterministic,
like also the von Neumann machine. The historic term "dataflow
machine",
however, has been used for an indeterministic machine, driven by an
arbiter,
so that the order of execution cannot be predicted. The anti machine is
no "dataflow machine".
Reconfigurable anti machineIn contrast to the
von
Neumann machine, anti machines also support reconfigurable data paths
(DPUs
or DPAs). Configuration may be considered to be a kind of "instruction
fetch" before run time (at configuration time), where such an
"instruction"
may be much more powerful than a typical on Neumann instruction. About
reconfigurability and Reconfigurable Computing see the morphware
page.
The dicholomy of machine paradigms: software versus flowwareFig. 4 compares both machine paradigms. Fig. 5 compares software programming languages versus flowware programming languages. There massive similarities, since the only difference is the use of a program counter versus a use of data counters, The only difference stems from the anti machine property which allows multiple data counters, so that flowware languages support more RT level parallelism than software languages..
configware | morphware | flowware | data.streams
|
||||||||||||||||||||||||||||
| Tweet #ReinventComputing |
|
| search Morphware with Google | Yahoo | BING | |
|
| search Flowware with Google | Yahoo | BING | |
|
| search Kress Array with Google | Yahoo | BING | | search Anti Machine with Google | Yahoo | BING | |
|
|
|
|
|