<?xml version="1.0"?>

 
<rss version="2.0">
<channel>
<title>IBM developerWorks : Power Architecture technology : Articles</title>
<link>http://www.ibm.com/developerworks/</link>
<description>The latest content from IBM developerWorks</description>
<pubDate>24 Nov 2009 19:55:14 +0000</pubDate>
<language>en</language>
<copyright>Copyright 2004 IBM Corporation.</copyright>
<image>
<title>developerWorks</title>
<url>http://www.ibm.com/developerworks/i/dwlogo-small.gif</url>
<link>http://www.ibm.com/developerworks/</link>
</image>

	<item>
		<title><![CDATA[The little broadband engine that could: Why is my scalar code so slow?]]></title> 
		<description><![CDATA[The SIMD-only architecture of the Cell Broadband Engine (Cell/B.E.)
      processor&apos;s Synergistic Processor Engine (SPE) is an architecture that has no scalar
      operations -- all operations are performed on 16-byte vectors. Design code that helps
      the Cell/B.E. compiler make efficient use of this architecture.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell3/index.html?ca=drs-]]></link> 
		<pubDate>07 Aug 2007 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: Mailboxes and interrupts]]></title> 
		<description><![CDATA[Meet two more means of communication between the SPE and the PPE -- mailboxes
    and signal notification.  Mailboxes are special-purpose registers, similar to the I/O
    registers used to communicate with peripheral devices on some systems, available on the SPEs and the PPE.  Signal notification registers are registers which can be read or written to by the PPE, but which the SPE can only read.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell2/index.html?ca=drs-]]></link> 
		<pubDate>03 Jul 2007 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: An introduction to using SPEs for Cell Broadband Engine development]]></title> 
		<description><![CDATA[In this first article in a series on Cell Broadband Engine (Cell/B.E.) development, Peter
      Seebach introduces the API used to run programs on SPEs, focusing specifically on
      loading code on an SPE and sending data to it for processing.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell1/index.html?ca=drs-]]></link> 
		<pubDate>05 Jun 2007 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: More on rendering fractals on the SPE]]></title> 
		<description><![CDATA[In the previous article in the series, you learned about the challenges
            of rendering fractals on the SPE.  That article focused on the SPEs copying their rendering results directly into the
            target data buffer. This article shows you how the fractal generator can be
            optimized further by taking advantage of the SPE&apos;s fondness for vector
            operations.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell10/index.html?ca=drs-]]></link> 
		<pubDate>29 Jul 2008 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: Rendering fractals on the SPE]]></title> 
		<description><![CDATA[In the previous article in the series, you learned some reasons why there
      were no appreciable performance gains when you migrated the
      fractal-rendering program from running on one SPE to running on multiple SPEs. This
      article is going to illuminate the
      challenge of rendering fractals on the SPE. The focus is on the SPEs copying their
      rendering results directly into the target data buffer.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell9/index.html?ca=drs-]]></link> 
		<pubDate>10 Jun 2008 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: Looking at some DaCS performance fine-tuning issues]]></title> 
		<description><![CDATA[In the previous article in the series, you migrated a fractal-rendering program from earlier in the
      series to run using the DaCS data library with no appreciable performance gains when
      going from running on one SPE to running on multiple SPEs. This article explores ways to optimize
      performance.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell8/index.html?ca=drs-]]></link> 
		<pubDate>20 May 2008 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: DaCS--flexible and complex]]></title> 
		<description><![CDATA[In an earlier article in this series, the author introduced a fractal-generation
      program built around the IDL interface that showcased the strength of IDL&apos;s 
      straightforward API. Executing the program was almost like calling a function and
      getting results. In this article (and using the same basic program), the author 
      demonstrates the Data Communication and Synchronization library&apos;s (DaCS) greater
      flexibility and the tradeoff:  additional complexity. With DaCS, it&apos;s possible to pass the fractal pattern in as an initial argument,
        then use buffers to pass data back and forth as they are processed. While this requires
        more design work, but it might actually be more efficient. This article also shows that DaCS allows
      for much more carefully tuned inputs and outputs.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell7/index.html?ca=drs-]]></link> 
		<pubDate>22 Apr 2008 04:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: IDL is dead--long live DaCS!]]></title> 
		<description><![CDATA[In SDK 3.0, the Data Communication and Synchronization library (DaCS)
      provides a sparkling substitute for IDL. DaCS is a set of services to aid the development
      of applications and application frameworks in a heterogeneous multi-tiered system.
      This article takes you on a tour of the DaCS process model and
      explores general DaCS principles, including communication and memory access.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell6/index.html?ca=drs-]]></link> 
		<pubDate>04 Mar 2008 05:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: Reviewing the newest little SDK that installs natively on PS3]]></title> 
		<description><![CDATA[Come along on a little train tour of the SDK for Multicore Acceleration 3.0
      to see what&apos;s different for developers and how you can make good use of the SDK,
      including native installation on PS3, support for FC7 and RHEL 5.1, enhanced compilers,
      Fortran and Ada support, BLAS, ALF, and DaCS--oh my!]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell5/index.html?ca=drs-]]></link> 
		<pubDate>19 Feb 2008 05:00:00 +0000</pubDate>               
	</item>

	<item>
		<title><![CDATA[The little broadband engine that could: Use multiple SPEs for a single task]]></title> 
		<description><![CDATA[Peter Seebach uses a simple, iterative-function fractal generator program to describe how to use multiple
    Synergistic Processor Engines (SPEs) to vectorize a single task using the job queue model.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/power/library/pa-tacklecell4/index.html?ca=drs-]]></link> 
		<pubDate>18 Sep 2007 04:00:00 +0000</pubDate>               
	</item>

</channel>
</rss>


