Comments on: Swimming in OpenCL http://supermegaultragroovy.com/2009/11/12/swimming-in-opencl/ Chris Liscio's Boo-urns Log Thu, 08 Dec 2011 10:40:00 +0000 hourly 1 http://wordpress.org/?v=3.2 By: chris http://supermegaultragroovy.com/2009/11/12/swimming-in-opencl/comment-page-1/#comment-103093 chris Mon, 09 Aug 2010 17:52:42 +0000 http://www.supermegaultragroovy.com/blog/?p=515#comment-103093 <p>Ian: Yes! This is an oft-overlooked benefit of OpenCL, in my opinion.</p> <p>Thanks for the heads up on the float8 types—I'll have to try that. :)</p> <p>Can't wait to see AVX show up in a future Mac update. Seems like a great thing for me to hold out for… ;)</p> Ian: Yes! This is an oft-overlooked benefit of OpenCL, in my opinion.

Thanks for the heads up on the float8 types—I’ll have to try that. :)

Can’t wait to see AVX show up in a future Mac update. Seems like a great thing for me to hold out for… ;)

]]> By: Ian http://supermegaultragroovy.com/2009/11/12/swimming-in-opencl/comment-page-1/#comment-103090 Ian Mon, 09 Aug 2010 17:44:23 +0000 http://www.supermegaultragroovy.com/blog/?p=515#comment-103090 <p>One advantage of writing in the OpenCL vector types is that unlike SSE/AltiVec/... intrinsics, they are portable, meaning you can be up and running on new architectures with vectorized code in no time. You also get standard operators like +-/*&,etc.</p> <p>One tip: use larger vectors than the machine width where it make sense, like float8 or float16. You should see a small win (~10%) today due to better use of superscalar resources and what is in effect loop unrolling. However, in the future your code can better take advantage of bigger vector units, like AVX, without further modification by you. http://software.intel.com/en-us/avx/</p> One advantage of writing in the OpenCL vector types is that unlike SSE/AltiVec/… intrinsics, they are portable, meaning you can be up and running on new architectures with vectorized code in no time. You also get standard operators like +-/*&,etc.

One tip: use larger vectors than the machine width where it make sense, like float8 or float16. You should see a small win (~10%) today due to better use of superscalar resources and what is in effect loop unrolling. However, in the future your code can better take advantage of bigger vector units, like AVX, without further modification by you. http://software.intel.com/en-us/avx/

]]> By: ¿Hardware y software en la misma liga? | MuyLinux http://supermegaultragroovy.com/2009/11/12/swimming-in-opencl/comment-page-1/#comment-92234 ¿Hardware y software en la misma liga? | MuyLinux Mon, 29 Mar 2010 20:52:43 +0000 http://www.supermegaultragroovy.com/blog/?p=515#comment-92234 <p>[...] Imagínate que el periodista pudiera codificar muchas pistas de audio al mismo tiempo y más deprisa aún. ¿Para qué quiere un periodista codificar varias pistas de audio al mismo tiempo más deprisa? Muy sencillo, vamos a suponer que ha estado en 5 presentaciones de producto, 2 actos oficiales y 3 entrevistas a lo largo del día y lo tiene todo grabado en su grabadora o móvil. Cuando llegue a la oficina o a casa, quiere volcarlo a su PC, pero el formato en el que se ha grabado no es compatible (sí, os lo juro, siguen usándose formatos no compatibles ;) con su reproductor de audio del PC/portátil. Pues nada, echa mano del codificador de audio y pasa todas esas pistas de audio al formato que sea en segundos gracias a la GPGPU. Ya no hablamos de minutos, hablamos de segundos (incluso de MUY pocos segundos). [...]</p> [...] Imagínate que el periodista pudiera codificar muchas pistas de audio al mismo tiempo y más deprisa aún. ¿Para qué quiere un periodista codificar varias pistas de audio al mismo tiempo más deprisa? Muy sencillo, vamos a suponer que ha estado en 5 presentaciones de producto, 2 actos oficiales y 3 entrevistas a lo largo del día y lo tiene todo grabado en su grabadora o móvil. Cuando llegue a la oficina o a casa, quiere volcarlo a su PC, pero el formato en el que se ha grabado no es compatible (sí, os lo juro, siguen usándose formatos no compatibles ;) con su reproductor de audio del PC/portátil. Pues nada, echa mano del codificador de audio y pasa todas esas pistas de audio al formato que sea en segundos gracias a la GPGPU. Ya no hablamos de minutos, hablamos de segundos (incluso de MUY pocos segundos). [...]

]]> By: Flavien http://supermegaultragroovy.com/2009/11/12/swimming-in-opencl/comment-page-1/#comment-89490 Flavien Mon, 22 Feb 2010 22:33:43 +0000 http://www.supermegaultragroovy.com/blog/?p=515#comment-89490 <p>Hi, I'm also currently using the vDSP but would like to port my code on windows / linux… so doing a kind of OpenCL wrapper sounds good (even if yes… for now which system would support it ?) also as I read the few lines about your project, you are probably dealing with autocorrelation (for the pitch analysis ? or not ?) if so, you may also mathematically improve your problem by passing to the frequency domain in order to compute your autocorrelation and then go back to the time domain. (Now maybe you're not autocorrelating at all…)</p> Hi, I’m also currently using the vDSP but would like to port my code on windows / linux… so doing a kind of OpenCL wrapper sounds good (even if yes… for now which system would support it ?) also as I read the few lines about your project, you are probably dealing with autocorrelation (for the pitch analysis ? or not ?) if so, you may also mathematically improve your problem by passing to the frequency domain in order to compute your autocorrelation and then go back to the time domain. (Now maybe you’re not autocorrelating at all…)

]]> By: chris http://supermegaultragroovy.com/2009/11/12/swimming-in-opencl/comment-page-1/#comment-84585 chris Sat, 12 Dec 2009 14:55:20 +0000 http://www.supermegaultragroovy.com/blog/?p=515#comment-84585 <p>@godDLL I've got the wrapper separated into a framework now. Just gotta build a test app (or two) to distribute with it. I may just try and rewrite the Apple samples with my library, to make life easier…</p> @godDLL I’ve got the wrapper separated into a framework now. Just gotta build a test app (or two) to distribute with it. I may just try and rewrite the Apple samples with my library, to make life easier…

]]>