Content deleted Content added
m Maintain {{WPBS}} and vital articles: 1 WikiProject template. Create {{WPBS}}. Keep majority rating "Start" in {{WPBS}}. Tag: |
|||
| (5 intermediate revisions by 5 users not shown) | |||
Line 1:
{{WikiProject banner shell|class=Start|
{{
}}
==VU0==
Really? Is the part about the VU0 necessary? The VU0 was just a primitive form of SIMD instruction set, the low end MIPS CPU at the core of the Emotion engine wasn't even really designed with it in mind, Sony basically hacked something together by shoving two of the MIPS processors 64-bit FPU's together and creating some new instructions for processing packed SIMD instructions. If we're going to mention that though, why would we leave out the Xbox - as the Pentium 3 it came with had SSE3, which was purpose built and actually had superior SIMD capabilities to Sony's Frankenstein solution. I know that the concept of SIMD in processors may *sound* similar to what the PhysX processor is doing. But that's because the PhysX processor was pretty close to the concept of a modern GPU, which consists of like thousands of tiny cores that perform the same operation many many times. Usually floating point (GPU's have since added integer capabilities, but at the time they were all floating point).
The two concepts, that of a GPU/Physics processor and an SIMD instruction set, sound similar because they are both basically the same concept, SIMD. The GPU just takes the concept to the extreme, whereas even on modern AVX you can at best hope to operate on 8 different packed values at once, with the GPU your operating on thousands. The GPU cores are also usually a lot weaker individually. And AVX sits right next to the processor so of course it's ideal for mixing with general programming. Whereas it can be difficult for the GPU and CPU to communicate effectively over their lengthy bus.[[Special:Contributions/2601:140:8980:106F:8576:80E0:C309:7606|2601:140:8980:106F:8576:80E0:C309:7606]] ([[User talk:2601:140:8980:106F:8576:80E0:C309:7606|talk]]) 08:34, 5 May 2019 (UTC)
==Untitled==
Does anyone else think this comes off as an advertisment? Someone with more knowledge on the subject should probably provide a counter point...
:I removed the advertisement and cleaned it up a bit (it was a PPU and a CPU in the previous version :P).
Line 20 ⟶ 29:
The only thing you get is a cookie storm and tons of advertising. I suggest we drop that link.
: No objections received, link deleted.
== What is a PPU really? ==
Line 33 ⟶ 41:
:There was one different component: 'a processor to manage inter-processor transfers' - I can't see how this could be far off what you can do with SPU/PPU initiated DMA's on the Cell. The whole thing reminds me of the days of DSP accelerator chips. This appears to be an accelerator card marketted around one killer app. But the Devrel guy was quick to describe the cores as custom CPUs and NOT dsp's, when I mentioned that term. I mentioned how I'd always perceived game Physics more as an excercise in collision - parsing complex spatial datastructures - rather than FP, and he answered by describing how the specialized memory architecture helped this.
:I suppose they may have analyzed physics code and got their VLIW ISA & execution unit mix tuned exactly to that, wheras desktop CPU's will be based on running a range of common benchmarks & legacy apps..
:: I don't see anything specific in the ''processor design'' of a so called "Physics processing unit". IMO, the term either refers to the special use case of a [[Graphics processing unit]] (GPU)... and then this article should make this very clear, or it is simply more marketing bullshit (see '''[[buzzword bingo]]'''). <span style="text-shadow: 0.1em 0.1em 0.2em black">[[User:ScotXW]]</span><sup>[[User talk:ScotXW|t@lk]]</sup> 10:40, 10 June 2014 (UTC)
== Distributed Computing? ==
Line 43 ⟶ 52:
Yeah, someone want to change that?
==PPU in Rev==
| |||