public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Muneendra <muneendra.kumar@broadcom.com>
To: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
	tj@kernel.org, linux-nvme@lists.infradead.org, hare@suse.de
Cc: Muneendra <muneendra.kumar@broadcom.com>,
	jsmart2021@gmail.com, mkumar@redhat.com, emilne@redhat.com
Subject: [PATCH v7 16/16] scsi: Made changes in Kconfig to select BLK_CGROUP_FC_APPID
Date: Thu,  7 Jan 2021 03:30:30 +0530	[thread overview]
Message-ID: <1609970430-19084-17-git-send-email-muneendra.kumar@broadcom.com> (raw)
In-Reply-To: <1609970430-19084-1-git-send-email-muneendra.kumar@broadcom.com>

Added a new config FC_APPID to select BLK_CGROUP_FC_APPID
which Enable support to track FC io Traffic.

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Muneendra <muneendra.kumar@broadcom.com>

---
v7:
Modified the Kconfig comments

v6:
Modified the Kconfig comments

v5:
No change

v4:
Addressed the error reported by kernel test robot

v3:
New patch
---
 drivers/scsi/Kconfig | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index 701b61ec76ee..500f88ce29e3 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -235,6 +235,19 @@ config SCSI_FC_ATTRS
 	  each attached FiberChannel device to sysfs, say Y.
 	  Otherwise, say N.
 
+config FC_APPID
+	bool "Enable support to track FC I/O Traffic"
+	depends on BLOCK && BLK_CGROUP
+	depends on SCSI
+	select BLK_CGROUP_FC_APPID
+	default y
+	help
+	  If you say Y here, it enables the support to track
+	  FC I/O traffic over fabric. It enables the Fabric and the
+	  storage targets to identify, monitor, and handle FC traffic
+	  based on VM tags by inserting application specific
+	  identification into the FC frame.
+
 config SCSI_ISCSI_ATTRS
 	tristate "iSCSI Transport Attributes"
 	depends on SCSI && NET
-- 
2.26.2


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      parent reply	other threads:[~2021-01-07  5:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 22:00 [PATCH v7 00/16] blkcg:Support to track FC storage blk io traffic Muneendra
2021-01-06 22:00 ` [PATCH v7 01/16] cgroup: Added cgroup_get_from_id Muneendra
2021-01-11  7:29   ` Hannes Reinecke
2021-01-06 22:00 ` [PATCH v7 02/16] blkcg: Added a app identifier support for blkcg Muneendra
2021-01-11  7:30   ` Hannes Reinecke
2021-01-06 22:00 ` [PATCH v7 03/16] nvme: Added a newsysfs attribute appid_store Muneendra
2021-01-11  7:31   ` Hannes Reinecke
2021-01-06 22:00 ` [PATCH v7 04/16] lpfc: vmid: Add the datastructure for supporting VMID in lpfc Muneendra
2021-01-11  7:32   ` Hannes Reinecke
2021-01-06 22:00 ` [PATCH v7 05/16] lpfc: vmid: Supplementary data structures for vmid and APIs Muneendra
2021-01-11  7:33   ` Hannes Reinecke
2021-01-06 22:00 ` [PATCH v7 06/16] lpfc: vmid: Forward declarations for APIs Muneendra
2021-01-11  7:35   ` Hannes Reinecke
2021-01-06 22:00 ` [PATCH v7 07/16] lpfc: vmid: VMID params initialization Muneendra
2021-01-06 22:00 ` [PATCH v7 08/16] lpfc: vmid: Add support for vmid in mailbox command, does vmid resource allocation and vmid cleanup Muneendra
2021-01-06 22:00 ` [PATCH v7 09/16] lpfc: vmid: Implements ELS commands for appid patch Muneendra
2021-01-06 22:00 ` [PATCH v7 10/16] lpfc: vmid: Functions to manage vmids Muneendra
2021-01-06 22:00 ` [PATCH v7 11/16] lpfc: vmid: Implements CT commands for appid Muneendra
2021-01-06 22:00 ` [PATCH v7 12/16] lpfc: vmid: Appends the vmid in the wqe before sending Muneendra
2021-01-06 22:00 ` [PATCH v7 13/16] lpfc: vmid: Timeout implementation for vmid Muneendra
2021-01-06 22:00 ` [PATCH v7 14/16] lpfc: vmid: Adding qfpa and vmid timeout check in worker thread Muneendra
2021-01-06 22:00 ` [PATCH v7 15/16] lpfc: vmid: Introducing vmid in io path Muneendra
2021-01-06 22:00 ` Muneendra [this message]

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=1609970430-19084-17-git-send-email-muneendra.kumar@broadcom.com \
    --to=muneendra.kumar@broadcom.com \
    --cc=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=jsmart2021@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkumar@redhat.com \
    --cc=tj@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