QP State before Any Messages Are Transferred

Connection Established and QPs Fully Configured

This discussion assumes that the following series of actions have already been accomplished:

  1. The local HCA RC QP was created (see “QP Creation” on page 236) and connected to a local HCA port that it will use to send and receive messages between itself and a RC QP in a remote CA (see “RC/UC Connection Establishment” on page 186).

  2. The CMs associated with the HCA and the remote CA have exchanged REQ, REP, and RTU messages.

  3. Both QPs are fully configured and in the fully operational RTS state (see “Ready to Send State” on page 247).

Current QP State

The two QPs have been configured with the information detailed in Table 17-2 on this page.

Table 17-2. Initial State of the Two QPs
Operational ParameterDescription
QP TypeRC.
QPN24-bit QPN assigned to this QP.
CQ(s)One or two CQs have been created and assigned to the QP's SQ and RQ. The same CQ may be used by both queues or a separate CQ may have been assigned to each of them. The CQ(s) are currently empty (i.e., they contain no CQEs).
SQ and RQThe QP's SQ and RQ have been created and are currently empty (i.e., they contain no WQEs).
Maximum Number of Scatter/Gather ElementsThe SQ and RQ have been configured with the maximum number of local memory buffers that will be specified in any WR's Scatter or Gather Buffer List.
SQ Completion Signaling TypeThe SQ Logic has been programmed to create a CQE on the SCQ under one of the following circumstances:
  • Successful completion of each message transfer always generates a SQ CQE, or

  • For each WR it posted to the SQ, software specifies whether or not to generate a SQ CQE for a successful completion.

Note that error completions always create a CQE.
Protection Domain (PD)The QP has been assigned to a PD. The QP logic is only permitted to access a local memory region or window that has been assigned to the same PD.
Current QP StateBoth QPs are in the fully operational RTS state.
Primary P_Key Index
  • Usage on outbound request packets: Whenever this QP's SQ Logic generates an outbound request packet to its associated CA port, it provides this value as an index into the port's P_KeyTable attribute. The P_Key contained in the selected entry is inserted into the packet's BTH:P_Key field.

  • Usage on inbound request packet: When an inbound request packet is received by the port associated with a QP, the packet's BTH:P_Key is compared to the entry in the port's P_KeyTable attribute selected by the Primary P_Key Index value stored in the destination QP's Context.

SQ's Start PSNThis is the Start PSN assigned to this QP's SQ Logic by software. It is inserted into the BTH:PSN field in the first request packet generated by the SQ Logic. The other QP's RQ Start ePSN is set to the same value (the value was supplied by the CM in the connection REQ message).
RQ Start ePSNRQ Logic 's Start ePSN is set to the SQ Start PSN assigned to the remote QP's SQ Logic. It was returned in the REP message during connection establishment. RQ Logic uses ePSN to verify that the next request packet received has the next expected PSN.
Primary Physical Port NumberPhysical CA port the QP will use to send and receive messages. Called the primary port to differentiate it from the Alternate Path Physical Port.
Destination QP Number (QPN)Inserted in the BTH:DestQP field in outbound request packets. Identifies the target QP to whom the request packet is to be delivered. It was returned in the REP message during connection establishment.
DLID
  • If the destination CA port is in same subnet, DLID = destination CA's port LID address;

  • Otherwise, DLID = LID of a router ingress port.

Send GRH Flag (and global routing information if the destination port is in a different subnet)
  • If remote QP resides in a CA in the same subnet, this flag is cleared to 0 and no GRH is inserted in each request packet generated by this QP's SQ Logic.

  • Otherwise, this flag is set to 1 and a GRH is included in each request packet. This QP's Context contains the following information:

    - Traffic Class.

    - Flow Label.

    - Hop Limit.

    - Source GID Index.

    - DGID.

Enable or disable incoming RDMA and Atomic operations
  • Enable/disable incoming RDMA Reads on this QP.

  • Enable/disable incoming RDMA Writes on this QP.

  • Enable/disable incoming Atomic operations on this QP.

Number of RDMA Reads & Atomic operations outstanding at any timeDepth of remote QP's special queue for receiving inbound RDMA Read/Atomic operations from this QP's SQ Logic. It was returned in the REP message during connection establishment.
Queue depth for inbound RDMA Read/Atomic operationsDepth of the special queue in this QP's RQ Logic into which inbound RDMA Read and Atomic operation requests are received.
Service Level (SL)4-bits. Represents the desired QoS within this subnet for message request packets generated by this QP's SQ Logic. Inserted in the LRH:SL field of each request packet.
Path MTU (PMTU)See “Maximum Data Payload Size” on page 42.
Maximum Static RateSee “Packet Injection Delay” on page 43.
Minimum RNR Nak Timer field valueIf an inbound Send or RDMA Write With Immediate message arrives when no WQEs are posted to this QP's RQ, the RQ Logic responds with an RNR Nak. This is the value that is placed in the Nak packet's RNR Nak Timer Field. The packet sender must wait at least this amount of time before attempting to resend the request packet again.
Local ACK TimeoutDefines the amount of time the QP's SQ Logic will wait for a response before it retries the transmission of the corresponding request packet (see “SQ Logic's Transport Timer” on page 381).
Retry CountSee “Ack Timeout and Missing Packet(s) Retry Counter” on page 44.
RNR Retry CountSee “Receiver Not Ready (RNR) Retry Count” on page 45. It was returned in the REP message during connection establishment. Note that a count of 7d (111b) indicates infinite retries.
Source Path BitsSee “Source Port's LID Address” on page 45.
Alternate Path Address InformationApplicable only if Automatic Path Migration is supported; for detail, see “Automatic Path Migration” on page 575, “LAP (Load Alternate Path) MAD” on page 1104, and “APR (Alternate Path Response) MAD” on page 1107.
  • Alternate path P_Key Index.

  • Alternate path physical port.

  • Service Level (SL).

  • Path MTU (PMTU). Must be the same as PMTU for the primary path.

  • Send GRH Flag. If the destination is in a different subnet:

    - Traffic class.

    - Flow label.

    - Hop limit.

    - Source GID index.

    - DGID

  • DLID.

    - If destination CA is in the same subnet, DLID = destination CA port address;

    - otherwise DLID = LID of a router ingress port.

  • Maximum Static Rate.

  • Local Ack Timeout.

  • Retry Count.

  • RNR Retry Count.

  • Source Path Bits.

Please note: Although Retry Count and RNR Retry Count are both shown as Alternate Path address information in the 1.0a specification, their removal from this list has been approved for the next specification revision.
Path Migration StateValid only if this CA supports Automatic Path Migration; for detail, see “Automatic Path Migration” on page 575. Valid states are:
  • Migrated. This is the default state.

  • Rearm.


..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.222.111.243