From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH v5 0/6] nvme-rdma device removal fixes
Date: Sun, 4 Sep 2016 10:01:37 +0300 [thread overview]
Message-ID: <89eb2382-9a2f-48d1-c9fd-0c018e07cd9f@grimberg.me> (raw)
In-Reply-To: <cover.1472833420.git.swise@opengridcomputing.com>
> 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.
Fine with me,
Queued for the next round of rc fixes.
Thanks Steve!
next prev parent reply other threads:[~2016-09-04 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 16:23 [PATCH v5 0/6] nvme-rdma device removal fixes Steve Wise
2016-09-01 13:43 ` [PATCH v5 1/6] iw_cxgb4: call dev_put() on l2t allocation failure Steve Wise
2016-09-01 13:44 ` [PATCH v5 2/6] iw_cxgb4: block module unload until all ep resources are released Steve Wise
2016-09-01 16:12 ` [PATCH v5 3/6] nvme_rdma: keep a ref on the ctrl during delete/flush Steve Wise
2016-09-02 16:01 ` [PATCH v5 4/6] nvme-rdma: destroy nvme queue rdma resources on connect failure Steve Wise
2016-09-02 16:01 ` [PATCH v5 5/6] nvme-rdma: add DELETING queue flag Steve Wise
2016-09-02 16:01 ` [PATCH v5 6/6] nvme-rdma: use ib_client API to detect device removal Steve Wise
2016-09-04 7:01 ` Sagi Grimberg [this message]
2016-09-12 14:49 ` [PATCH v5 0/6] nvme-rdma device removal fixes Steve Wise
2016-09-12 14:58 ` Sagi Grimberg
2016-09-12 15:00 ` 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=89eb2382-9a2f-48d1-c9fd-0c018e07cd9f@grimberg.me \
--to=sagi@grimberg.me \
/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).