<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>koobe def: &#187; Computing</title>
	<atom:link href="http://koobe.net/category/computing/feed/" rel="self" type="application/rss+xml" />
	<link>http://koobe.net</link>
	<description>ebook, computation, academia, and intellectual property (un)tangled</description>
	<lastBuildDate>Fri, 18 Jun 2010 21:02:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>IBM tops Green500 list</title>
		<link>http://koobe.net/2009/07/ibm-tops-green500-list/</link>
		<comments>http://koobe.net/2009/07/ibm-tops-green500-list/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 15:04:19 +0000</pubDate>
		<dc:creator>Wayne</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[IBM]]></category>

		<guid isPermaLink="false">http://koobe.net/?p=331</guid>
		<description><![CDATA[In the latest Green500 supercomputer list published by Green500.org, 18 of 20 fastest supercomputers are powered by IBM. The most efficient cluster is the BladeCenter QS22 Cluster built with PowerXCell 8i 4.0 Ghz processor and Infiniband in University of Warsaw. Actually this cluster is not a computing monster provided the max performance is 18.57 TFLOPs [...]]]></description>
			<content:encoded><![CDATA[<p>In the latest Green500 supercomputer list published by <a href="http://green500.org/index.php">Green500.org</a>, 18 of 20 fastest supercomputers are powered by IBM. The most efficient cluster is the BladeCenter QS22 Cluster built with PowerXCell 8i 4.0 Ghz processor and Infiniband in University of Warsaw. Actually this cluster is not a computing monster provided the max performance is 18.57 TFLOPs which ranks 422 in the <a href="http://www.top500.org/">Top500</a> chart. But the total power consumption is merely 34.63 kW. This achieves an impressive performance/power ratio of 536.24 MFLOPS/W. </p>
]]></content:encoded>
			<wfw:commentRss>http://koobe.net/2009/07/ibm-tops-green500-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>800 TFLOP real-time ray tracing GPU emerges</title>
		<link>http://koobe.net/2009/07/800-tflop-real-time-ray-tracing-gpu-emerges/</link>
		<comments>http://koobe.net/2009/07/800-tflop-real-time-ray-tracing-gpu-emerges/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 12:26:10 +0000</pubDate>
		<dc:creator>Wayne</dc:creator>
				<category><![CDATA[Computing]]></category>

		<guid isPermaLink="false">http://koobe.net/?p=309</guid>
		<description><![CDATA[This 800 teraflop real-time ray tracing system, jointly developed by Toyota and Unisys, consists of 73-core chips and can fit into a desktop computer chassis. This monster GPU system is aimed at the auto industry for efficient prototype body designs and paint combinations. For your information, the NVIDIA Tesla desktop GPU system C1060 featuring 240 [...]]]></description>
			<content:encoded><![CDATA[<p>This 800 teraflop real-time ray tracing system, jointly developed by Toyota and Unisys, consists of 73-core chips and can fit into a desktop computer chassis. This monster GPU system is aimed at the auto industry for efficient prototype body designs and paint combinations. For your information, the NVIDIA Tesla desktop GPU system C1060 featuring 240 streaming processor cores delivers  about 1 TFlops of parallel computing in single precision floating point calculations. The high-end Tesla S1070 system with 4 GPUs (and each GPU is equipped with 240 streaming cores) reaches 4TFlops and 0.3TFlops in single precision and double precision calculations, respectively.</p>
]]></content:encoded>
			<wfw:commentRss>http://koobe.net/2009/07/800-tflop-real-time-ray-tracing-gpu-emerges/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PGI adds GPU support to compilers</title>
		<link>http://koobe.net/2009/07/pgi-adds-gpu-support-to-compilers/</link>
		<comments>http://koobe.net/2009/07/pgi-adds-gpu-support-to-compilers/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 12:47:20 +0000</pubDate>
		<dc:creator>Wayne</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[compiler]]></category>
		<category><![CDATA[GPGPU]]></category>
		<category><![CDATA[NVIDIA]]></category>
		<category><![CDATA[PGI]]></category>

		<guid isPermaLink="false">http://koobe.net/?p=304</guid>
		<description><![CDATA[The trend of distributing complicated and heavy computations to the GPU is fast developing. PGI now presents it new product line of C and Fortran compilers with the support of NVIDIA GPU for general purpose computing. The new compiler, PGI Release 9.0 includes the PGI Accelerator&#153 has been demonstrated at ICS &#8217;09 in Hamburg last [...]]]></description>
			<content:encoded><![CDATA[<p>The trend of distributing complicated and heavy computations to the GPU is fast developing. PGI now presents it new product line of C and Fortran compilers with the support of NVIDIA GPU for general purpose computing. The new compiler, PGI Release 9.0 includes the PGI Accelerator&#153 has been demonstrated at ICS &#8217;09 in Hamburg last week. </p>
<p>According to <a href="http://www.hpcwire.com/features/A-Trio-of-HPC-Offerings-Unveiled-at-ISC-49648192.html">HPCWire</a>, the new PGI&#8217;s compilers provide an more intuitive way of GPGPU programming by generating GPU code directly from the C or Fortran source code. The model used by PGI is based on directives that the programmer must insert into the source code at the appropriate spots. This is similar to OpenMP directives. For example,</p>
<p><code>SUBROUTINE SAXPY (A,X,Y,N)<br />
    INTEGER N<br />
    REAL A,X(N),Y(N)<br />
!$ACC REGION<br />
    DO I = 1, N<br />
       X(I) = A*X(I) + Y(I)<br />
    ENDDO<br />
 !$ACC END REGION<br />
 END</code></p>
<p>The loop inside <code>ACC REGION</code> will be parallelized by the compiler and the GPU code will be bundled into the binary file along with the general CPU code. Beneath the compilers, the CUDA C extension is employed as the low-level interface to the GPU. This will certainly push forward the application of GPGPU in more general scientific computing. Currently, as the CUDA cannot fully utilize the power of multi-GPU cores, the PGI Release 9 compiler only works with one specific GPU per application. PGI is also seeking possibilities to use AMD&#8217;s Stream platform, but will need a working OpenCL implementation for that purpose.</p>
<p>You can try out the Accelerator&#153 from <a href="http://www.pgroup.com/resources/accel.htm">http://www.pgroup.com/resources/accel.htm</a>. This feature is available at no charge until the end of 2009 for users with a working PGI Linux license.</p>
]]></content:encoded>
			<wfw:commentRss>http://koobe.net/2009/07/pgi-adds-gpu-support-to-compilers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>AMD unlikely to adopt CUDA from NVIDIA</title>
		<link>http://koobe.net/2009/07/amd-unlikely-to-adopt-cuda-from-nvidia/</link>
		<comments>http://koobe.net/2009/07/amd-unlikely-to-adopt-cuda-from-nvidia/#comments</comments>
		<pubDate>Sun, 05 Jul 2009 11:36:00 +0000</pubDate>
		<dc:creator>Wayne</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[GPGPU]]></category>

		<guid isPermaLink="false">http://koobe.net/?p=300</guid>
		<description><![CDATA[The CUDA, NVIDIA&#8217;s extension to C language for general purpose GPU (GPGPU) computation, is reported to be unlikely seen on its competitor&#8217;s product lines. It is not surprising to see that AMD drops the support for the CUDA as AMD has its own proprietary flavor of GPGPU, called Stream, although it is slightly lagged behind [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.nvidia.com/object/cuda_home.html">CUDA</a>, NVIDIA&#8217;s extension to C language for general purpose GPU (GPGPU) computation, is <a href="http://www.theinquirer.net/inquirer/news/1432307/amd-won-nvidia-cuda-run-gpus">reported</a> to be unlikely seen on its competitor&#8217;s product lines. It is not surprising to see that AMD drops the support for the CUDA as AMD has its own proprietary flavor of GPGPU, called <a href="http://www.amd.com/US/PRODUCTS/TECHNOLOGIES/STREAM-TECHNOLOGY/Pages/stream-technology.aspx">Stream</a>, although it is slightly lagged behind the CUDA technology. But now this is not important, as AMD claims that it is now focusing on a more general approach, i.e. the <a href="www.khronos.org/opencl/">OpenCL</a> standard proposed first by Apple Inc. The OpenCL supports a large variety of hardwares, and serves as a strong candidate for the heterogeneous CPU/GPU computation environment. </p>
]]></content:encoded>
			<wfw:commentRss>http://koobe.net/2009/07/amd-unlikely-to-adopt-cuda-from-nvidia/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
