From mboxrd@z Thu Jan  1 00:00:00 1970
From: sagi@grimberg.me (Sagi Grimberg)
Date: Sun, 15 Apr 2018 11:53:02 +0300
Subject: [PATCH v1 0/3] nvmet-rdma automatic port re-activation
In-Reply-To: <20180413170010.GA23178@lst.de>
References: <20180412080656.1691-1-sagi@grimberg.me>
 <20180413170010.GA23178@lst.de>
Message-ID: <0f781a93-2cbf-8d60-2028-4581912bf07a@grimberg.me>


>> 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...