Channels ▼

Developer Reading List

, April 02, 2013 New books on Java, Erlang, Unit Testing, Windows and more.
  • E-mail
  • Print

Intel Xeon Phi Coprocessor High-Performance Programming

by Jim Jeffers and James Reinders

Intel coding evangelists Jim Jeffers and James Reinders have completed a new book on programming the Intel Xeon Phi Coprocessor — a topic on which we are currently running a tutorial series. The authors have spent much of the last two years educating customers about the prototype and preproduction Phi hardware, so they are uniquely experienced in software development for this new silicon. As a result, this book is the definitive programming reference for the 60+ core monster from Intel.

It starts off by reassuring the reader that much of the benefit of the new chip can be obtained using conventional parallel programming techniques (vectorization, OpenMP-style compiler directives, and so forth). The back half of the book gets into the programming that is more chip-specific. The first topics in these later chapters will be familiar to users of GPU products: reducing the latency of data transfers, optimal threading models, and the like.

Finally, the authors address Phi-only kinds of considerations, such as data locality on the processor, configuring the Phi in various imaginative ways, using the Phi in Linux clusters, and so on. The text is highly readable and interlaced with lots of code examples in C and Fortran.

My only reservation about the book is that it focuses almost entirely on writing green field code for the processor. And it relies heavily on technologies that Intel has long favored, namely OpenMP, Threading Building Blocks (TBB), and Cilk. I would have liked to see consideration given to running existing programs that use Boost threads, Pthreads, or Java threads; and discussion of what changes would need to be made for them to run well on the Phi.

But this is a small complaint, given the extensive and unique information about the processor that is presented here. This volume is certainly the definitive title on the subject and considerably more approachable than the technical literature Intel has released about the Phi. Highly recommended.

(Adrian Bridgwater contributed to this review.)






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.