Jump to content

Talk:Reconfigurable computing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 82.46.67.130 (talk) at 17:54, 26 July 2007 (Problems with the Article). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The reason why one should not change reconfigurable computing to reconfigurable system is to understand what exactly reconfigurable computing addresses. To baseline; a computer system is defined as an organised collection of hardware and software components designed to manipulate data in a '''''''meaningful''''''' manner. An abstract way to model such computer systems is to use a method called computer system model (CSM). CSM is composed of three architecture types providing clear abstraction level views to a computer system. These architecture types are known as computer architecture (CA) which is everything to do with the CPU, implementation architecture (IA) which is everything to do with the platform and software architecture (SA) also known as system architecture and deals with the software domain of a computer system. Computer Architecture addresses the organisation and design of the CPU, a basic CPU is composed of two domains which are; Control Path and Data Path. However, these two domains are heavily influenced by the computational configuration adopted. There are two computation configurations which are; Temporal –compute in time and Spatial –compute in space. Examples of temporal solutions would be; Pentium, Opteron, Xeon, Itanium, Power and SPARC. And examples of spatial would be ASICs. Without delving deep into CPU design a short synopsis would be; CPUs that use a temporal configuration generally has a large control path over the data path. As an example the Itanium McKinley has a control path of ~71% and a data path of ~7.4% the remaining area is used for miscellaneous circuitry. Whereas an ASIC, the ideal spatial solution will use ~80% data path and 15% control path. Spatial solutions like ASICs offer greater performance/watt/cycle than there temporal solutions, which, temporal solutions counteract this by offering better application flexibility through programmability. Reconfigurable Computing (RC) introduces a third type of computation configuration which is a mix between temporal and spatial. How the blend of this mix is done depends on the innovation of the RC. As I described earlier computational configuration influences the CA’s control and data paths, and RC is a new form of computational configuration thus, RC is not a computer system it is in fact an architectural form of CA. Which means the best suited name is Reconfigurable Computing and not Reconfigurable System.

Terminology

I converted the terminology into a table and moved it into the near bottom. Having it as sections made it hard to get an overview of the article. BTW, this is the first time I've seen an article have a whole terminology listing, is it really needed or could we link to relevant terms instead? Henrik 20:33, 28 February 2006 (UTC)[reply]

Problems with the Article

1. The paper talks about "Estrin" hybrid computers. As far as I am aware this is not a commonly used term in reconfigurable computing. I would recommend it is not used unless anyone can provide proof that it is a current and widespread term.

2. Too much marketing material is reproduced here in relation to SRC and Mitrionics. There are a lot of players in this market, loads will die off and loads more will emerge. This article should be futureproofed by toning the down the constant references to current market players. It will also lessen the temptation for the market players themselves to increase the amount they're referred to in this article.

3. Only one author has ever used the term "Reconfigurable Computing Paradox", so it seems like it shouldn't be used here until it gains more currency in the greater research community.

Generally the article is not in a good shape. I think we need to start discussing a new plan for a total rewrite of this article.

82.46.67.130 17:53, 26 July 2007 (UTC)[reply]