Data does not need to be managed entirely by the PPE.
数据并不需要完全通过PPE进行管理。
Both the SPE and the PPE can initiate DMA transfers.
SPE和PPE都可以发起dma传输。
So you write to the inbox and read from the outbox if you are the PPE.
所以如果是PPE，就会写入到收件箱，读取自发件箱。
Our trusty compiler, built for generating PPC Linux binaries for the PPE.
可信赖的编译器，用来为ppe生成ppcLinux二进制程序。
The PPE depends on the SPEs to provide the bulk of the application performance.
PPE 需要依赖SPE来提供主要的应用程序性能。
On the PPE that isn't so bad, as the value is merely truncated or expanded.
在PPE上，这样做的结果并不太坏，因为值不过是被截断或扩充了而已。
Unlike the SPE, the PPE does not stall and wait for a value when it reads or writes.
与SPE不同，PPE在读写时并不会停下来等待值的出现。
Note that there are two communications with the PPE in this code fragment, not one!
请注意在这段代码中与PPE之间有两次通信，而不是一个！
The most significant difference between the SPE and PPE lies in how they access memory.
SPE与PPE之间最显著的差别在于访问内存的方法。
The mailboxes, even for the PPE, are named according to the perspective of the SPE.
邮箱（甚至那些用于PPE的邮箱）都是从 SPE 的角度定义的。
The first type of processor element, the PPE, contains a 64-bit Power Architecture core.
第一类处理器元素PPE包含64位PowerArchitecture内核。
Other channels are used to access virtual memory associated with a user context on the PPE.
其他通道用来访问与PPE上的用户上下文关联在一起的虚拟内存。
It actually requires that the main code be written so that the PPE manages the resources.
实际上，它要求编写主代码以便由PPE管理资源。
The API for offloading code to the SPEs is distributed as a code library for the PPE, libspe.
将代码提供给spe使用的API是作为PPE使用的一个代码库libspe进行分发的。
This series begins with an overview of the API used to communicate between the PPE and the SPEs.
本系列文章首先对PPE和SPE之间进行通信使用的API进行概要介绍。
For example, one PPE-side mailbox register appears as a write-only physical memory location.
例如，一个ppe端的邮箱寄存器会作为一个只写的物理内存位置出现。
This is done using mailboxes, special purpose registers available to the SPEs and to the PPE.
这是通过使用邮箱完成的，邮箱是SPE和PPE可以使用的一些专用寄存器。
It's instructive to understand what happens on the spe when the ppe is using the libspe2 API.
理解PPE在使用libspe2API时spe上究竟发生了什么是非常有益的。
Notice that in both the PPE and the SPE the struct was aligned to 16 bytes and padded to 16 bytes.
注意在PPE和SPE 中，这个结构被对齐为16字节，并填充成 16 个字节。
Remember, the first parameter to the function is the 64-bit address that was passed in from the PPE.
记住，到此函数的第一个参数是传递自ppe的64位地址。
You can get a patch to GCC to add a pipeline definition for the PPE so you can create optimized code.
您可以找到GCC的一个补丁，它用来添加ppe的流水线定义，这样就可以创建优化的代码。
This is a special tool that converts spe programs into an object file that can be linked into a PPE executable.
这是一个特殊工具，可以将SPE程序转换成一个能被链接进PPE可执行程序的对象文件。
I further tested this simple Pthread code on the PPE to see how it scales with an increasing number of threads.
我在PPE上进一步测试了这个简单的Pthread代码，以此了解随着线程数量的增加它的性能变化情况。
When the PPE writes a data word to that address, the SPU can read from its corresponding mailbox read channels.
当PPE将一个数据字写入这个地址时，SPU就可以从对应的邮箱读通道中读取这个数据字的内容。
A DMA request always involves moving data between the SPE local store and a virtual address space on the PPE side.
dma请求通常会涉及数据在SPE本地存储与ppe端虚拟地址空间之间进行移动。
If a serious error occurs, for example, an invalid opcode, the SPU is stopped and an interrupt is delivered to the ppe.
如果发生了一个非常严重的错误，例如一个无效的操作码，那么SPU就会停止，并向PPE发送一个中断。
For the SPE, it is simply a set of channels (a read channel and a write channel) to write 32-bit values to the PPE.
对于spe而言，邮箱就是一组信道集(包括写信道和读信道)，用来将32位值写到PPE。
Now I will look into PPE-controlled programs, and for that, I need to know how to get the PPE and the SPE to communicate.
现在，我要来看一下受ppe控制的程序，为此，我需要知道如何让PPE与SPE相互通信。
The next program I'll show you utilizes the MFC and the channel interface to do character conversions on data specified by the PPE.
我要展示的下一个程序使用了MFC和信道接口来在由PPE指定的数据上进行字符传输。
应用推荐