[openib-general][PATCH 1 of 3] repost: Client Reregister support for kernel space

[Leonid Arsh]

Hi,
  the most urgent and critical case is
  the SM failure/restart when the SM is not connected to the host directly.
  In this cases neither PortError no PortActive events will be
generated on the host.
  The SM will lose the multicast group configuration for the host and
the host will need to rejoin its multicast groups in this case.
  IPoIB shall handle the problem by catching the ClientReregister event.

  There are additional cases. Any client which registers itself on the
SA, will need to handle this event in order to work properly after the
SM failure/restart. We'll need it very soon for a user mode
application.

On 5/30/06, Roland Dreier <rdreier at cisco.com> wrote:
>     Leonid> Roland, Aren't you going to apply these patches?  This is
>     Leonid> a standard feature, and we need it rather urgently.
>
> Sorry, I had let these patches fall off of my queue.
>
> So why is this an urgent feature?  A good description of your use case
> would make it easier for me to write the changelog entries (since your
> patches didn't include usable descriptions).
>
> Thanks,
>   Roland
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
>
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
>