From: maxg@mellanox.com (Max Gurtovoy)
Subject: [PATCH rfc 0/3] nvmet-rdma automatic port re-activation
Date: Wed, 11 Apr 2018 19:17:13 +0300 [thread overview]
Message-ID: <053ca9f3-2237-e270-82cd-d99d123bde1c@mellanox.com> (raw)
In-Reply-To: <20180322190303.10951-1-sagi@grimberg.me>
Hi Sagi,
Can we add it to the v4.17 cycle with the small fixes/updates needed ?
On 3/22/2018 9:02 PM, Sagi Grimberg wrote:
> 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.
>
> In order to make it happen, we save the RDMA device node_guid on a
> ULP listener representation (nvmet_rdma_port) and when a RDMA device
> comes into the system, we check if there is a listener port that needs
> to be re-activated.
>
> In addition, reflect the port state to the sysadmin.
>
> Israel Rukshin (2):
> nvmet: Add fabrics ops to port
> nvmet: Add port transport active flag
>
> Sagi Grimberg (1):
> nvmet-rdma: automatic listening port re-activation
>
> drivers/nvme/target/configfs.c | 10 ++
> drivers/nvme/target/core.c | 17 ++-
> drivers/nvme/target/nvmet.h | 3 +
> drivers/nvme/target/rdma.c | 231 +++++++++++++++++++++++++----------------
> 4 files changed, 169 insertions(+), 92 deletions(-)
>
prev parent reply other threads:[~2018-04-11 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 19:02 [PATCH rfc 0/3] nvmet-rdma automatic port re-activation Sagi Grimberg
2018-03-22 19:03 ` [PATCH rfc 1/3] nvmet-rdma: automatic listening " Sagi Grimberg
2018-03-25 8:25 ` Max Gurtovoy
2018-03-26 7:01 ` Max Gurtovoy
2018-04-04 13:06 ` Sagi Grimberg
2018-03-22 19:03 ` [PATCH rfc 2/3] nvmet: Add fabrics ops to port Sagi Grimberg
2018-03-22 19:03 ` [PATCH rfc 3/3] nvmet: Add port transport active flag Sagi Grimberg
2018-03-26 7:52 ` Max Gurtovoy
2018-04-04 13:08 ` Sagi Grimberg
2018-03-22 19:03 ` [PATCH 4/3 rfc nvmetcli] nvmetcli: expose nvmet port status and state Sagi Grimberg
2018-03-27 8:34 ` Nitzan Carmi
2018-04-11 16:17 ` Max Gurtovoy [this message]
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=053ca9f3-2237-e270-82cd-d99d123bde1c@mellanox.com \
--to=maxg@mellanox.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