No, apaerently Apple didn't do this all by themselves. What they did is work or a long time with Intel, nvidia, AMD and other before going to Kronos with their draft OpenCL spec in hand. They did the work in a small club.
I read only a light weight "technical overview" that had some code examples. I looks to me like the standard itself is small and there is not to much to argue about it it. All the work will be in implementing it. Writing an OpenCL run time system looks to me like a very majoir effort
Also while Applemight use a little of OpenCL in SL. I think before we see it widely used we will need for there to be some higher level libraries. It would a an almost no-brainer touse OpenCL to drive the physics in an OpenGL based game but first you'd have to re-write one of the common physics engines touse OpenCL. My gues is that uses will not see much from OpenCL untill after mid 2010.
I doubt it. The point of OpenCL and Grand Central is that you don't need Crossfire or SLI. These technologies are only useful for graphics rendering in games since games need to see a single combined GPU. GPGPU functions and OpenCL don't care if you have many slow GPUs or 1 big combined GPU. In fact, SLI and Crossfire would probably be detrimental because of wasted overhead. Instead, Grand Central will assign individual tasks to each separate GPU.Will Snow leopard support CrossFire and SLI?
Or even better Hybrid versions of each.
Is that tech overview public?
Has someone actually compared the syntax and implementation between OpenCL and CUDA. It'd be interesting if they really are closely related since I believe the guy that Apple hired to develop the OpenCL spec was actually a former ATI guy. Although, I guess OpenCL, CUDA, CTM, and DX11 would all be fairly closely related since they are running on similar graphics architectures and are doing similar things.Actually, OpenCL is mostly CUDA.
I don't see how nVidia producing a mobile chipset really has much effect on the Mac Pro. nVidia could only produce a mobile chipset now after having had to cajole a mobile FSB license from Intel. nVidia has tried to get a server FSB license to make a platform for Quadro, but Intel has steadfastly denied them. This isn't likely to change since the server market is a huge money maker and stability is also key so Intel wouldn't want to risk diluting anything.SLI is possible because Nvidia is now producing the chipsets for macs, we could easily see SLI in the new MacPro, wether it has anything to do with OpenCL though is unknown
GPGPU and OpenCL is only really effective in highly parallel, floating point tasks. Like encoding video. So we'll see it in all the media apps and the new Quicktime X. It won't likely help the GUI directly, although Apple could program some complicated but questionably useful physics effects. Like dropping stuff in the trash could make the can and the dock shake realistically.I believe that OpenCL will accelerate only specific tasks.
Though I am very curious to see what it will actually achieve, I am holding my fingers crossed for a 10% to 15% increase in OpenCL supported tasks.
I think it will be a respectable boost.
I wonder if OpenCL will be used by OS X to accelerate its GUI...![]()
I can't help but wonder, with all this potential extra and continual use of the graphics chip - won't the system run much hotter?
Sounds pretty impressive...!
I'd love to see an OpenCL app on an iPhone, purely out of interest as to what it could do.
AppleMatt
I can't help but wonder, with all this potential extra and continual use of the graphics chip - won't the system run much hotter?
Perhaps people are expecting the usual "standards" jockeying when Microsoft is involved in the process.
You'd be amazed at the progress we can make when we remove Microsoft from the equation.![]()
The question that comes to mind for me is whether the quality, stability, or reliability of the interface will have suffered from the tight schedule.
Excellent point.
Only for very computationally intensive applications that would make use of OpenCL. But then you'd get a corresponding increase in speed.
In general use, it shouldn't make a difference.
Actually, OpenCL is mostly CUDA.
And anyone who knows anything else knows that games aren't the primary purpose of OpenGL.
Well the idea is that for tasks that can be optimized for GPGPU, the GPU would be able to get them done faster than the CPU. So instead of the CPU working all out for half an hour, the GPU works all out for 5 minutes. If these are going to be tasks you were going to do anyways, then there is a net power savings. Of course, it may encourage more use of the GPU as more programs come up, but that's just progress.I'm just wondering if Photoshop, Final Cut Pro or 3D render apps start integrating with it closely, then surely the GPU will start to be pushed in the same way as when playing say a 3D game? We all know that the fans spin up.
Also, I think the new APIs are likely to inspire developers to come up with new more powerful apps which they may not have thought about before?
From what I can see, if they push the timing for the legal stuff, they can go a bit more open by SIGGRAPH Asia in December, leaving Apple a chance to talk about it within Snow Leopard at MWSF. Till the legal stuff is done, no demos or specs.