[Bf-cycles] Apple OpenCL and Cycles

[Marcio Andrade]

Hi,

It is \blender\intern\cycles\device\device_opencl.cpp

I also had to change the maximum local workgroup size for execution. For 2-dimension workgroups, the Intel CPU accepts at most 1024 x 1, and blender was submiting a workgroup of 11 x 11 for kernel_ocl_tonemap, so I changed it to submit 128 x 1.

I could email the changes to you, if you like, in order to not pollute the list.

Regards,
migueletto



________________________________
De: Nazim Mer <nazim.mer at gmail.com>
Para: bf-cycles at blender.org 
Enviadas: Segunda-feira, 17 de Dezembro de 2012 15:53
Assunto: Re: [Bf-cycles] Apple OpenCL and Cycles


Hi,
Can you post the directory in which the  device_opencl.cpp file is contained in...(is this file the same among st all platforms)

as well as:
what the final file should look like once changes are made...

OR 
would enabling CPU based Opencl be a target for the official blender build " but certainly a good target for the next release."
i.e. Blender 2.65a....



On 17 December 2012 15:35, Ton Roosendaal <ton at blender.org> wrote:

Hi Marcio,
>
>Our OS X platform maintainer - Jens Verwiebe - reported similar good results.
>It hasn't been taken further yet... but certainly a good target for the next release.
>
>Could you upload your compiled blender.app for others to check?
>
>-Ton-
>
>------------------------------------------------------------------------
>Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
>Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>
>
>On 17 Dec, 2012, at 13:57, Marcio Andrade wrote:
>
>> Hello,
>>
>> I read that OpenCL development on Cycles is on hold, mainly because of compiler/driver problems in the AMD SDK. I have been doing some experiments with OpenCL on a Mac, and so far I did not encounter thouse kind of problems. After making some small changes to the kernel (basically enabling some defines that were commented out in kernel_types.h and fixing one compile error), I gave it a try.
>>
>> Compilation is fast and does not give memory errors. On my system the kernel is compiled in under 5 seconds. My Mac has a Intel HD 3000 GPU, which does not support OpenCL, so in order to make these tests I enabled OpenCL on the CPU (a small change to device_opencl.cpp). When I run the kernel in Blender, rendering time is close to the normal render using CPU, which is expected, since OpenCL Kernel on CPU should be close to the C++ Kernel on CPU.
>>
>> Apple is the original author of OpenCL, and OpenCL support on Macs seems to be pretty decent (no need to install anything, it is already bundled). So, is there anyone else trying Cycles/OpenCL on Apple hardware ? I would like to know how OpenCL performs on a Mac with a true GPU, to see if its worth pursuing this direction.
>>
>>
>> Regards,
>> migueletto
>>
>> _______________________________________________
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-cycles
>
>_______________________________________________
>Bf-cycles mailing list
>Bf-cycles at blender.org
>http://lists.blender.org/mailman/listinfo/bf-cycles
>

_______________________________________________
Bf-cycles mailing list
Bf-cycles at blender.org
http://lists.blender.org/mailman/listinfo/bf-cycles