When a RDMA device goes away we must destroy all it's associated
RDMA resources. RDMa device resets also manifest as device removal
events and a short while after they come back. We want to re-activate
a port listener on this RDMA device when it comes back in to the system.
I really detest this series. It just shows how messed up the whole
IB core interaction is. The right way to fix this is to stop treating
a IB device reset as a device removal, and give it a different event.
And also make sure we have a single unified event system instead of
three separate ones.
I've raised this claim before, but got resistance from Doug:
https://www.spinics.net/lists/linux-rdma/msg59815.html
At that point, in the lack of change in the RDMA interface, this
is pretty much what we can do to support device resets...
--
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
