The series of mini-guides is taken from the original "Data Communication and Synchronization for Cell BE Programmer's Guide and API Reference." The rest are from IBM developerWorks.
M I N I - G U I D E S
Introduction (SDK 3.0)
Overview of DaCS services functionality categories (resource reservation, process management, group management, remote memory, message passing, mailboxes, process synchronization, data synchronization, and error handling.
An overview (SDK 3.0)
Look at the API library services (functions and environment and the process management and resource sharing models) and how to build a basic application and how to use the PDT (Performance Debugging Tool) for traced libraries.
Reservation services (SDK 3.0)
Discover the hierarchical parent-child relationship topology of parents, children, and peers, focusing on the child-related APIs and their descriptions.
Process management (SDK 3.0)
How to start, stop, and monitor DaCS DE (DaCS Elements) processes; APIs and descriptions.
Group functions (SDK 3.0)
How to organize DaCS processes in groups so they can be treated as a single entity, including how to define and design groups, definitions for group owner and member functions and the process synchronization service function, and a scenario that demonstrates group usage.
Intro to data communications (SDK 3.0)
How the following five work together.
- details: rDMA (SDK 3.0)
The API that makes up the remote direct memory access services.
- details: rDMA block transfers (SDK 3.0)
A means to perform direct memory accesses to and from remote memory.
- details: rDMA list transfers (SDK 3.0)
Enable scatter/gather operations between non-contiguous regions of memory and one contiguous region of memory.
- details: Message passing services (SDK 3.0)
Two-way communications using the familiar send/recv model.
- details: Mailbox services (SDK 3.0)
A simple method of passing a single 32-bit unsigned word between processes.
Wait identifier management services (SDK 3.0)
Manage wait identifiers (WIDs) which are used to synchronize data communication.
Transfer completion routines (SDK 3.0)
The routines you can use to test the wait identifier to see if the communication operation has finished.
Locking primitives services (SDK 3.0)
Mutex (mutual exclusion primitive) management services and mutex locking services APIs and their descriptions.
DaCS Elements types (SDK 3.0)
Focus on the four DE types supported in DaCS.
Error handling (SDK 3.0)
Background on error handling, how to create and register the error handler, and error-handling APIs and their descriptions.
M I N I - G U I D E S > H Y B R I D X 8 6
Hybrid x86: Using DaCS on Cell/B.E.-x86 hybrid systems (SDK 3.0)
Description, installation and configuration, linking to libraries, affinities, building, running, and optimizing an application.
M I N I - G U I D E S > G L O S S A R I E S
Glossary: Error codes (SDK 3.0)
Error codes and descriptions.
Glossary: Trace events (SDK 3.0)
API and performance hooks and their descriptions.
A R T I C L E S / T U T O R I A L S
The little broadband engine that could: IDL is dead -- long live DaCS!
Tour the DaCS process model and explore general DaCS principles, including communication and memory access.
The little broadband engine that could: DaCS -- flexible and complex
Migrate and IDL program to DaCS.
The little broadband engine that could: Looking at some DaCS performance fine-tuning issues
Optimize DaCS performance for application ports.
The little broadband engine that could: Rendering fractals on the SPE
More on optimizing performance.
Fun with DaCS: Error handling
How to create and register a user error handler for use with DaCS.
C O D E S A M P L E S
Cell/B.E. SDK: Code sample directory
When SDK version 3.1 comes out, look here for DaCS samples.