On 08/24/2010 07:46 PM, Xavier Thomas wrote: > You might be interested in MiniCL used in the bullet physics library. > It permit to use OpenCL on CPU only. > > Thanks, but I have a question on MiniCL as I am not sure if this is suitable. IMO you need different code for CPU's and GPU's.
CPU optimization you minimize the number of loops. The total number of instructions, time should be minimized. GPU you balance the loops between the number of platforms, devices, nodes and cores. Sometimes it is better not to optimize any code on GPU's, but just play with the data in the KernelTasks. But we know that the same code on a CPU will perform very bad. Still I will look into the MiniCL library as I didn't heard about it. Jeroen. > 2010/8/24 Jeroen Bakker<[email protected]>: > >> Hi all >> >> I have been experimenting with OpenCL and are planning a basic framework >> to support it in Blender. >> >> main features are: >> * OpenCL is disabled by default, CPU fall-back must ALWAYS be >> available. OpenCL can be enabled with command-line parameter >> * Compiler directive to completely disable OpenCL in Blender. >> * Basic implementation to access and use GPU-devices >> * I am not targeting the blender-render, but other time-consuming >> processes (fluids, node systems etc) >> >> I think this matches the basic blender principles: >> * can work on standard home PC's >> * blender installation is unzipping an zip >> >> Are other people also busy with this subject? >> >> Best regards, >> Jeroen >> >> http://wiki.blender.org/index.php/User_talk:Jbakker >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> >> > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
