Yes, this is possible too. The alternate path specified in ib_send_cm_lap() can be used to set cm_id_priv->alt_av. Then in ib_cm_init_qp_attr() cm_id_priv->alt_av can be used to initialize the fields for making path_mig_state transitions to IB_MIG_REARM or IB_MIG_MIGRATED.
VBabu Sean Hefty wrote: > Venkatesh Babu wrote: > >> Loading the alternate path may not necessarily indicate the failover. >> It is just saying that alternate path is available. Failover actually >> happens only when primary path's any components like local port or >> remote port or switch port goes down. We should get some events when >> this happens to cause the failover. > > > From the CM's perspective, I see that two (independent) things need to > occur: > > 1. The CM itself must failover to the alternate path. > 2. The CM must allow loading a new alternate path. > > The call ib_send_cm_lap() should be used to load a new alternate path, > and would be independent of failover. And ib_cm_init_qp_attr() could > be used to notify the CM that failover has occurred, based on the > state of the connection. > > > - Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
