<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>mikeash.com pyblog/friday-qa-2010-04-02-opencl-basics.html comments</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>mikeash.com Recent Comments</description><lastBuildDate>Sun, 10 May 2026 04:33:54 GMT</lastBuildDate><generator>PyRSS2Gen-1.0.0</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Filip - 2011-10-24 12:50:03</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>Lets say you are calculating a huge set of numbers, how do you stop the kernel when the user says "no more, i am bored and want to quit, but not the app, only the calculating".
&lt;br /&gt;
&lt;br /&gt;Is that even possible in openCL ?</description><guid isPermaLink="true">7c70f419cbda3575f117213811146d2a</guid><pubDate>Mon, 24 Oct 2011 12:50:03 GMT</pubDate></item><item><title>pyth - 2010-04-06 08:56:14</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>For a in depth discussion on work sizes and work items check out the excellent opencl tutorial podcast over on macresearch: &lt;a href="http://www.macresearch.org/opencl"&gt;http://www.macresearch.org/opencl&lt;/a&gt;.
&lt;br /&gt;It explains what SMUGOpenCL does under the hood and more (probably more then you want to know...)  </description><guid isPermaLink="true">65d3bcad3df9db1048feefaf3ed11d0a</guid><pubDate>Tue, 06 Apr 2010 08:56:14 GMT</pubDate></item><item><title>Kyle Sluder - 2010-04-05 06:20:55</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>Wouldn't it be nice if we could hand off some LLVM byte code instead of just raw program text? I'm thinking this would be even more useful on the iPhone for pixel shaders, but even on the desktop for OpenCL it would be nice to have already performed the parsing and some static analysis.</description><guid isPermaLink="true">4af4e539b5003b1b67e0d23e1a92e824</guid><pubDate>Mon, 05 Apr 2010 06:20:55 GMT</pubDate></item><item><title>mikeash - 2010-04-03 00:27:35</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>You would not believe how many times I made that typo. Thanks for pointing out the one I missed.
&lt;br /&gt;
&lt;br /&gt;In answer to your question, that probably is not guaranteed. I didn't even think about that. You'd probably need to make the final results array use a larger data type in order to be safe.</description><guid isPermaLink="true">3fa13329d17b9fd67d8dfb839aee2dca</guid><pubDate>Sat, 03 Apr 2010 00:27:35 GMT</pubDate></item><item><title>natevw - 2010-04-02 17:56:52</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>A question, and a tip:
&lt;br /&gt;
&lt;br /&gt;Does OpenCL guarantee that setting a single byte in a shared array like your kernel does will be "thread" safe?
&lt;br /&gt;
&lt;br /&gt;During the SL seeds, Ian Ollman posted to the Developer Forums "Why you should vectorize and some tips to get started". Unfortunately, my ADC membership has since expired and it doesn't seem to have been converted to a tech note, but if you have access it could help you get more performance out of OpenCL.</description><guid isPermaLink="true">9763cd9302527b90bc6883763d3cd4d5</guid><pubDate>Fri, 02 Apr 2010 17:56:52 GMT</pubDate></item><item><title>natevw - 2010-04-02 16:41:06</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2010-04-02-opencl-basics.html#comments</link><description>I think you mean "SMUGOpenCL" in the second paragraph. Other than that, this comment is left intentionally useless because I haven't finished the article.</description><guid isPermaLink="true">a2721340bf3469c997d6f8e6a58ff8db</guid><pubDate>Fri, 02 Apr 2010 16:41:06 GMT</pubDate></item></channel></rss>
