From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2 0/4] Add duplicate_connect option for ctlr connect requests
Date: Fri, 20 Oct 2017 16:17:05 -0700 [thread overview]
Message-ID: <20171020231709.3183-1-jsmart2021@gmail.com> (raw)
This patch adds a duplicate_connect option option to those supported by
fabric connection requests. When set to true (1), duplicate connections
are allowed. When set to false (0), duplicate connections are rejected.
The option is set in the fabrics layer and acted upon by each transport.
This patch set came about as of this prior patch review:
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012783.html
---
v2:
split compare for hostnqn, hostid, subnqn to a helper function
duplicate_connection converted to a boolean option (presence means true)
James Smart (4):
nvme: add duplicate_connect option
nvme: add helper to compare options to controller
nvme_fc: add support for duplicate_connect option
RFC: nvme-rdma: add support for duplicate_connect option
drivers/nvme/host/fabrics.c | 7 +++-
drivers/nvme/host/fabrics.h | 14 ++++++++
drivers/nvme/host/fc.c | 33 ++++++++++++++++++
drivers/nvme/host/rdma.c | 82 +++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 135 insertions(+), 1 deletion(-)
--
2.13.1
next reply other threads:[~2017-10-20 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 23:17 James Smart [this message]
2017-10-20 23:17 ` [PATCH v2 1/4] nvme: add duplicate_connect option James Smart
2017-10-23 8:21 ` Johannes Thumshirn
2017-10-20 23:17 ` [PATCH v2 2/4] nvme: add helper to compare options to controller James Smart
2017-10-23 8:31 ` Johannes Thumshirn
2017-10-20 23:17 ` [PATCH v2 3/4] nvme_fc: add support for duplicate_connect option James Smart
2017-10-23 9:27 ` Johannes Thumshirn
2017-10-23 9:28 ` Johannes Thumshirn
2017-10-20 23:17 ` [PATCH v2 4/4] nvme-rdma: " James Smart
2017-10-23 9:30 ` Johannes Thumshirn
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=20171020231709.3183-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.