[openib-general] Client Reregistration Status

Hal Rosenstock halr at voltaire.com
Thu Aug 12 14:23:44 PDT 2004


Hi,

It looks like client reregistration will be in IBA 1.2. The MgtWG
approved their part of these changes today and the other changes were
"shipped off" to the SWG.

The details are as follows:
1. PortInfo:CapabilityMask bit to indicate IsClientRegistrationSupported
(bit 4)
2. New PortInfo bit for ClientReregister
Used By end nodes (CA, router, base SP0, enhanced SP0) 
Access RW Length 1 Offset 408 
Description: Optional; shall be 0 if not implemented
(PortInfo:CapabilityMask.IsClientReregistrationSupported = 0). Used by
SM to request end node client reregistration of SA subscriptions. See
<ref to 14.4.11 Client Reregistration>. 
3. New subsection on Client Reregistration:
14.4.11 Client Reregistration 
Client reregistration allows the Subnet Manager to request that a client
reregister all subscriptions requested from this port. The SM may
request this at any time of any port supporting this option. A typical
reason for the SM doing this might be that the SM suffered a failure and
as a result lost its own records of such subscriptions. The SM class
uses the PortInfo attribute to affect client reregistration. A port
indicates it supports client reregistration for the SM class by setting
PortInfo:CapabilityMask.IsClientReregistrationSupported = 1. 

o14-13.1.yy: If a port supports client reregistration
(PortInfo.IsClientReregistrationSupported = 1), the SMA shall respond to
a SubnSet(PortInfo) with PortInfo:ClientReregister=1 as follows: - a
SubnGetResp(PortInfo) shall be returned with PortInfo:ClientReregister=1
- an asynchronous unaffiliated event of type Client Reregistration shall
be generated (see <ref to 11.6.3.3 Unaffiliated Asynchronous Events>). 

o14-13.2.yy: Compliance statement <ref to o14-13.1.yy> is the only
situation in which any SMA shall return a PortInfo with
ClientReregister=1; in all other cases, it shall be 0.

4. Query HCA can read IsClientReregistration capability mask bit.

5. Addition of new asynchronous unaffiliated event for client
reregistration

o Client Reregistration Event - issued when SM requests client
reregistration (see <ref to 14.4.11 Client Reregistration>) 

o11-6.1.2: If the CI indicates that the port supports client
reregistration, the CI shall generate a Client Reregistration Event when
the SMA receives this request from the SM.

Note that the last 2 items (4 and 5) need approval by SWG and are
subject to change.

-- Hal





More information about the general mailing list