Download Power Hawk Series 600 Closely
Transcript
1 Chapter 1Introduction 1 1 1 Overview 1 This manual is a guide to the programming interfaces that are unique to closely-coupled single board computer (SBC) configurations. A closely-coupled configuration is one where there are multiple SBCs in the same VME backplane. The programming interfaces described in this book allow inter-process communication between processes that are resident on separate SBCs in a closely-coupled configuration. Many of these interfaces are designed to be compatible with the interfaces available for interprocess communication on a symmetric multi-processor. The Diskless Systems Administrator’s Guide is a companion to this manual and contains information on configuring, booting and administering closely-coupled configurations as well as other diskless configurations. The types of inter-process, inter-board communication mechanisms supported for transferring data include: Shared memory A shared memory region is resident in the physical memory of one SBC in the VMEbus. Other SBCs access that physical memory through configured VME master or VME slave windows. Once configured, access to shared memory is accomplished through either the shmat(2) family of system calls or via the mmap(2) system call in the same manner as access to shared memory regions which are strictly local to one SBC. Posix message queues These interfaces can be used to pass data between processes that are resident on separate SBCs on the same VMEbus. VME messages are used to pass data to and from a message queue. Storage space for the messages in the message queue is user-defined to be resident on one SBC in the VME cluster. VMEnet sockets Standard network protocols can be configured to operate on the VME backplane. The VMEbus is then utilized like any other network fabric. The standard socket(3) interfaces can be used to establish VMEnet connections between processes that are running on separate SBCs in the same VMEbus. 1-1