Re: [PATCH] send client reregistration in case of SM LID change

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/21/2014 4:26 AM, Vladimir Koushnir wrote:
> if for some reason SM LID recorded in PortInfo of the node is different
> from our SM LID, it is safer to send client reregister notification to this node
> to trigger reregistration of the node in Master SM.
> 
> This scenario may occur when Standby SM loses connectivity to the Master SM and becomes
> Master SM for some time period. If the connectivity is re-established but Handover sent by
> Standby SM is lost. the only indication about SM handovers in the fabric is SM LID mis-configuration
> in some nodes.
> 
> It is important to note that this is a workaround.
> Some applications/ULPs only look at client reregistration and not at SM LID change.
> Most IB device drivers are not currently issuing SM LID change local event.
> 
> The fix forces opensm to set client reregister bit in PortInfo(Set) in the scenario above.
> 
> Signed-off-by: Vladimir Koushnir <vladimirk@xxxxxxxxxxxx>

Thanks. Applied.

-- Hal
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux