By: Moritz (better.delete@this.not.tell), April 20, 2011 9:24 am
Room: Moderated Discussions
Vincent Diepeveen (diep@xs4all.nl) on 4/20/11 wrote:
---------------------------
>Moritz (Better@not.tell) on 4/15/11 wrote:
>---------------------------
>Where AMD and Nvidia shut up to much about is the actual amount of resources they have to execute executions X.
>For example a conditional move is an instruction you can see from AMD's instruction
>set they have in abundance, but how many of the 4 units can execute this?
My understanding is that non of them can, conditionals or branching is not done by the execution-units.
>There is in the 6900 manual not even a diagram showing the 4 execution units, let
>alone what sort of instructions which unit can execute.
That is because they are all the same now.
>This is something that's very crucial to know for programmers. If you look at agner
>fog, he has measured some latencies on cpu's; there is nothing like that about gpu's.
because latency doesn't matter, the idea is that there is always something else to do.
>Yet they leak so fragmentaric, that it's not even remotely enough to write really
>fast code for a gpu right from scratch.
>Only trial and error brings that.
>Very simple question is for example how fast is a shift-right?
>Then there is an opencl compiler in between that can mess things up, in case of
>AMD; yet i pray it'll get slowly better.
I think they are at it. intel is at an advantage because they have the compiler know-how in-house.
I guess you are not supposed to think that much about the actual code. They tell you how big the memorys are and how wide the different levels of units are, the rest is up to the compiler. Therefore you should write your code on a high level of abstraction and not use tricks making assumptions. Just write "a /= 2;" instead of shifting and hope the compiler is that smart.
>What i really wonder about is the small amount of contract jobs i see where companies/organisations
>ask for capable gpu programmers.
maybe there are just not that many programs that would benefit. Also not every customer has a graphicscard that is supported and faster than a multicore CPU.
---------------------------
>Moritz (Better@not.tell) on 4/15/11 wrote:
>---------------------------
>Where AMD and Nvidia shut up to much about is the actual amount of resources they have to execute executions X.
>For example a conditional move is an instruction you can see from AMD's instruction
>set they have in abundance, but how many of the 4 units can execute this?
My understanding is that non of them can, conditionals or branching is not done by the execution-units.
>There is in the 6900 manual not even a diagram showing the 4 execution units, let
>alone what sort of instructions which unit can execute.
That is because they are all the same now.
>This is something that's very crucial to know for programmers. If you look at agner
>fog, he has measured some latencies on cpu's; there is nothing like that about gpu's.
because latency doesn't matter, the idea is that there is always something else to do.
>Yet they leak so fragmentaric, that it's not even remotely enough to write really
>fast code for a gpu right from scratch.
>Only trial and error brings that.
>Very simple question is for example how fast is a shift-right?
>Then there is an opencl compiler in between that can mess things up, in case of
>AMD; yet i pray it'll get slowly better.
I think they are at it. intel is at an advantage because they have the compiler know-how in-house.
I guess you are not supposed to think that much about the actual code. They tell you how big the memorys are and how wide the different levels of units are, the rest is up to the compiler. Therefore you should write your code on a high level of abstraction and not use tricks making assumptions. Just write "a /= 2;" instead of shifting and hope the compiler is that smart.
>What i really wonder about is the small amount of contract jobs i see where companies/organisations
>ask for capable gpu programmers.
maybe there are just not that many programs that would benefit. Also not every customer has a graphicscard that is supported and faster than a multicore CPU.
Topic | Posted By | Date |
---|---|---|
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/11 11:55 PM |
Graph is not red-green colorblind friendly (NT) | RatherNotSay | 2011/04/12 03:51 AM |
Fixed | David Kanter | 2011/04/12 08:46 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | James | 2011/04/12 12:30 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 02:51 PM |
Try HD6450 or HD6850 | EduardoS | 2011/04/12 03:31 PM |
Try HD6450 or HD6850 | David Kanter | 2011/04/13 10:25 AM |
Try HD6450 or HD6850 | EduardoS | 2011/04/13 03:20 PM |
of cause | Moritz | 2011/04/14 08:03 AM |
of cause | EduardoS | 2011/04/14 01:55 PM |
Barts = 5D | Moritz | 2011/04/14 09:26 PM |
Barts = 5D | Antti-Ville Tuunainen | 2011/04/15 12:38 AM |
Limiting fixed function units | Moritz | 2011/04/15 04:28 AM |
Limiting fixed function units | Vincent Diepeveen | 2011/04/20 02:38 AM |
lack of detail | Moritz | 2011/04/20 09:24 AM |
lack of detail | EduardoS | 2011/04/20 11:45 AM |
gpgpu | Vincent Diepeveen | 2011/04/16 02:10 AM |
gpgpu | EduardoS | 2011/04/17 12:31 PM |
gpgpu | Groo | 2011/04/17 12:58 PM |
gpgpu | EduardoS | 2011/04/17 01:08 PM |
gpgpu | Ian Ameline | 2011/04/18 03:55 PM |
gpgpu | Ping-Che Chen | 2011/04/19 12:59 AM |
GPU numerical compliance | Sylvain Collange | 2011/04/19 11:38 AM |
GPU numerical compliance | Vincent Diepeveen | 2011/04/20 02:17 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 02:02 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 04:41 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 05:52 AM |
gpgpu and core counts | none | 2011/04/20 07:05 AM |
gpgpu and core counts | EduardoS | 2011/04/20 11:36 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 10:16 AM |
gpgpu and core counts | EduardoS | 2011/04/20 11:34 AM |
gpgpu and core counts | Heikki Kultala | 2011/04/20 07:24 PM |
gpgpu and core counts | EduardoS | 2011/04/20 08:55 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 06:48 AM |
gpgpu and core counts | EduardoS | 2011/04/22 01:41 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/21 10:42 AM |
AMD Compute and Texture Fetch | Vincent Diepeveen | 2011/04/22 01:14 AM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 10:53 AM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 01:46 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 02:02 PM |
AMD Compute and Texture Fetch | EduardoS | 2011/04/22 02:18 PM |
AMD Compute and Texture Fetch | anon | 2011/04/22 03:30 PM |
AMD Compute and Texture Fetch | David Kanter | 2011/04/22 09:17 PM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/20 12:12 PM |
gpgpu and core counts | Heikki Kultala | 2011/04/21 10:23 AM |
gpgpu and core counts | Vincent Diepeveen | 2011/04/22 02:11 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 08:39 AM |
Keep the crazy politics out of this | Vincent Diepeveen | 2011/04/22 09:12 AM |
Keep the crazy politics out of this | David Kanter | 2011/04/22 10:44 AM |
gpgpu and core counts | Jouni Osmala | 2011/04/22 11:06 AM |
gpgpu | EduardoS | 2011/04/20 11:59 AM |
gpgpu | Vincent Diepeveen | 2011/04/20 12:37 PM |
gpgpu | EduardoS | 2011/04/20 05:27 PM |
gpgpu | Vincent Diepeveen | 2011/04/21 02:06 AM |
gpgpu | EduardoS | 2011/04/22 02:00 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | PiedPiper | 2011/04/12 10:05 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/12 10:42 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | MS | 2011/04/15 05:04 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/16 02:25 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | David Kanter | 2011/04/16 08:42 AM |
New Article: Predicting GPU Performance for AMD and Nvidia | Vincent Diepeveen | 2011/04/20 02:20 AM |
memory | Moritz | 2011/04/14 09:03 PM |
memory - more | Moritz | 2011/04/15 11:11 PM |
New Article: Predicting GPU Performance for AMD and Nvidia | Kevin G | 2011/04/14 11:30 AM |