NonStop S-Series Server Description Manual (G06.24+)

Contents
HP NonStop S-Series Server Description Manual—520331-003
x
Figures
Figure 7-2. Stack Frames Overlap and Grow to Lower Addresses 7-5
Figure 7-3. Gateways and To-RISC Shells Enable TNS Access to System
Library 7-7
Figure 7-4. A TNS Call to the System Library Is Directed Through the Shell
Map 7-9
Figure 7-5. syscall Exception or Address Error Exception Sets Privileged
State 7-11
Figure 7-6. Millicode Routines Switch Between Main and Privileged Stacks 7-13
Figure 7-7. Deliberate Invocation of Error Exception Triggers Privilege
Transition 7-15
Figure 7-8. Far Jump Tables Allow Calls to Cross Direct Jump Area
Boundaries 7-17
Figure 8-1. An Interrupt Can Interrupt a Process or Another Interrupt Handler 8-3
Figure 8-2. Interrupts Invoke Interrupt Handlers, Return to Interrupted Code 8-5
Figure 8-3. The Interrupt Stack Marker Saves RISC and TNS State 8-7
Figure 8-4. The System Interrupt Vector Transfers Control to Software 8-9
Figure 8-5. Some Interrupts Can Be Masked by Mask Register Bits 8-11
Figure 9-1. Interprocessor Communication Involves Multiple Levels of
Protocol 9-3
Figure 9-2. From Linker-Listener Perspective: One Request and One Reply 9-5
Figure 9-3. The Message System Uses Setup and Acknowledgments in
Messages 9-7
Figure 9-4. Message Data Is Transferred To and From Request and Reply
Buffers 9-9
Figure 9-5. Message Transfers Use Three Phases and Two Transfer
Methods 9-11
Figure 9-6. For Request With Short Data, Listener Pre-Pushes Data 9-13
Figure 9-7. For Request With Medium Data, Listener Post-Pulls Data to
Cache 9-15
Figure 9-8.
For Request With Long Data, Listener Post-Pulls Data to Its
Buffer 9-17
Figure 9-9. For All Read Requests, Listener Pre-Pushes Data in Reply
Phase 9-19
Figure 10-1. Application Initiates Storage I/O, Communications I/O Uses Ethernet or
ATM 10-3
Figure 10-2. ServerNet Hardware Bridges Controllers to I/O Software 10-5
Figure 10-3. Queues in Controllers for Storage, in Processor for
Communications 10-7
Figure 10-4. Alternative Storage I/O Models Provide Backward Compatibility 10-9
Figure 10-5. Module Driver Pushes Entries to Global Buffers 10-11
Figure 10-6. I/O Process Sends Command Descriptor Block to Controller 10-13