From: James Smart <jsmart2021@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: James Smart <jsmart2021@gmail.com>
Subject: [PATCH v2 0/4] Add VMID support to nvme-fc transport and lpfc driver
Date: Thu, 19 May 2022 05:31:06 -0700 [thread overview]
Message-ID: <20220519123110.17361-1-jsmart2021@gmail.com> (raw)
This patch adds vmid support to the nvme-fc transport.
Various virtualization technologies used in Fibre Channel
SAN deployments have the ability to identify and associate traffic
with specific virtualized applications. The T11 standard defines
an application services tag that can be added to FC traffic to aid
in identification and monitoring of traffic associated with the
applications.
VMID support is present in the kernel in blkcg, the SCSI fc transport
has tied into the infrastructure, and libvirt has been
updated to support the blkcg settings. Refer to:
https://lore.kernel.org/all/20210608043556.274139-1-muneendra.kumar@broadcom.com/
This patch set ties the nvme-fc transport into the blkcg infrastructure
so that vmid tags can be added to nvme traffic. The patch set also
updates the lpfc driver to utilize the nvme-fc transport addition.
Although the patch adds a nvme interface, it is being sent to the SCSI
maintainers tree due to the lpfc dependencies. As there is no other
consumer of the new interface, when the scsi tree merges with mainline,
the new interface will be picked up there.
Patches cut against scsi 5.19/scsi-queue tree with lpfc 14.2.0.3 patches
included.
V2:
Revised the first patch which calls blkcg_get_fc_appid().
Fixes build errors when merged with
blk-cgroup: move blkcg_{get,set}_fc_appid out of line
commit db05628435aa
James Smart (3):
lpfc: commonize VMID code location
lpfc: rework lpfc_vmid_get_appid() to be protocol independent
lpfc: Add support for vmid tagging of NVMe I/Os
Muneendra (1):
nvme-fc: Add new routine nvme_fc_io_getuuid
drivers/nvme/host/fc.c | 18 +++
drivers/scsi/lpfc/Makefile | 2 +-
drivers/scsi/lpfc/lpfc_crtn.h | 3 +
drivers/scsi/lpfc/lpfc_nvme.c | 45 ++++++
drivers/scsi/lpfc/lpfc_scsi.c | 263 +-----------------------------
drivers/scsi/lpfc/lpfc_vmid.c | 288 +++++++++++++++++++++++++++++++++
include/linux/nvme-fc-driver.h | 14 ++
7 files changed, 373 insertions(+), 260 deletions(-)
create mode 100644 drivers/scsi/lpfc/lpfc_vmid.c
--
2.26.2
next reply other threads:[~2022-05-19 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 12:31 James Smart [this message]
2022-05-19 12:31 ` [PATCH v2 1/4] nvme-fc: Add new routine nvme_fc_io_getuuid James Smart
2022-05-19 12:31 ` [PATCH v2 2/4] lpfc: commonize VMID code location James Smart
2022-05-19 12:31 ` [PATCH v2 3/4] lpfc: rework lpfc_vmid_get_appid() to be protocol independent James Smart
2022-05-19 12:31 ` [PATCH v2 4/4] lpfc: Add support for vmid tagging of NVMe I/Os James Smart
2022-05-20 0:25 ` [PATCH v2 0/4] Add VMID support to nvme-fc transport and lpfc driver Martin K. Petersen
2022-05-24 3:27 ` Martin K. Petersen
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=20220519123110.17361-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.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).