From: jsmart2021@gmail.com (jsmart2021@gmail.com)
Subject: [PATCH 0/5] nvmet_fc: bug fixes and lldd api mods
Date: Thu, 23 Mar 2017 20:43:16 -0700 [thread overview]
Message-ID: <20170324034321.8719-1-jsmart2021@gmail.com> (raw)
From: James Smart <jsmart2021@gmail.com>
This patch set contains modifications to the lldd api on the target
side to specify isr vs threaded calling contexts, address the manner in
which the transport releases io contexts back to the lldd, and addresses
the abort interface.
Any modifications to the lpfc driver are isolated to nvme-specific files.
Therefore any mods should be able to go in through the blk tree and avoid
the scsi tree.
James Smart (5):
nvmet_fc: add target feature flags for upcall isr contexts
nvmet_fc: add req_release to lldd api
nvme_fcloop: split job struct from transport for req_release
nvmet_fc: Rework target side abort handling
nvmet_fc: add missing reference in add_port
drivers/nvme/target/fc.c | 251 +++++++++++++++++++++++++++++++----------
drivers/nvme/target/fcloop.c | 197 ++++++++++++++++++++++++++------
drivers/scsi/lpfc/lpfc_nvmet.c | 126 ++++++++++++++++-----
drivers/scsi/lpfc/lpfc_nvmet.h | 7 +-
include/linux/nvme-fc-driver.h | 97 +++++++++++-----
5 files changed, 523 insertions(+), 155 deletions(-)
--
2.9.3
next reply other threads:[~2017-03-24 3:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 3:43 jsmart2021 [this message]
2017-03-24 3:43 ` [PATCH 1/5] nvmet_fc: add target feature flags for upcall isr contexts jsmart2021
2017-04-20 10:58 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 2/5] nvmet_fc: add req_release to lldd api jsmart2021
2017-04-20 11:02 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 3/5] nvme_fcloop: split job struct from transport for req_release jsmart2021
2017-04-20 11:06 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 4/5] nvmet_fc: Rework target side abort handling jsmart2021
2017-04-20 11:15 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 5/5] nvmet_fc: add missing reference in add_port jsmart2021
2017-04-20 11:16 ` Sagi Grimberg
2017-04-05 8:05 ` [PATCH 0/5] nvmet_fc: bug fixes and lldd api mods Sagi Grimberg
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=20170324034321.8719-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).