diff options
| author | Steve Wise <swise@opengridcomputing.com> | 2016-09-02 16:01:54 (GMT) |
|---|---|---|
| committer | Sagi Grimberg <sagi@grimberg.me> | 2016-09-12 19:29:41 (GMT) |
| commit | e87a911fed07e368c6f97e75152e6297a7dfba48 (patch) | |
| tree | 993be810cc0bd7019f3e1c5faf2d2a02b33202a4 /COPYING | |
| parent | e89ca58f9c901c8c4cfb09f96d879b186bb01492 (diff) | |
| download | linux-e87a911fed07e368c6f97e75152e6297a7dfba48.tar.xz | |
nvme-rdma: use ib_client API to detect device removal
Change nvme-rdma to use the IB Client API to detect device removal.
This has the wonderful benefit of being able to blow away all the
ib/rdma_cm resources for the device being removed. No craziness about
not destroying the cm_id handling the event. No deadlocks due to broken
iw_cm/rdma_cm/iwarp dependencies. And no need to have a bound cm_id
around during controller recovery/reconnect to catch device removal
events.
We don't use the device_add aspect of the ib_client service since we only
want to create resources for an IB device if we have a target utilizing
that device.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions