Talk:Multithreading (computer architecture)/Archive 1

Archive 1

Unnamed section

Anno UK83.67.105.130 11:01, 2 October 2007 (UTC) i think that this should be merged as it would provide greater laerning potential as one document for cross refencing pourposes

MAMF: I see no point in combining the general and specific articles related to multi-threading. Having browsed most of the links I feel the current setup is better. A general high-level discussion article, with links for more depth when desired (and back should you start in an article with more detail than you want) —Preceding unsigned comment added by 83.160.178.134 (talk) 12:39, 13 June 2008 (UTC)

I agree indeed, but then this page needs to be revamped, as it was originally intended to only cover the Hardware multithreading, thus the previous name before the renaming. As of now, if somebody looks for software multithreading information, he will get very confused by what the page says which is specific to hardware multithreading. I'd suggest to move the detailed hardware material to a separate page, and link to there from here. Samuel Thibault Fri, 18 Sep 2009 13:47:17 +0200

"Execution times of a single-thread are not improved but can be degraded." I strongly doubt of this. If there is really only one thread, then it can use the whole computing power and caches for itself. When running two threads that do not share data, that's another story of course Samuel Thibault 16:27, 1 December 2008 (UTC)

That's the point the sentence is trying to make. Dyl (talk) 07:41, 28 December 2008 (UTC)

Then I'll clarify the sentence, because that's not what I understood from it. Samuel Thibault 13:44, 1 January 2009 (UTC) —Preceding unsigned comment added by SamuelThibault (talk • contribs)

Errr, no, looking at the list again, running two threads is the point of the previous item in the list: "Multiple threads can interfere with each other when sharing hardware resources such as caches or translation lookaside buffers (TLBs).", here "multiple threads" does not necessarily mean "multiple threads of the same process". —Preceding unsigned comment added by SamuelThibault (talk • contribs) 13:49, 1 January 2009 (UTC)

Mmm, I'm tempted to drop the reference to multithreaded cryptography. If we let that one in, then I'm afraid we'll get a big bunch of "multithreaded this" and "multithreaded that", as multithreading is potentially applied to any algorithm... Samuel Thibault 16:41, 22 Feb 2009 (UTC)

Multithreading vs SMT?

Can somebody explain the differences between this article and Simultaneous Multithreading? As these two articles are written now, it looks that overlap is huge, and it is tempting to merge this article into SMT (which is much more specific and universally recognizable term than 'Multithreading'). Ipsign (talk) 05:09, 11 October 2010 (UTC)

As this article is trying to explain, SMT is a sub-type of MT. As such, this article covers other types of MT. There are also errors in the Simultaneous multithreading article. I don't agree that SMT is a more widely recognized term. If anything, the Intel Marketing trademark 'Hyperthreading' is more widely recognized. Dyl (talk) 03:48, 12 October 2010 (UTC)

Hyperthreading is (arguably) one of SMT implementations, so I would argue they should belong to the same article (I dont care if it is named SMT or Hyperthreading). And when somebody searches for 'multithreading', I don't think they expect to see this article (more likely, it is about multithreading in software, which is currently under Thread (computer science)). In addition, most of material in current Multithreading article is completely unsourced. I will be arguing complete rewrite and/or merge on these grounds. Ipsign (talk) 14:03, 17 October 2010 (UTC)

You want to merge multithreading because it is completely unsourced? Where's the policy that mandates such action? Also, where would you merge this article too? Rilak (talk) 06:59, 29 October 2010 (UTC)

SMT is ability of a single processor to simultaneously dispatch instructions from more than one hardware thread context. Because there are two hardware threads per physical processor, additional instructions can run at the same time. The POWER5 processor is a superscalar processor that is optimized to read and run instructions in parallel. Simultaneous multi-threading allows you to take advantage of the superscalar nature of the POWER5 processor by scheduling two applications at the same time on the same processor. No single application can fully saturate the processor. Simultaneous multi-threading is a feature of the POWER5 processor and is available with shared processors.[Mohammed zakariya.pune] — Preceding unsigned comment added by 122.182.3.154 (talk) 11:52, 27 September 2011 (UTC)