// Don't know who created this page but I'd like to fill in the actual taxonomy (computer architecture class definitions),
// Don't know who created this page but I'd like to fill in the actual taxonomy (computer architecture class definitions),
// since I've recently returned to the field. Am hoping neutrality will speak for itself but both that and accuracy can be checked
// since I've recently returned to the field. Am hoping neutrality will speak for itself but both that and accuracy can be checked
Line 18:
Line 18:
The MIMD-Based Paradigms category subsumes systems in which a specific programming or execution paradigm is at least as fundamental
The MIMD-Based Paradigms category subsumes systems in which a specific programming or execution paradigm is at least as fundamental
to the architectural design as structural considerations are. Thus, the design of ''dataflow architectures'' and ''reduction machines'' is as much the product of supporting their distinctive execution paradigm as it is a product of connecting processors and memories in MIMD fashion. The category's subdivisions are defined by these paradigms.
to the architectural design as structural considerations are. Thus, the design of ''dataflow architectures'' and ''reduction machines'' is as much the product of supporting their distinctive execution paradigm as it is a product of connecting processors and memories in MIMD fashion. The category's subdivisions are defined by these paradigms.
:[[File:Vector toolbar with signature button.png|right]]When you leave messages, please remember to "sign" your name, by putting <nowiki>~~~~</nowiki> (four [[tilde]] signs) at the end. This will add your name, and the date and time. You can also do this by clicking the 'sign' button, pictured to the right.
:I've added the above.
:Please note, the most important thing - for all facts - is to give references, where the reader can check the facts.
:For the first two above, I'm assuming that all the facts can be checked in the "Flynn" reference 2? So I used that same reference.
:For the third part, for now, I was not sure.
:It's essential to give references, because of the core policy of [[WP:V|verifiability]], and to avoid any [[WP:OR|original research]] or [[WP:SYNTH|novel synthesis]], both of which are not appropriate for an encyclopaedia.
:So, in future, please make it very clear where each fact can be checked. If that means repeating the same reference many times, that's fine - but everything should have a footnote reference - otherwise it could be challenged and removed by other editors.
This is the talk page for discussing improvements to the Duncan's taxonomy article. This is not a forum for general discussion of the article's subject.
{{Request edit}}
// Don't know who created this page but I'd like to fill in the actual taxonomy (computer architecture class definitions),
// since I've recently returned to the field. Am hoping neutrality will speak for itself but both that and accuracy can be checked
// against the original article (ref#2).
// Please consider adding the definitions below for the three highest-level categories in the taxonomy.
// under heading "Synchronous Architectures"
This category includes all the parallel architectures that coordinate concurrent execution in lockstep fashion and do so via mechanisms such as global clocks, central control units or vector unit controllers. Further subdivision of this category is made primarily on the basis of the synchronization mechanism.
// under heading "MIMD" (Flynn has already been cited via ref#1)
Based on Flynn's Multiple-Instruction-Multiple-Data Streams terminology, this category spans a wide spectrum of architectures in which processors execute mutiple instruction sequences on (potentially) dissimilar data streams without strict synchronization. Although both instruction and data streams can be different for each processor, they need not be. Thus, MIMD architectures can run identical programs that are in various stages at any given time, run unique instruction and data streams on each processor or execute a combination of each these scenarios. This category is subdivided further primarily on the basis of memory organization.
// under heading "MIMD Paradigm" {a second pass can add the links to pages for each example}
The MIMD-Based Paradigms category subsumes systems in which a specific programming or execution paradigm is at least as fundamental
to the architectural design as structural considerations are. Thus, the design of dataflow architectures and reduction machines is as much the product of supporting their distinctive execution paradigm as it is a product of connecting processors and memories in MIMD fashion. The category's subdivisions are defined by these paradigms.
When you leave messages, please remember to "sign" your name, by putting ~~~~ (four tilde signs) at the end. This will add your name, and the date and time. You can also do this by clicking the 'sign' button, pictured to the right.
I've added the above.
Please note, the most important thing - for all facts - is to give references, where the reader can check the facts.
For the first two above, I'm assuming that all the facts can be checked in the "Flynn" reference 2? So I used that same reference.
For the third part, for now, I was not sure.
It's essential to give references, because of the core policy of verifiability, and to avoid any original research or novel synthesis, both of which are not appropriate for an encyclopaedia.
So, in future, please make it very clear where each fact can be checked. If that means repeating the same reference many times, that's fine - but everything should have a footnote reference - otherwise it could be challenged and removed by other editors.
