linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH 0/3] Add duplicate_connect option for ctlr connect requests
Date: Tue, 10 Oct 2017 17:35:09 -0700	[thread overview]
Message-ID: <20171011003512.5946-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

James Smart (3):
  nvme: add duplicate_connect option
  nvme_fc: add support for duplicate_connect option
  RFC: nvme rdma: add support for duplicate_connect option

 drivers/nvme/host/fabrics.c | 19 +++++++++-
 drivers/nvme/host/fabrics.h |  2 ++
 drivers/nvme/host/fc.c      | 46 +++++++++++++++++++++++++
 drivers/nvme/host/rdma.c    | 84 +++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 150 insertions(+), 1 deletion(-)

-- 
2.13.1

             reply	other threads:[~2017-10-11  0:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  0:35 James Smart [this message]
2017-10-11  0:35 ` [PATCH 1/3] nvme: add duplicate_connect option James Smart
2017-10-19 15:20   ` Christoph Hellwig
2017-10-19 15:58     ` James Smart
2017-10-11  0:35 ` [PATCH 2/3] nvme_fc: add support for " James Smart
2017-10-19 15:23   ` Christoph Hellwig
2017-10-19 15:59     ` James Smart
2017-10-11  0:35 ` [PATCH/RFC 3/3] nvme rdma: " James Smart

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=20171011003512.5946-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 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).