Glossary
| Term | Description |
|---|---|
| 3U module | The 3U form factor is a well-established open standard for small passive-backplane systems. It was developed for use in VMEbus systems. Its size, 100mm x 160mm, was defined in the original VMEbus specification, IEEE 1014-1987 and complies with the IEEE 1101.1 mechanical specification. |
| 6U module | The 6U form factor is a well-established open standard for small passive-backplane systems. It was developed for use in VMEbus systems. Its size, 160mm x 233mm was defined in the original VMEbus specification, IEEE 1014-1987 and complies with the IEEE 1101.1 mechanical specification. |
| 8B/10B encoding | See “8-bit/10-bit Encoder per Lane” on page 706. |
| :: | See “IPv6 Address Documentation Convention” on page 154. |
| Abandon operation | See “Resync Operation” on page 499. |
| ABR | Adjusted Block Received. See “Terminology” on page 640. |
| Ack coalescing | See “Responder May Coalesce Acks for Sends or RDMA Writes” on page 385. |
| Ack, ghost | “Detecting Ghost Acks” on page 210. |
| Ack, window | See description of Window in Table 33-10 on page 949. |
| Acknowledge CP | Acknowledge Control Packet. See Table 30-1 on page 855. |
| Acknowledge Extended Transport Header (AETH) | See Figure 17-6 on page 369 and Table 17-3 on page 370. |
| AckReq bit | Acknowledge Request bit (BTH:AckReq). See “Ack Packet Scheduling” on page 435. |
| ActCount | Master SM's Activity Counter. See “Are You Alive?” on page 854. |
| ActDefer state | Link Layer Active Defer state. See “LinkActDefer State” on page 609. |
| Action | The specification uses the term Action one time and offers no definition. It appears to be referring to the mysterious Action method that a device's SMA acts upon. |
| Active state | Link Layer Active state. See “LinkActive State” on page 608. |
| Active/Active Model | See “Active Client to Active Client” on page 1112. |
| Active/Passive Model | See “Active Client to Passive Server” on page 1112. |
| actively managed chassis | See the description of chassis, actively managed in the glossary |
| Activity Counter | Master SM's Activity Counter. See “Are You Alive?” on page 854. |
| Address Handle | See “Address Handles” on page 526. |
| Address vector | See:
|
| Adjusted Blocks Received (ABR) | See the definition of ABR in the glossary. |
| Admin Data Area | See Table 33-1 on page 919 and Table 33-2 on page 920. |
| AETH | See the definition of Acknowledge Extended Transport Header in the glossary. |
| Affiliated Asynchronous Error | See “Affiliated Asynchronous Errors” on page 293. |
| Affiliated Asynchronous Event | See “Affiliated Asynchronous Events” on page 292. |
| Aggregatable Global Unicast Addresses | See “Unlimited Global Unicast Addresses (Travel the Globe!)” on page 148. |
| Alternate Path Response (APR) | See “APR (Alternate Path Response) MAD” on page 1107. |
| Alternate path | This is the alternate path between two QPs or EECs that is switched to when Automatic Path Migration is triggered. Refer to:
|
| APM | See “Automatic Path Migration” on page 575. |
| Application-specific Manager | See “General Services Managers” on page 167. |
| APR | See the definition of Alternate Path Response in the glossary. |
| Armed state | “Automatic Path Migration” on page 575. |
| Asynchronous Event Handler | See “Registering a Handler” on page 292. |
| Asynchronous event | See the definition of Affiliated Asynchronous Event in the glossary. |
| Atomic Ack packet | See “Atomic Operation Consists of a Request and Ack Packet” on page 96. |
| Atomic Compare and Swap If Equal operation | See “Atomic Compare and Swap If Equal Operation” on page 98. |
| Atomic Fetch and Add operation | See “Atomic Fetch and Add Operation” on page 97. |
| Atomic operation | See “Atomic RMW Operations” on page 94. |
| Atomic Request packet | See “Atomic Operation Consists of a Request and Ack Packet” on page 96. |
| AtomicAckETH | See “Atomic Acknowledge Packet Contents” on page 96 and Figure 17-11 on page 381. |
| AtomicETH | See “Request Packet Contains AtomicETH Field” on page 96 and Figure 17-10 on page 380. |
| Attribute ID | See Table 28-1 on page 783 and Table 28-2 on page 783. |
| Attribute | See “Definition of an Attribute” on page 26. |
| Automatic Path Migration (APM) | See “Automatic Path Migration” on page 575. |
| Auxiliary Power signal group | See “Chassis and Module” on page 989. |
| Base LID | See “Source Port's LID Address” on page 45 and “Assigning Port's Base LID Address” on page 137. |
| Base Transport Header (BTH) | See “Every Packet Contains a BTH” on page 15. Also see Figure 11-1 on page 206. |
| Baseboard Management Agent (BMA) | See Table 9-1 on page 170 and “Baseboard Management” on page 987. |
| Baseboard Management Key (B_Key) | See “Baseboard Management Key (B_Key)” on page 340. |
| Baseboard Manager (BM) | See “General Services Managers” on page 167 and “Baseboard Management” on page 987. |
| Beacon Sequence | Also referred to as TS1 (i.e., Training Sequence 1). Refer to “Link Training” on page 732 and Figure 26-30 on page 739. |
| Big-endian | The most-significant byte of a multi-byte data object is stored in the start memory location, and the successive lower bytes of the object are stored in successively higher memory locations. |
| Bind operation | See “Binding a Window To a Region” on page 310. |
| BTH | See the definition of Base Transport Header in the glossary. |
| Bulk-Power signal group | See “Chassis and Module” on page 989. |
| Byte Striping | See “Byte Striping” on page 703. |
| B_Key | See the definition of Baseboard Management Key in the glossary. |
| B_KeyLeasePeriod | See “Device Logic Detects Death of BM” on page 346. |
| B_KeyProtectBit | See “The Key Comparison” on page 343. |
| B_KeyViolations | See “Starting the Countdown and Handling a Timeout” on page 346. |
| CA | Channel Adapter. See “Some Preliminary Terminology” on page 10. |
| CapabilityMask | This is a 16-bit attribute element of the ClassPortInfo attribute. It indicates the capabilities of the general services management agent associated with this ClassPortInfo attribute.
|
| Channel Adapter (CA) | See the definition of CA in the glossary. |
| Channel Interface (CI) | The verb layer, the HCA driver, and the HCA interface (and, if present, the device ROM) are collectively referred to as the CI in the specification. |
| Channel | Short for communications channel. Refers to two QPs in two CAs used by two applications to send and receive messages to and from each other. |
| Chassis Management Entity (CME) | See “Chassis Baseboard Management Elements” on page 991. |
| Chassis, actively managed | See “Chassis Baseboard Management Elements” on page 991. The chassis' CME provides access to a module-specific GUID and physical slot information for every installed IBA module over the point to point IB-ML connecting the CME to each module. |
| Chassis, passively managed | A passively managed chassis provides access to each IBA module's ModuleInfo SEEPROM through a BM access to the BMA on each module and access to the each module's ChassisInfo SEEPROM through a BM access over the module's point-to-point IB-ML bus. Over its dedicated IB-ML link, each module permits access to its unique ChassisInfo SEEPROM that provides the ChassisGUID as well as the slot number the module is installed in. See Figure 34-4 on page 997. |
| ChassisInfo | See Table 34-1 on page 992. |
| CI | See the definition of Channel Interface in the glossary. |
| CL | See Credit Limit in “Terminology” on page 640. |
| Class Manager | See “Role of GSMs” on page 167. |
| Class | Refers to the type of general services class manager. |
| ClassPortInfo | Each MA within a device implements a ClassPortInfo attribute that indicates the capabilities of that MA. The presence of a ClassPortInfo attribute for an optional MA indicates that it is implemented in the device. |
| Client | See “Definition of Client and Server” on page 1110. |
| Client/Server Model | See “Active Client to Passive Server” on page 1112. |
| CM | Each CA implements a Communications Manager (CM) that handles connection establishment for RC, UC, and RD as well as the SIDR_REQ and SIDR_REP messages for discovering whether a specific service is supported on a remote CA through an UD QP. |
| CMA | Communications Management Agent. The CM and CMA are one and the same (see CM in the glossary). |
| CME | Chassis Management Entity. See “Chassis Baseboard Management Elements” on page 991. |
| CmpSwap | Compare and Swap If Equal atomic operation. See “Atomic Compare and Swap If Equal Operation” on page 98. |
| Coalescing Acks | See the description of Ack coalescing in the glossary. |
| Code violation error | See “Code Violation and Disparity Error Detection” on page 729. |
| COM symbol | Comma symbol. See “Character Boundary Sensing” on page 725. |
| Comma Symbol | See the description of COM symbol in the glossary. |
| Communications Channel | See the definition of Channel in the glossary. |
| Communications establishment | The exchange of messages between the CMs of two CAs for the purpose of establishing a communications channel between two QPs (and the applications that use them for communication with each other). |
| Communications Management Agent (CMA) | See the definition of CMA in the glossary. |
| Communications Manager (CM) | See the definition of CM in the glossary. |
| Completed Flushed In Error | This Status value in a CQE indicates that the corresponding WQE was flushed without being executed due to a fatal error in the message transfer associated with a WQE executed posted before this WQE. |
| Completion Queue (CQ) | As each WQE on a SQ or RQ completes, either successfully or due to an error, a message transfer completion notification in the form of a CQE is posted to CQ associated with that SQ or RQ. The CA then signals its driver, typically via an interrupt, that a CQE has been posted to that CQ. |
| Completion Queue Entry (CQE) | This is a message transfer completion notification posted to a SQ's or RQ's CQ upon completion of a message transfer. |
| ComponentMask | See “Background on the MAD's ComponentMask Field” on page 937. |
| Config.Debounce | See “Debounce Substate” on page 740. |
| Config.Idle | See “Idle Substate” on page 741. |
| Config.RcvrCfg | See “RcvrCfg Substate” on page 740. |
| Config.WaitRmt | See “WaitRmt Substate” on page 740. |
| Configuration state | See “Configuration State” on page 739. |
| Control Packet (CP), SM | See Table 30-1 on page 855. |
| CP | SM Control Packet. See Table 30-1 on page 855. |
| cPSN | Current PSN. See “Some Definitions” on page 366. |
| CQ | See the definition of Completion Queue in the glossary. |
| CQE | See the definition of Completion Queue Entry in the glossary. |
| CR | Credits. See “Terminology” on page 640. |
| CRC | Cyclic Redundancy Check. A number derived from, and stored or transmitted with, a block of data in order to detect corruption on the receiving end. By recalculating the CRC and comparing it to the value originally transmitted, the receiver can detect some types of transmission errors. |
| CRD | Current Running Disparity. See “Disparity” on page 709. |
| Credit Limit (CL) | See the definition of CL in the glossary. |
| Credits, Flow Control | See “Link-Level Flow Control” on page 637. |
| Current Running Disparity (CRD) | See the definition of CRD in the glossary. |
| D bit | Direction bit. See “Solution: Directed-Route SMP” on page 875. |
| D | Data character. See “Preparing 8-bit Character for Encode” on page 708. |
| Datagram ETH (DETH) | Included in every RD and UD packet. See Table 16-4 on page 332. |
| DefaultMulticastPrimaryPort | See “Multicast Packet Handling When Table Is Not Implemented” on page 675. |
| DefaultMulticast SecondaryPort | See “Multicast Packet Handling When Table Is Not Implemented” on page 675. |
| DefaultPort | See SwitchInfo.DefaultPort in “Random Forwarding Table (RFT)” on page 671. |
| DestQP | Destination QP. In any IBA packet, the BTH:DestQP field identifies the destination QP that the packet is to be delivered to. |
| DETH | See the definition of Datagram ETH in the glossary. |
| Device Management Agent (DMA) | See Table 9-1 on page 170. |
| Device Manager (DM) | See “Role of GSMs” on page 167. |
| DGID | Destination Global ID. The GRH:DGID address specifies either:
|
| Directed-Route SMP | See “Solution: Directed-Route SMP” on page 875. |
| Direction (D) bit | See the definition of D bit in the glossary. |
| Disable CP | SM Control Packet. See Table 30-1 on page 855. |
| Disabled state | See “Disabled State” on page 736. |
| Disconnect Reply (DREP) MAD | See “DREP (Disconnect Reply) MAD” on page 1095. |
| Disconnect Request (DREQ) MAD | See “DREQ (Disconnect Request) MAD” on page 1094. |
| Discover CP | SM Control Packet. See Table 30-1 on page 855. |
| Discovering state | See “Discovering State” on page 858. |
| Disparity error | See “Disparity” on page 709. |
| Disparity | See “Disparity” on page 709. |
| DLID | Destination Local ID. The LRH:DLID address specifies one of the following:
|
| DMA | Direct Memory Access. Refers to the ability of a device to directly access memory without the intercession of a system processor. |
| Down state | See “LinkDown State” on page 604. |
| DREP | See the definition of Disconnect Reply in the glossary. |
| DREQ | See the definition of Disconnect Request in the glossary. |
| Dual-Simplex | A communications channel that can perform transfers in both directions simultaneously. |
| Duplicate Ack | See “Effects of Retry on Requester and Responder” on page 393. |
| Duplicate packet | Due to a retry of a request packet that took a long time to reach the responder QP's RQ Logic, the responder QP's RQ Logic (or the responder EEC's Receive Logic) receives a duplicate request packet. Assuming that the QP's RQ Logic (or the EEC's Receive Logic) ultimately receives both copies of the request packet, it sends two copies of the response back to the requester QP's SQ Logic (or the requester EEC's Send Logic). |
| Duplicate PSN region |
|
| Dword | A group of four bytes aligned on an address divisible by four. An Intel term. |
| E | Error character. When the Physical Layer receives a character that is incorrectly coded (a code violation), it presents the character to the Link Layer with an 'E' indication. See Table 26-8 on page 698. |
| EBP | End Bad Packet delimiter (i.e., control character).
|
| Edit Modifier | See Table 33-1 on page 919 and Table 33-2 on page 920 and “SubnAdmConfig() Operation” on page 941. |
| EEC | End-to-End Context. Comprises one end of a RD RDC. An EEC in one CA is connected to an EEC in another CA, forming a RDC. |
| EECN | EEC Number. The 24-bit number assigned to an EEC by the Create EEC verb when it creates an EEC. |
| EGP | End Good Packet delimiter.
|
| Egress Port | The switch or router port through which a packet exits the switch or router. |
| Elastic Buffer | See “The Elastic Buffer's Role” on page 726. |
| Encapsulated IPv6 packet | An IPv6 (Internet Protocol Version 6) packet encapsulated within an IBA raw IPv6 packet. See “Raw IPv6 Datagrams” on page 543. |
| End delimiter | EBP or EGP control character at the end of a packet. |
| End of Bad Packet Delimiter (EBP) | See the definition of EBP in the glossary. |
| End of Good Packet Delimiter (EGP) | See the definition of EGP in the glossary. |
| End-to-End Context (EEC) | See the definition of EEC in the glossary. |
| End-to-End Flow Control credits | See “End-to-End Flow Control” on page 417. |
| Endnode | A CA port. |
| EndRID | End Record ID. Refer to Table 33-1 on page 919, Table 33-2 on page 920, and “Query by RID Range” on page 947. |
| Enumeration | Where used in the specification, refers to an instance of a multi-element item. An example would be an entry in the GUIDInfo attribute. |
| ePSN | Expected PSN. See “Responder QP's RQ Logic Request PSN Verification” on page 212. |
| Error state | Refers to the Error state of a QP or an EEC. See “Error State Operational Characteristics” on page 257. |
| Error, locally detected | An error detected by requester QP's or EEC's Send Logic. |
| Error, remotely detected | An error detected by the responder QP's or EEC's Receive Logic and reported back to the requester QP's or EEC's Send Logic in a Nak packet. |
| ETH | Extended Transport Header. One of the additional header fields that follows the BTH in a packet. Which ETH(s) follow the BTH is defined by the type of packet (as defined by the packet's BTH:Opcode; see Table 5-1 on page 81). |
| EUI-64 Address | See “Port's Default GUID Is Hardwired” on page 156. |
| Event forwarding | See “Event Subscription and Event Forwarding” on page 801. |
| Event Notification | See “Event Subscription and Event Forwarding” on page 801. |
| Extended Transport Header (ETH) | See the definition of ETH in the glossary. |
| Failover | Refers to the automatic migration of a communications channel between two QPs or EECs from one path to another. See “Automatic Path Migration” on page 575. |
| FCB | Flow Control Block. A FCB is 64-bytes in size and a data VL's available received buffer space is reported in FCBs. See “Link-Level Flow Control” on page 637. |
| FCCL | Flow Control Credit Limit. See “Space Availability Is Reported in FCPs” on page 638. |
| FCCRC | Flow Control packet's CRC field. |
| FCP | Flow Control Packet. See “Space Availability Is Reported in FCPs” on page 638. |
| FCTBS | Flow Control Total Blocks Sent. See “Space Availability Is Reported in FCPs” on page 638. |
| Flow Control Block (FCB) | See the definition of FCB in the glossary. |
| Flow Control Credit Limit (FCCL) | See the definition of FCCL in the glossary. |
| Flow Control Credits | Same as FCBs. |
| Flow Control Packet (FCP) | See the definition of FCP in the glossary. |
| Flow Control Total Blocks Sent (FCTBS) | See the definition of FCTBS in the glossary. |
| Flow Control | Refers one of two features:
|
| Flow Label | 20-bit GRH:FlowLabel field. When non-zero, indicates to routers that all packets with the same FlowLabel bound for the same destination must be delivered to the destination port in order. When zero, there's no importance placed on packet delivery order. |
| Flush error completion status | See the description of Completed Flushed In Error in the glossary. |
| Format Prefix (FP) | See “Unicast GID Address Format” on page 149. |
| Forwarding Table | See “Switch Performs Packet Forwarding” on page 662. |
| FP | See the description of Format Prefix in the glossary. |
| Fragment Flag | See “Reliable Multi-Packet Transaction Protocol” on page 949. In particular, Table 33-11 on page 951. |
| Free Resource Count | See “CQE Contents” on page 287. |
| Free Space (FS) | See “Assumptions” on page 642. |
| FS | See the description of Free Space in the glossary. |
| Full-duplex | Bi-directional, simultaneous communications. |
| Gather Buffer List | See the definition in Table 13-1 on page 263. |
| General Services Agent (GSA) | The entity within a device that the respective GSM communicates with in order to access and possibly manipulate the GSM-related attributes, permitting status checking and configuration of the device. |
| General Services Interface (GSI) | Each CA and router port and each switch's management port (port 0) implement QP1 as the GSI. GSMs send GMP request MADs to and receive GMP response MADs and Trap(Notice) MADs from the GSAs within a device through a port's GSI. |
| General Services Manager (GSM) | See “General Services Managers” on page 167. |
| General Services Management Packet (GMP) | MADs sent and received by GSMs to communication with the GSAs within devices for the purpose of accessing GSM-related attributes within the devices. |
| Get method | Used to read an attribute's contents. |
| GetResp | Response to a Get(attribute) or Set(attribute) request MAD. Returns the data read from the specified attribute. |
| GID | Global ID. 128-bit IPv6-compliant address of a port or a multicast group address. |
| GIDPrefix | A 64-bit element of the PortInfo attribute, the SM uses it to assign a subnet ID to a port. All CA and router ports, and each switch's management port (port 0), are assigned the same subnet ID. It forms the upper 64 bits of a port's 128-bit IPv6-compliant GID. The lower 64 bits are supplied by one of the port's assigned GUIDs. |
| Global ID (GID) | See the description of GID in the glossary. |
| Global Route Header (GRH) | The GRH immediately follows the LRH field in a packet and is present under the following circumstances:
|
| Globally Unique ID (GUID) | See “Port's GUID(s) Assignment” on page 156. |
| GMP | See the description of General Services Management Packet in the glossary. |
| GRH | See the description of Global Route Header in the glossary. |
| GSA | See the description of General Services Agent in the glossary. |
| GSI | See the description of General Services Interface in the glossary. |
| GSM | See the description of General Services Manager in the glossary. |
| GUID | See the description of Globally Unique ID in the glossary. |
| Handle | Used in a number of contexts:
|
| Handover CP | SM Control Packet. See Table 30-1 on page 855. |
| Hardware Management signal group | See “Chassis and Module” on page 989. |
| HCA | Host Channel Adapter. Interfaces a processor complex to the IBA fabric. |
| High-Priority Limit Counter | See “Detailed Description of VL Arbitration” on page 628. |
| High-Priority Table | See “Detailed Description of VL Arbitration” on page 628. |
| Hop Count | See “Solution: Directed-Route SMP” on page 875. |
| Hop Limit (HopLmt) | The GRH:HopLmt field defines the maximum number of routers a global packet is permitted to cross before it must be discarded. |
| Hop Pointer | See “Solution: Directed-Route SMP” on page 875. |
| HopLmt | Hop Limit. The GRH:HopLmt field defines the maximum number of routers a global packet is permitted to cross before it must be discarded. |
| Host Channel Adapter (HCA) | See the description of HCA in the glossary. |
| IB Module | InfiniBand module. See “Chassis and Module” on page 989. Also see “Module Baseboard Management Elements” on page 1001. |
| IB-ML, virtual | InfiniBand Management Link. Refer to the description of IB2MME in Table 34-5 on page 1004. |
| IB-ML | InfiniBand Management Link. IB-ML is a multi-drop, multi-master, two-wire serial bus that uses the SMBus 1.1-based data transfer and arbitration protocols [System Management Bus Specification, Revision 1.1, December 11, 1998; Copyright (c) 1996, 1997, 1998, Benchmarq Microelectronics Inc., Duracell Inc., Energizer Power Systems, Intel Corporation, Linear Technology Corporation, Maxim Integrated Products, Mitsubishi Electric Corporation, National Semiconductor Corporation, Toshiba Battery Co., Varta Batterie AG]. |
| IB | Abbreviation for InfiniBand. |
| IBA | Abbreviation for InfiniBand Architecture. |
| IBML2IB | IB-ML to InfiniBand Link bridge. |
| ICRC | Invariant CRC. See “Invariant CRC (ICRC)” on page 648. |
| Idle Sequence | See “Idle Sequence Description” on page 722. |
| IETF | Internet Engineering Task Force. Large, open international community of network designers, operators, vendors, and researchers concerned with the evaluation of the Internet architecture and the smooth operation of the Internet. |
| ImmDtETH | 32-bit ETH that contains the 32-bit immediate data value in the last or only request packet of a Send With Immediate or an RDMA Write With Immediate message transfer. See “Immediate Data Option” on page 85. |
| Immediate Data | See “Immediate Data Option” on page 85. |
| Inactive SM | See “Not-Active State” on page 869. |
| InformInfo | This attribute is used to issue an event notification subscription request to a GSM or to the SA. See “Event Subscription and Event Forwarding” on page 801. Also see “SA Methods” on page 924 |
| Ingress Port | The port on a router or a switch that receives a packet. |
| Init state | Depends on which of the following context it's used in:
|
| Initial Path Array | See “Solution: Directed-Route SMP” on page 875. |
| Initialize state | See the description of Init state in the glossary. |
| Inter-Packet Delay (IPD) | See “Static Rate Control” on page 589. |
| Inter-Subnet Transfer | A packet transfer from a CA port in one subnet to a CA port in another subnet. |
| Interface Check | See “SQE State Operational Characteristics” on page 255. |
| Internet Engineering Task Force (IETF) | See the description of IETF in the glossary. |
| Intra-Subnet Transfer | A packet transfer from a CA port in a subnet to a CA port in the same subnet. |
| Invariant CRC (ICRC) | Invariant CRC. See “Invariant CRC (ICRC)” on page 648. |
| IO Controller (IOC) | An IOU consists of one or more IOCs interfaced to the IBA fabric by a TCA. An IOC is an IO subsystem such as a mass storage controller. |
| IO Unit (IOU) | An IOU consists of one or more IOCs interfaced to the IBA fabric by a TCA. An IOC is an IO subsystem such as a mass storage controller. |
| IO Virtual Address (IOVA) | See “Use Register Physical Memory Region Verb Call” on page 307. |
| IOC | See the description of IO Controller in the glossary. |
| IOControllerProfile | DM attribute. See Table 37-6 on page 1127 and “IOControllerProfile Attribute” on page 1127. |
| IOU | See the description of IO Unit in the glossary. |
| IOUnitInfo | DM attribute. See Table 37-5 on page 1126 and “IOUnitInfo Attribute” on page 1126. |
| IOVA | See the description of IO Virtual Address in the glossary. |
| IPD | Inter-Packet Delay. See “Static Rate Control” on page 589. |
| IPv4 Address | Internet Protocol Version 4 address. See “IPv4 Addresses Too Limiting” on page 147. |
| IPv4 | Internet Protocol Version 4. See “IPv4 Addresses Too Limiting” on page 147. |
| IPv6 | Internet Protocol Version 6. See “IPv6 Addressing” on page 148. |
| IPVer | The BTH:IPVer field indicates the latest version of the Internet Protocol that the packet's format adheres to. Currently, the only valid value is 6 (Internet Protocol Version 6). |
| IsSM bit | See Table 28-8 on page 797. |
| IsSMDisabled bit | |
| IsTrapSupported | |
| K | Control character. See “Preparing 8-bit Character for Encode” on page 708. |
| KeepAlive packet | See “Reliable Multi-Packet Transaction Protocol” on page 949. |
| Kernel mode | A program must have the highest program privilege level (i.e., kernel mode privilege) to access other OS kernel mode programs. |
| Lane | Used in the following contexts:
|
| LAP | See “LAP (Load Alternate Path) MAD” on page 1104. |
| LFSR | Linear Feedback Shift Register. See “Idle Sequence Description” on page 722. |
| LID Mask Control (LMC) | See “Assigning LID Address Range to Port” on page 137. |
| LID-routed SMP | See “LID-Routed SMPs” on page 787. |
| LID | Local ID. The SM assigns a 16-bit subnet-unique local ID to each CA and router port and to each switch's switch management port (port 0). |
| Limit Sequence Number (LSN) | See “SQ Logic Can Use MSN to Complete WQEs” on page 429. |
| Limited send WQE | See “Limited WQEs” on page 425. |
| Linear Feedback Shift Register (LFSR) | See the description of LFSR in the glossary. |
| Linear Forwarding Table (LFT) | See “Linear Forwarding Table (LFT)” on page 669. |
| LinearFDBCap | Linear Forwarding Database Capacity. See “SwitchInfo Attribute” on page 819. |
| LinearFDBTop | Linear Forwarding Database Top. See “SwitchInfo Attribute” on page 819. |
| Link Layer | Refer to “Link Layer Overview” on page 119 and “Detailed Description of the Link Layer” on page 599. |
| Link Management Packets | See “Link-Level Flow Control” on page 637. |
| Link Next Header (LNH) | See “LNH Field” on page 612. |
| Link packet | See “Link-Level Flow Control” on page 637. |
| Link training | See “Link Training” on page 732. |
| Link-Local Address | Meaning depends on context:
|
| Link | The physical link that connects two ports directly together. |
| LinkActDefer state | See “LinkActDefer State” on page 609. |
| LinkActive state | See “LinkActive State” on page 608. |
| LinkArm state | See “LinkArm State” on page 606. |
| LinkDown state | See “LinkDown State” on page 604. |
| LinkDownDefault | See “SM Can Specify Default Link Down State” on page 735. |
| LinkDownedCounter | See “Major Error Handling” on page 753. |
| LinkErrorRecoveryCounter | See “Major Error Handling” on page 753. |
| LinkInitialize state | See “LinkInitialize State” on page 605. |
| LinkInitRetraining | See “Other Link Layer to Physical Layer Interface Signals” on page 699. |
| LinkPhyReset | See “Other Link Layer to Physical Layer Interface Signals” on page 699. |
| LinkSpeedEnabled | See “Link Training Detail” on page 749. |
| LinkSpeedSupported | See “Solution” on page 591. |
| LinkUp state | See “LinkUp State” on page 743. |
| LinkWidthEnabled | See “Link Training Detail” on page 749. |
| LinkWidthSupported | See “Solution” on page 591. |
| Little-endian | The least-significant byte of a multi-byte data object is stored in the start memory location, and the subsequent bytes of the object are stored in successively higher memory locations. |
| LMC | LID Mask Control. See “Assigning LID Address Range to Port” on page 137. |
| LNH | Link Next Header (LRH:LNH). See “LNH Field” on page 612. |
| Load Alternate Path (LAP) | See “LAP (Load Alternate Path) MAD” on page 1104. |
| Local Ack Timeout | See “Ack Receipt Timeout (Local Ack Timeout)” on page 44. |
| Local ID (LID) | Local ID. The SM assigns a 16-bit subnet-unique local ID to each CA and router port and to each switch's switch management port (port 0). |
| Local access Key (L_Key) | See “Creating a Virtual Region” on page 300. |
| Local Route Header (LRH) | This is the first field in every data packet. It contains the subfields described in “Detailed Description of LRH” on page 610, and its purpose is to get the request packet to the destination CA or router port in the local subnet. |
| Locally detected error | An error detected by requester QP's or EEC's SQ Logic. |
| Low-Priority Table | See “Detailed Description of VL Arbitration” on page 628. |
| LRH | See the description of Local Route Header in the glossary. |
| LSN | Limit Sequence Number. See “SQ Logic Can Use MSN to Complete WQEs” on page 429. |
| LVer | Link Version (LRH:LVer). See “LVer Field” on page 612. |
| L_Key | Local access Key. See “Creating a Virtual Region” on page 300. |
| MAD header, base | Management Datagram base header. See Table 28-1 on page 783 and Table 28-2 on page 783. |
| MAD header | Management Datagram header. See Table 28-1 on page 783. |
| MAD | Management Datagram. See “Managers Use Special Packets Called MADs” on page 27. Also see “Detailed Description of MADs” on page 779. |
| Management Datagram (MAD) | See the description of MAD in the glossary. |
| Management Key (M_Key) | See “Management Key (M_Key)” on page 324. |
| Management Port | Refers to port 0 on a switch (the switch's management port). |
| Master SM | Master Subnet Manager. See “Master State” on page 861. |
| Master state | Refers to a SM in the Master state. See “Master State” on page 861. |
| MasterSMLID | Master Subnet Manager LID address attribute element. The Master SM programs the PortInfo.MasterSMLID attribute element of every CA and router port and the switch management port (port 0) with the LID address of the port it resides behind. This enables the port to send a SubnTrap(Notice) SMP to notify the SM when a device event of interest to the SM occurs. |
| Maximum Static Rate | See “Static Rate Control” on page 589. |
| Maximum Transfer Unit (MTU) | See “Maximum Data Payload Size” on page 42. |
| Memory Bind operation | See “Memory Windows” on page 308. |
| Memory region handle | Returned by any of the verbs that are used to create a virtual or physical memory region and used as an input parameter when calling any of the region manipulation verbs or memory window-related verbs. |
| Message method | The Method field in a MAD defines the action to be performed on an attribute by the MA that receives the request MAD packet. |
| Message Receipt Acknowledgement (MRA) | See “MRA (Message Receipt Acknowledgment) MAD” on page 1096. |
| Message Sequence Error (MSN) | See “SQ Logic Can Use MSN to Complete WQEs” on page 429. |
| Message | Refers to the complete data message to be transferred from one CA's memory to another CA's memory in a message transfer operation. If the message size exceeds a packet's PMTU, the message is segmented into a multi-packet transfer by the QP's SQ Logic. |
| Method | See the description of Message method in the glossary. |
| Methods, class-specific | This is a method defined for use by a specific class manager when acting upon a class-specific attribute. |
| Methods, common | This is a method defined for use by many, but not necessarily all, class managers when acting upon a class-specific attribute. |
| Migation, Automatic Path | See “Automatic Path Migration” on page 575. |
| Migrated state | This is the default state of a QP's or EEC's Migration state machine after power-up. Software sets up a QP or EEC for APM by transitioning it to the ReArm state. The QP or EEC then automatically transitions to the Armed state when it receives any packet from its companion QP or EEC with the BTH:MigReq bit = 0. Software can then trigger a migration to the alternate path by changing the state of its local QP or EEC from Armed to Migrated. Alternatively, an automatic path migration is triggered when a QP's or EEC's Send Logic has exhausted its Retry Count. In that case, the QP or EEC automatically transitions from the Armed to the Migrated state. |
| MigReq bit | The BTH:MigReq bit is used by the QP or EEC sending a packet to request that the remote QP or EEC migrate to the alternate path. See “Automatic Path Migration” on page 575. |
| MME | Module Management Entity. See “Chassis Baseboard Management Elements” on page 991. |
| Module carrier | See “Module Basics” on page 682. |
| Module Management Entity (MME) | See “Chassis Baseboard Management Elements” on page 991. |
| Module, IB | InfiniBand module. See “Module Basics” on page 682. |
| ModuleInfo | Module Information SEEPROM. See Table 34-2 on page 998. |
| MRA | See “MRA (Message Receipt Acknowledgment) MAD” on page 1096. |
| MSN | Message Sequence Number. See “SQ Logic Can Use MSN to Complete WQEs” on page 429. |
| MTU | Maximum Transfer Unit. See “Maximum Data Payload Size” on page 42. |
| MTUCap | Maximum Transfer Unit Capacity. See “MTUCap and NeighborMTU” on page 614. |
| Multicast Address | See:
|
| Multicast Forwarding Table (MFT) | See “Switch Multicast Packet Forwarding” on page 675. |
| Multicast Group | Same as a multicast GID address.
|
| Multicast LID | See “LID Address Space” on page 133 and “Multicasting” on page 563. |
| MulticastFDBCap | Multicast Forwarding Database (same as MFT) Capacity. See “Multicast Forwarding Table Is Optional” on page 675. |
| MulticastForwardingTable (MFT) | MFT attribute. See “Switch Multicast Packet Forwarding” on page 675. |
| Multipathing |
|
| M_Key | See “Management Key (M_Key)” on page 324. |
| M_KeyLeasePeriod | See “Management Key (M_Key)” on page 324. |
| M_KeyProtectBits | See “Management Key (M_Key)” on page 324. |
| Nak code | When the RQ Logic of a RC QP or the Receive Logic of a RD EEC returns an error code, it returns a Nak error code embedded in the Syndrome field of the AETH. See:
|
| Nak packet (or Negative Acknowledge Packet) | See the description of Nak code in the glossary. |
| Implied Sequence Error Nak | Refer to “Response Packet Lost” on page 399. |
| Nak-Invalid RD Request | See “One Additional Nak Type Defined” on page 473. |
| Nak-Invalid Request | See “Invalid Request Nak” on page 404. |
| Nak-Remote Access Error | See “Remote Access Error Nak” on page 403. |
| Nak-Remote Operational Error | See “Remote Operational Error Nak” on page 407. |
| Nak-RNR | See “Receiver Not Ready (RNR) Nak” on page 408. |
| Nak-PSN Sequence Error | See “PSN Sequence Error Nak” on page 401. |
| NeighborMTU | See “MTUCap and NeighborMTU” on page 614. |
| Network Layer | See “Network Layer Overview” on page 124. |
| Next Header (NxtHdr) | See “Raw IPv6 Datagram Format” on page 543. |
| Next Packet (NP) | See “Terminology” on page 640. |
| NodeInfo attribute | Device information attribute. See “NodeInfo Attribute” on page 816. |
| Not-Active state | SM Not-Active state. See “Not-Active State” on page 869. |
| Notice Queue (NQ) | See “The Notice Queue” on page 806. |
| Notice | Device MAs log notifications of internally detected events in the Notice attribute. The Notice attribute is either automatically delivered to the respective manager in a Trap(Notice) MAD (if traps are enabled) or it can be read by the respective manager using the Get(Notice) method. |
| NoticeCount | See “The Notice Queue” on page 806. |
| NoticeToggle | See “The Notice Queue” on page 806. |
| NP | Next Packet. See “Terminology” on page 640. |
| nPSN | Next Packet Sequence Number. See “Some Definitions” on page 366. |
| NQ | Notice Queue. See “The Notice Queue” on page 806. |
| NRZ encoding | Non-Return to Zero encoding. |
| NV memory | Non-volatile memory. |
| NxtHdr | See “Raw IPv6 Datagram Format” on page 543. |
| Opcode | The BTH:Opcode field defines the type of packet. |
| OperationalVLs | See “VLCap and OperationalVLs” on page 620. |
| OptionMask | See “Optional Features” on page 1021. |
| Packet Sequence Number (PSN) | Self-explanatory. Each packet contains its Packet Sequence Number in the BTH:PSN field. |
| PAD Symbol | See “12x Packet Format Rules” on page 721. |
| Page | The processor's memory management unit (MMU) defines physical memory and virtual memory as being divided into pages of memory space. When the currently executing processor instruction requires a memory access or the processor must fetch an instruction from memory, the processor's MMU uses the virtual memory address to perform a lookup in its page directory table(s) to determine whether the physical memory page corresponding to the addressed virtual memory page is currently in physical memory. If it is, the MMU translates the virtual memory address into the correct physical memory address and accesses the targeted data or instruction. If it isn't in physical memory right now, the MMU experiences a page fault exception, causing the processor to jump to the OS kernel's memory management facility. The OS fetches the desired page of information from mass storage, places it into an available page of physical memory, and creates a page directory entry mapping the virtual page start address to the actual start address of the page in physical memory. Now that the page is in memory, the processor re-executes the instruction that caused the page fault, but this time the directory lookup and subsequent page address translation succeeds, and the desired data or instruction is fetched from memory. The page size is processor design-specific. The most typical page size is 4KB, but most of today's processors have a programmable page size. |
| Partition Key (P_Key) | See “Partition Key (P_Key)” on page 319. |
| Partition Manager (PM) | See “Partition Key (P_Key)” on page 319. |
| Partition membership, full | See “P_Key Format and the Membership Types” on page 321. |
| Partition membership, limited | See “P_Key Format and the Membership Types” on page 321. |
| PartitionEnforcementCap | See “A Port Can Be a Member of Multiple Partitions” on page 319. |
| PartitionEnforcement Inbound | See “Inbound and Outbound P_Key Checking” on page 838. |
| PartitionEnforcement Outbound | See “Inbound and Outbound P_Key Checking” on page 838. |
| passively managed chassis | See the description of chassis, passively managed in the glossary. |
| Path Maximum Transfer Unit (PMTU) | See “Maximum Data Payload Size” on page 42. |
| PathRecord | See “PathRecord” on page 975. |
| PayLen | GRH:PayLen. Payload length.
|
| Payload Length | See the description of PayLen in the glossary. |
| PD | Protection Domain. See:
|
| Peer-to-Peer Model | See “Active Client to Active Client” on page 1112. |
| Performance Management Agent (PMA) | See “The Role of Performance Management (PM)” on page 1020. |
| Performance Manager (PM) | See “The Role of Performance Management (PM)” on page 1020. |
| Permissive LID (PLID) | See “Solution: Directed-Route SMP” on page 875. |
| PhyLinkStat | Physical Link Status signal. See “Physical Layer/Link Layer Interface” on page 654. |
| Physical Layer | See:
|
| Physical memory region | See “Physical Memory Regions” on page 307. |
| PktLen | See “Packet Length Field (PktLen)” on page 614. |
| PLID | Permissive LID address. See “Solution: Directed-Route SMP” on page 875. |
| PM | Performance Manager. See “The Role of Performance Management (PM)” on page 1020. |
| PMA | Performance Management Agent. See “The Role of Performance Management (PM)” on page 1020. |
| PMTU | Path Maximum Transfer Unit. See “Maximum Data Payload Size” on page 42. |
| Polling state | See “Polling State (Polling and Listening)” on page 737. |
| Port 0, switch | Port 0 on a switch is the switch's management port. See “Switch Layers” on page 111. |
| Port | A bi-directional interface that connects an IBA device to an IBA link. |
| PortInfo | Each port implements the PortInfo attribute. See “PortInfo Attribute” on page 824. |
| PortPhysicalState | The PortInfo.PortPhysicalState attribute element indicates the current state of the port's Physical Layer. The SM can command a state change by writing a new value into this element. See “SM Can Command a State Change” on page 735. |
| PortSamplesControl | See “Required Features” on page 1021. |
| PowerOnReset | The PowerOnReset signal. |
| ppm | Parts per million. |
| Privileged code | See the description of Kernel mode in the glossary. |
| Processing error | An error was encountered during the processing of the WQE by the SQ Logic. |
| Protection Domain (PD) | See the description of PD in the glossary. |
| PSN, invalid | See Figure 11-2 on page 212 and Figure 11-3 on page 215. |
| PSN | Each packet contains the Packet Sequence Number in the BTH:PSN field. |
| P_KeyTable attribute | See “Partition Key (P_Key)” on page 319. |
| P_Key Index | See “Which P_Key Is Inserted in Packets and Checked?” on page 319. |
| P_KeyViolationsCounter | See “Bad P_Key Trap and P_KeyViolations Counter” on page 323. |
| P_Key, default full membership | See “P_KeyTable May or May Not Be in NV Memory” on page 323. |
| P_Key, default limited membership | See “P_KeyTable May or May Not Be in NV Memory” on page 323. |
| P_Key | Partition Key. See “Partition Key (P_Key)” on page 319. |
| QoS | Quality of Service. See:
|
| QP Context | The basic operational characteristics of the QP are programmed into its context during the QP setup. |
| QP | Queue Pair. See “A QP Is a Bi-Directional Message Transport Engine” on page 32. |
| QP0 (SMI) | See “Purpose of the SMI (QP0)” on page 762. |
| QP1 (GSI) | See “The GSMs, GSAs, and GSIs” on page 910. |
| QPN | Queue Pair Number. When the Create QP verb is called to create a QP, the verb creates the QP in the HCA and assigns it a QPN. That QPN is then passed to the remote CA's CM during the connection establishment process for the RC and UC transport types. |
| Quadword (Qword) | A group of eight bytes starting at an address divisible by eight. An Intel term. |
| Quality of Service (QoS) | See the description of QoS in the glossary. |
| Queue Pair (QP) | See “A QP Is a Bi-Directional Message Transport Engine” on page 32. |
| Qword | See the description of Quadword in the glossary. |
| Q_Key, controlled |
|
| Q_Key | Queue Key. See “Queue Key (Q_Key)” on page 333. |
| Q_KeyViolations | See the description of this PortInfo attribute element in Figure 29-5 on page 825. |
| RA | A Record Attribute is a record in the SA database. See “Record Attribute (RA)” on page 933. |
| Random Forwarding Table (RFT) | See “Random Forwarding Table (RFT)” on page 671. |
| RandomFDBCap | Random Forwarding Database Capacity. See “RFT-Related Attributes” on page 672. |
| Raw Datagram | See “Raw Transport Service Types” on page 537. |
| Raw EtherType Datagram | See “Raw EtherType Datagrams” on page 545. |
| Raw Header (RWH) | See “Raw EtherType Datagram Format” on page 545. |
| Raw IPv6 Datagram | See “Raw IPv6 Datagrams” on page 543. |
| Raw packet | See “Raw Transport Service Types” on page 537. |
| RC | Reliable Connected transport service. See “RC Basic Operational Characteristics” on page 352. |
| RCQ | Receive Completion Queue. The CQ associated with a QP's RQ. Upon completion of a RQ WQE (i.e., the completion of an inbound Send or RDMA Write With Immediate message transfer), a CQE is posted to the RQ's CQ. |
| RcvCLK | Receive Clock signal. See “Receive-Side Signals” on page 697. |
| RcvControl | Receive Control signals. See “Receive-Side Signals” on page 697. |
| RcvStream | Receive character stream. See “Receive-Side Signals” on page 697. |
| RD Domain (RDD) | Reliable Datagram Domain. See “RD Domain” on page 331. |
| RD | Reliable Datagram transport service. See “RD Basic Operational Characteristics” on page 462. |
| RDC | RD Channel. Refers to the two EECs in two CAs that RD QPs use to send and receive messages. |
| RDD | Reliable Datagram Domain. See “RD Domain” on page 331. |
| RDETH | Reliable Datagram ETH contains the EECN of the destination EEC in the destination CA. See “RD ETH” on page 471. |
| RDMA Read Response packet | See “RDMA Read Operation” on page 86. |
| RDMA Read | See “RDMA Read Operation” on page 86. |
| RDMA Write | See “RDMA Write Operation” on page 90. |
| Ready-to-Use (RTU) MAD | See “RTU (Ready to Use) MAD” on page 1093. |
| ReArm state | See “Enabling APM” on page 577. |
| Receive Data Packet state | See “Test Each Byte Once” on page 655 and Figure 25-19 on page 656. |
| Receive Idle state | See Figure 25-19 on page 656. |
| Receive Init state | See Figure 25-19 on page 656. |
| Receive Link Packet state | See Figure 25-19 on page 656. |
| Receive Queue (RQ) | See “QP Consists of Two Queues” on page 32. |
| Recovery state | See “Recovery State” on page 744. |
| Record Attribute (RA) | A Record Attribute is a record in the SA database. See “Record Attribute (RA)” on page 933. |
| Record | See “Purpose of the SA” on page 918. |
| Redirection, GMP | See “GMP Redirection” on page 175. |
| Region | See “Memory Regions” on page 299. |
| REJ | Reject communications message. See “REJ (Reject) MAD” on page 1098. |
| Reject (REJ) MAD | Reject communications message. See “REJ (Reject) MAD” on page 1098. |
| Reliable Connected (RC) service | See the description of RC in the glossary. |
| Reliable Datagram (RD) service | See the description of RD in the glossary. |
| Reliable Datagram Channel (RDC) | See the description of RDC in the glossary. |
| Remote Access Key (R_Key) | When a region or window is created (using the verbs), a remote access key is returned by the verb (if remote access rights were requested). When an application posts a WR to a QP's SQ to perform an RDMA Read or Write in a remote CA's memory, it must supply the virtual memory start address, the R_Key, and the length that were provided earlier by a remote application associated with the remote CA. Those three items are then included in the request packet's RETH field. |
| Remotely detected error | An error detected by the responder QP's or EEC's Receive Logic and reported back to the requester QP's or EEC's SQ Logic in a Nak packet. |
| REP | Communications reply message. See “REP (Reply) MAD” on page 1088. |
| Repeater | See “Repeater's Role” on page 18. |
| Reply (REP) MAD | Communications Reply message. See “REP (Reply) MAD” on page 1088. |
| Report(Notice) | See “Event Subscription and Event Forwarding” on page 801. |
| ReportResp | Report Response. See “How Does the GSM Send an Event Notice to the Subscriber?” on page 181. |
| REQ | Communications Request message. See “REQ (Request) MAD” on page 1074. |
| Request (REQ) MAD | Communications Request message. See “REQ (Request) MAD” on page 1074. |
| Requester | See “Definition of Requester and Responder” on page 47. |
| Resend Request | See Table 33-11 on page 951. |
| Reset state |
|
| Record ID (RID) | See “Record Identifier (RID) Definition” on page 935. |
| Responder | See “Definition of Requester and Responder” on page 47. |
| ResponseTimeValue | See “Timeouts” on page 953. |
| RespTimeValue | See “Determining Whether a GSA Is Implemented” on page 172. |
| Resync | See “Resync Operation” on page 499. |
| RETH (RDMA ETH) | This ETH is included in all RDMA Read or Write request packets. It contains the virtual memory start address, the R_Key, and the buffer length of the buffer in the remote CA's memory. |
| Retry Counter | Depends on the context:
|
| Return Path Array | See “Solution: Directed-Route SMP” on page 875. |
| RFT | See the description of Random Forwarding Table in the glossary. |
| RID | Record ID. See “Record Identifier (RID) Definition” on page 935. |
| RMW | Atomic read, modify, write operation. |
| RNR Nak Timeout | Receiver Not Ready Nak Timeout. |
| RNR Nak Timer | See “RNR Nak Packet Contains Minimum Retry Delay Period” on page 409. |
| RNR Nak | Receiver Not Ready Negative Acknowledge. See “Receiver Not Ready (RNR) Nak” on page 408. |
| RNR Retry Count | Receiver Not Ready Retry Count. See “Receiver Not Ready (RNR) Nak” on page 408. |
| Router | See “Role of Switches and Routers” on page 16. |
| Routing Table | See “Role of Switches and Routers” on page 16. |
| RQ | Receive Queue. See “QP Consists of Two Queues” on page 32. |
| RTR state | Ready to Receive state of a QP or an EEC. See:
|
| RTS state | Ready to Send state of a QP or an EEC. See:
|
| RTU | Ready to Use communications message. See “RTU (Ready to Use) MAD” on page 1093. |
| RWH | Raw Header. See “Raw EtherType Datagram Format” on page 545. |
| Rx clock | See “Rx Clock” on page 725. |
| R_Key | See the description of Remote Access Key in the glossary. |
| SA | Subnet Administrator. See:
|
| SA_Key | Subnet Administration Key. See “Request Only Table Changes” on page 947. |
| Scatter Buffer List | See the definition in Table 13-7 on page 276. |
| SCQ | Send Completion Queue. The CQ associated with a QP's SQ. Upon completion of a SQ WQE (i.e., an outbound message transfer has completed), a CQE is posted to the SQ's CQ. |
| SDP | Start Data Packer delimiter.
|
| SE bit | Solicited Event bit. See “Solicited and Unsolicited Events” on page 288. |
| SEEPROM | Serial EEPROM (Electrically Erasable Programmable Read-Only memory). |
| Segment Number | See “MAD Fields Related to a Multiple-MAD SA Transfer” on page 949. |
| Send Completion Queue (SCQ) | The CQ associated with a QP's SQ. Upon completion of a SQ WQE (i.e., the completion of an outbound message transfer), a CQE is posted to the SQ's CQ. |
| Send method | Sends a message to the targeted MA within a device. No response MAD is returned by MA. |
| Send operation | See “Send Operation” on page 84. |
| Send Queue (SQ) | See “QP Consists of Two Queues” on page 32. |
| Send Sequence Number (SSN) | See “SQ Logic Can Use MSN to Complete WQEs” on page 429. |
| SerDes | Serializer/Deserializer. Serializer converts 10-bit parallel characters into a serial bit stream for transmission over the wire. Deserializer converts the incoming serial bit stream received over the wire into parallel 10-bit characters. |
| Server | See “Definition of Client and Server” on page 1110. |
| Service Class or Service Type | See “Four IBA Transfer Protocol Flavors” on page 61. |
| Service ID Resolution Reply (SIDR_REP) | Communications message:
|
| Service ID Resolution Request (SIDR_REQ) | Communications message:
|
| Service Level (SL) | See “Desired Local Quality of Service” on page 43. |
| ServiceEntries | See “ServiceEntries Attribute” on page 1130. |
| ServiceID | 64-bit value identifying the service with which to create a communications channel. See “Definition of Client and Server” on page 1110. |
| ServiceName |
|
| Set method | In a MAD, instructs the target MA to write the data supplied in the MAD's data area into an attribute. |
| SGID | Source Global ID is the 128-bit IPv6-compliant address of the port that injected a packet into the fabric. |
| Shared memory region | See “Shared Memory Regions” on page 303. |
| SIDR_REP | Service ID Resolution Reply communications message.
|
| SIDR_REQ | Service ID Resolution Request communications message.
|
| Signaling type | See “Create QP Verb” on page 221. |
| Site-Local Address | See “Site-Local Unicast Address: Packet Cannot Leave the Site” on page 150. |
| Skip Sequence | See “Inserting Clock Compensation Zones” on page 723. |
| SKP Symbol |
|
| SL | Service Level. LRH:SL field. See “Desired Local Quality of Service” on page 43. |
| SL/TClass mapping | See “Network Layer Overview” on page 124. |
| Sleeping state | See “Sleeping State (Not Polling but Listening)” on page 748. |
| SLID | Source Local LID. LRH:SLID address identifies the CA or router port that injected the packet into the local subnet. |
| SLP | Start Link Packet delimiter.
|
| SLtoVLMappingTable |
|
| SM Priority | Subnet Manager Priority. See “SM Priority” on page 858. |
| SM | Subnet Manager. See “The SM” on page 160. |
| SMA | Subnet Management Agent. Each device (other than a repeater) has an SMA. When the SM wishes to access an SM-related attribute within a device, it issues an SMP to the SMA within the device, the SMA performs the access and, in most cases, sends back a response SMP to the SM. |
| SMBus | System Management Bus. See the description of IB-ML in the glossary. |
| SMI | Subnet Management Interface. See “Purpose of the SMI (QP0)” on page 762. |
| SMP | Subnet Management Packet. See “SMP MADs” on page 787. |
| SMState | SMInfo.SMState attribute element. Subnet Manager state. See “Introduction to the SM States” on page 853. |
| SM_Key | Subnet Management Key. See “Subnet Manager Key (SM_Key)” on page 330. |
| SNMP Tunneling | An SNMP (Simple Network Management Protocol) message can be transported through an IBA subnet by encapsulating it in a series of one or more GMPs using the SNMP Management Class. |
| Solicited Event | See “Solicited and Unsolicited Events” on page 288. |
| Source Path Bits | See “Source Port's LID Address” on page 45. |
| SQ Drain state | Send Queue Drain state:
|
| SQ Error state | Send Queue Error state:
|
| SQ signaling type | Send Queue signaling type. See “Create QP Verb” on page 221. |
| SQ | Send Queue. See “QP Consists of Two Queues” on page 32. |
| SQD state | Send Queue Drain state.
|
| SQE state | See the description of SQ Error state in the glossary. |
| SSN | Send Sequence Number. See “SQ Logic Can Use MSN to Complete WQEs” on page 429. |
| Stale request packet | See “No Protection From Stale Packets” on page 207. |
| Standby CP | SM Standby Control Packet. See Table 30-1 on page 855. |
| Standby SM | Standby Subnet Manager. See “Standby State” on page 865. |
| Standby state | SM Standby state. See “Standby State” on page 865. |
| Start delimiter |
|
| Start of Data Packet Delimiter (SDP) | See the description of SDP in the glossary. |
| Start of Link Packet Delimiter (SLP) | See the description of SLP in the glossary. |
| Start PSN | The start Packet Sequence Number assigned to a QP's or EEC's Send Logic when it is programmed during QP setup. |
| Static Rate Control | See “Static Rate Control” on page 589. |
| Status field in MAD | Has no meaning in a request MAD. In a response MAD, it indicates the completion status of the request issued to the MA.
|
| Striping | See “Byte Striping” on page 703. |
| Subn | The specification abbreviation of the SM class in the SMP MAD's Management Class field. See Table 28-1 on page 783. |
| SubnAdmConfig | See “SubnAdmConfig() Operation” on page 941. |
| SubnAdmGet | See “SubnAdmGet() Operation” on page 937. |
| SubnAdmGetBulk | See “Fetch Entire Database” on page 948. |
| SubnAdmGetTable | See “Database Queries Using SubnAdmGetTable()” on page 945. |
| SubnAdmInform | An event notification subscription request sent to the SA. See “Event Subscription and Event Forwarding” on page 801. |
| SubnAdmInformResp | An event notification subscription reply sent back by the SA. See “Event Subscription and Event Forwarding” on page 801. |
| SubnAdmReport(Notice) | An event notification sent to a subscriber by the SA. See “Event Subscription and Event Forwarding” on page 801. |
| SubnAdmReportResp | A subscriber's acknowledgment of receipt of an event notification sent by the SA. See “Event Subscription and Event Forwarding” on page 801. |
| SubnAdmSet | A request MAD sent to the SA to write to an SA attribute. See “SubnAdmSet() Operation” on page 940. |
| Subnet Administrator (SA) | See “Subnet Administrator's Role” on page 176. |
| Subnet Administrator Key (SA_Key) | See the description of SA_Key in the glossary. |
| Subnet ID | The 64-bit ID of this subnet (aka GIDPrefix). GIDPrefix is a 64-bit element of the PortInfo attribute. The SM uses it to assign a subnet ID to a port. All CA and router ports in a subnet, and each switch's management port (port 0) in a subnet are assigned the same subnet ID. It forms the upper 64 bits of a port's 128-bit IPv6-compliant GID. The lower 64 bits are supplied by one of the port's assigned GUIDs. |
| Subnet Management Agent (SMA) | See the description of SMA in the glossary. |
| Subnet Management Interface (SMI) | See the description of SMI in the glossary. |
| Subnet Management Key (SM_Key) | See the description of SM_Key in the glossary. |
| Subnet Management Packet (SMP) | See the description of SMP in the glossary. |
| Subnet Manager (SM) | See the description of SM in the glossary. |
| Subnet Prefix | Same as Subnet ID and GIDPrefix. |
| Subnet Sweep | See “Other M_Key-Related Matters” on page 329. |
| Subnet | See “Definition of a Subnet” on page 12. |
| SubnetTimeout | See “Software Times Return of MAD Response” on page 781. |
| SubnGetResp | The response packet to a SubnGet(attribute) or SubnSet(attribute) to read or write a SM-related attribute. See “SM Methods” on page 810. |
| Subscribe (for event notification) | See “Event Subscription and Event Forwarding” on page 801. |
| Suspend operation | See “Receipt of an RNR Nak Causes Suspend Followed by Restart” on page 486. |
| Sweep | See “Other M_Key-Related Matters” on page 329. |
| Switch | See “Role of Switches and Routers” on page 16. |
| SwitchInfo | See “SwitchInfo Attribute” on page 818. |
| Symbol | See “Physical Layer” on page 108. |
| SymbolErrorCounter | See “Minor Error Handling” on page 753. |
| Syndrome | See:
|
| Table | See “Definition of a Table” on page 941. |
| Target Channel Adapter (TCA) | See “Some Preliminary Terminology” on page 10. |
| TCA | See the description of Target Channel Adapter in the glossary. |
| TClass | GRH:TClass. Traffic Class. See:
|
| TCP/IP | Transmission Control Protocol/Internet Protocol. |
| Training Sequence 1 (TS1) | A special character sequence transmitted during training of the physical link.
|
| Training Sequence 2 (TS2) | A special character sequence transmitted during training of the physical link.
|
| Training, link | See “Link Training” on page 732. |
| TransactionID | See Table 28-1 on page 783 and the description of TransactionID in Table 28-2 on page 783. |
| Transport Layer | The Transport Layer is responsible for sending and receiving messages across the fabric between QPs. When necessary, it segments a message into multiple packets (when the message's length is greater than the PMTU). The QP on the receiving end reassembles the message data in the specified data buffer(s) in its memory. See “Transport Layer Overview” on page 125. |
| Transport Service | The type of QP used to send and receive messages with a remote QP of the same type. See “Intro to Transport Types” on page 61. |
| Transport Timer (Ttr) | See “SQ Logic's Transport Timer” on page 381. |
| Trap number | See “Traps” on page 790. |
| Trap(Notice) | A MAD sent to a manager by a MA as an event notification. See “Traps” on page 790. |
| TrapGID | The DGID port address that a Trap(Notice) MAD is sent to as an event notification. See “Traps” on page 790. |
| TrapLID | The DLID port address that a Trap(Notice) MAD is sent to as an event notification. See “Traps” on page 790. |
| TrapRepress | See “Stopping Repetitive Trap Generation” on page 800. |
| TS1 | See the description of Training Sequence 1 in the glossary. |
| TS2 | See the description of Training Sequence 2 in the glossary. |
| Ttr | See the description of Transport Timer in the glossary. |
| Tx clock | See “Tx Clock” on page 718. |
| UC | Unreliable Connected transport service.
|
| UD | Unreliable Datagram transport service.
|
| ULP | Upper-Layer protocol. Software above the Verb Layer. |
| Unaffiliated Asynchronous Error | See “Unaffiliated Asynchronous Errors” on page 294. |
| Unicast Forwarding Table | See “Two Unicast Forwarding Tables” on page 669. |
| Unicast LID | A LID address that uniquely identifies a single destination port in a subnet. See “LID Address Space” on page 133. |
| Universal/Local Bit |
|
| Unreliable Connected (UC) service | See the description of UC in the glossary. |
| Unreliable Datagram (UD) service | See the description of UD in the glossary. |
| Unsolicited Event | See the description of Solicited Event in the glossary. |
| Upper Layer Protocol (ULP) | See the description of ULP in the glossary. |
| User mode | A program with very low privilege. Also see kernel mode. |
| VA | Virtual memory address. |
| Variant CRC (VCRC) | A CRC covering all the fields of a packet, including those that may be changed by switches and/or routers. |
| VCRC | See the description of Variant CRC in the glossary. |
| Vendor ID | Identifies the vendor that manufactured and/or designed a subsystem. |
| Vendor-specific Manager | See “General Services Managers” on page 167. |
| Verbs Layer | See “Verbs Overview” on page 126. |
| Virtual Address (VA) | Virtual memory Address. |
| Virtual Lane (VL) |
|
| Virtual memory region | See “Virtual Memory Regions” on page 299. |
| Vital Product Data (VPD) | See “Some Information Accessed by the BM” on page 341. |
| VL | See the description of Virtual Lane in the glossary. |
| VL0:VL14 | Data Virtual Lanes.
|
| VL15 | SMP Virtual Lane.
|
| VLCap | See “VLCap and OperationalVLs” on page 620. |
| VPD | Vital Product Data. See “Some Information Accessed by the BM” on page 341. |
| Weight | See “Arbitration on a Port with Multiple Data VLs” on page 629. |
| Window (in context of multipacket MADs) | See “Reliable Multi-Packet Transaction Protocol” on page 949. |
| Window Ack | See “Reliable Multi-Packet Transaction Protocol” on page 949. |
| Window | Depends on context:
|
| Work Queue Entry (WQE) | A WR that has been posted to the SQ or RQ of a QP to handle an outbound or inbound message transfer. |
| Work Queue (WQ) | General reference to either a QP's SQ or RQ. |
| Work Request (WR) | A request posted to the SQ or RQ of a QP to handle an outbound or inbound message transfer. |
| Work Request ID | A 64-bit software-assigned ID that uniquely identifies a message transfer WR. It's used to relate a CQE posted on the CQ to a specific message transfer WR posted to a QP's SQ or RQ earlier. |
| WQ | See the description of Work Queue in the glossary. |
| WQE, limited send | See “Limited WQEs” on page 425. |
| WQE | See the description of Work Queue Entry in the glossary. |
| WR | See the description of Work Request in the glossary. |
| xCA | Refers to either an HCA or a TCA. |
| XmitClk | Transmit Clock. See “Transmit-Side Signals” on page 695. |
| XmitControl | Transmit Control. See “Transmit-Side Signals” on page 695. |
| XmitReady | Transmit Ready. See “Transmit-Side Signals” on page 695. |
| XmitStream | Transmit character stream. See “Transmit-Side Signals” on page 695. |
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.