From: swise@opengridcomputing.com (Steve Wise)
Subject: [PATCH v4 0/6] nvme-rdma device removal fixes
Date: Thu, 1 Sep 2016 09:12:59 -0700 [thread overview]
Message-ID: <cover.1472746379.git.swise@opengridcomputing.com> (raw)
This series addresses several problems when shutting down a nvme-rdma
host when its controllers are attempting to reconnect to a target that
is no longer reachable.
To tickle these bugs:
1) attach over iw_cxgb4 to 10 devices on a target.
2) 'ifconfig down' the target's interface
3) wait for keep-alive to fire and begin reconnecting (~15-20 seconds)
4) do one of these on the host:
- rmmod iw_cxgb4
- reboot
- reboot -f
Doug/Sagi, the first 2 iw_cxgb4 patches are included here because they're
needed for the testing. While I've also submitted them to linux-rdma,
perhaps Sagi can merge them in nvmf-4.8-rc? If that is acceptable
with everyone.
Patch series:
1/6 iw_cxgb4: call dev_put() on l2t allocation failure
2/6 iw_cxgb4: block module unload until all ep resources are released
3/6 nvme_rdma: keep a ref on the ctrl during delete/flush
4/6 nvme-rdma: destroy nvme queue rdma resources on connect failure
5/6 nvme-rdma: add DELETING queue flag
6/6 nvme-rdma: use ib_client API to detect device removal
Changes since v3:
- removed WIP/RFC tag
- fixed a bug in patch 4 where a rdma reject from the target causes a
double free of the ib queue and cm_id.
- remove noisy pr_info()s in patch 6
- kref_get -> kref_get_unless_zero in nvme_rdma_del_ctrl() of patch 3
- add reviewed-by tags
Changes since v2:
- refactor/simplify the remove_one function.
- nvme-rdma module remove function doesn't need to explicitly
remove the controllers; they will be removed as part of
ib_client unregister.
- removed forward declarations.
Changes since v1:
- the big change was patch 6 rewrite - use client_ib API to handle
device removal instead of rdma_cm device removal events.
- tweaked patch 5 to avoid bisect issues
- small code rework on patch 3 based on Christoph's suggestion
- clear_bit() -> !test_and_clear_bit() in patch 4 (Christoph's comment)
- add reviewed-by tags.
---
Sagi Grimberg (1):
nvme-rdma: add DELETING queue flag
Steve Wise (5):
iw_cxgb4: call dev_put() on l2t allocation failure
iw_cxgb4: block module unload until all ep resources are released
nvme_rdma: keep a ref on the ctrl during delete/flush
nvme-rdma: destroy nvme queue rdma resources on connect failure
nvme-rdma: use ib_client API to detect device removal
drivers/infiniband/hw/cxgb4/cm.c | 6 +-
drivers/infiniband/hw/cxgb4/device.c | 5 ++
drivers/infiniband/hw/cxgb4/iw_cxgb4.h | 1 +
drivers/nvme/host/rdma.c | 136 ++++++++++++++++-----------------
4 files changed, 76 insertions(+), 72 deletions(-)
--
2.7.0
next reply other threads:[~2016-09-01 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 16:12 Steve Wise [this message]
2016-09-01 13:43 ` [PATCH v4 1/6] iw_cxgb4: call dev_put() on l2t allocation failure Steve Wise
2016-09-01 13:44 ` [PATCH v4 2/6] iw_cxgb4: block module unload until all ep resources are released Steve Wise
2016-09-01 16:12 ` [PATCH v4 3/6] nvme_rdma: keep a ref on the ctrl during delete/flush Steve Wise
2016-09-01 16:12 ` [PATCH v4 5/6] nvme-rdma: add DELETING queue flag Steve Wise
2016-09-01 16:12 ` [PATCH v4 4/6] nvme-rdma: destroy nvme queue rdma resources on connect failure Steve Wise
2016-09-02 15:08 ` Steve Wise
2016-09-01 16:12 ` [PATCH v4 6/6] nvme-rdma: use ib_client API to detect device removal Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1472746379.git.swise@opengridcomputing.com \
--to=swise@opengridcomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).