From: James Smart <jsmart2021@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: James Smart <jsmart2021@gmail.com>
Subject: [PATCH 0/3] nvme-fc: sync with FC-NVME-2 standard
Date: Fri, 27 Sep 2019 14:51:33 -0700 [thread overview]
Message-ID: <20190927215136.3096-1-jsmart2021@gmail.com> (raw)
The following 3 patches start the sync up with FC-NVME-2 rev 1.06.
The first patch updates the nvme-fc.h header to match the spec
The second patch updates the existing transport to match the
header - where field names may have changed.
The last patch updates the CMD IU for a new "category" field that
identifies the command set type for the io - needed by analyzer
guys to decode the sqe.
Subsequent patches will be coming to add new behavioral changes.
Older implementations should continue to work fine, with new
behaviors enabling new features.
James Smart (3):
nvme-fc: Sync nvme-fc header to FC-NVME-2
nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes
nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu
drivers/nvme/host/fc.c | 29 ++++----
drivers/nvme/target/fc.c | 27 +++----
include/linux/nvme-fc.h | 182 +++++++++++++++++++++++++++++++++++------------
3 files changed, 168 insertions(+), 70 deletions(-)
--
2.13.7
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-09-27 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:51 James Smart [this message]
2019-09-27 21:51 ` [PATCH 1/3] nvme-fc: Sync nvme-fc header to FC-NVME-2 James Smart
2019-09-27 21:51 ` [PATCH 2/3] nvme-fc and nvmet-fc: sync with FC-NVME-2 header changes James Smart
2019-09-27 21:51 ` [PATCH 3/3] nvme-fc: Set new cmd set indicator in nvme-fc cmnd iu James Smart
2019-10-04 23:56 ` [PATCH 0/3] nvme-fc: sync with FC-NVME-2 standard Sagi Grimberg
2019-10-10 19:42 ` Keith Busch
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=20190927215136.3096-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=linux-nvme@lists.infradead.org \
/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).