nvmet-rdma automatic port re-activation
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH v1 0/3] nvmet-rdma automatic port re-activation
Quoted 9 lines · Sagi Grimberg
Quoted 9 lines
Quoted 4 lines
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.
Quoted 8 lines
Quoted 2 lines
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.htmlAt that point, in the lack of change in the RDMA interface, this is pretty much what we can do to support device resets...
Meh. I really hate all that rubbish boilerplate code. Nothing in here is protocol specific, so even without a proper reset even it is something that should be done in common code.