From: Muneendra Kumar M <muneendra.kumar@broadcom.com> To: Benjamin Block <lkml@mageta.org> Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, tj@kernel.org, linux-nvme@lists.infradead.org, hare@suse.de, jsmart2021@gmail.com, emilne@redhat.com, mkumar@redhat.com, Benjamin Block <bblock@linux.ibm.com> Subject: RE: [PATCH v9 03/13] nvme: Added a newsysfs attribute appid_store Date: Tue, 20 Apr 2021 12:24:41 +0530 [thread overview] Message-ID: <a6497bd924795a5a9279b893b0d83baf@mail.gmail.com> (raw) In-Reply-To: <YHxRK33kf7OSVlxf@chlorum.ategam.org> [-- Attachment #1: Type: text/plain, Size: 1544 bytes --] Hi Benjamin, >> --- >> drivers/nvme/host/fc.c | 73 >> +++++++++++++++++++++++++++++++++++++++++- >> 1 file changed, 72 insertions(+), 1 deletion(-) >Hmm, I wonder why only NVMe-FC? Or is this just for the moment? We also have the FC transport class for SCSI; I assume this could feed the same IDs into the LLDs. At present it supports only for SCSI-FC . In future we are adding the support for NVMe-FC But to make it generic and avoid duplication we added this under /sys/class/fc . Ewan was mentioning that at some point there is a plan to decouple the FC transport somewhat so that there is a layer that represents the FC stuff regardless of the FC4 type (SCSI, NVMe). When we have this layer we can move the things accordingly. Regards, Muneendra. -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4220 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Muneendra Kumar M <muneendra.kumar@broadcom.com> To: Benjamin Block <lkml@mageta.org> Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, tj@kernel.org, linux-nvme@lists.infradead.org, hare@suse.de, jsmart2021@gmail.com, emilne@redhat.com, mkumar@redhat.com, Benjamin Block <bblock@linux.ibm.com> Subject: RE: [PATCH v9 03/13] nvme: Added a newsysfs attribute appid_store Date: Tue, 20 Apr 2021 12:24:41 +0530 [thread overview] Message-ID: <a6497bd924795a5a9279b893b0d83baf@mail.gmail.com> (raw) In-Reply-To: <YHxRK33kf7OSVlxf@chlorum.ategam.org> [-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --] Hi Benjamin, >> --- >> drivers/nvme/host/fc.c | 73 >> +++++++++++++++++++++++++++++++++++++++++- >> 1 file changed, 72 insertions(+), 1 deletion(-) >Hmm, I wonder why only NVMe-FC? Or is this just for the moment? We also have the FC transport class for SCSI; I assume this could feed the same IDs into the LLDs. At present it supports only for SCSI-FC . In future we are adding the support for NVMe-FC But to make it generic and avoid duplication we added this under /sys/class/fc . Ewan was mentioning that at some point there is a plan to decouple the FC transport somewhat so that there is a layer that represents the FC stuff regardless of the FC4 type (SCSI, NVMe). When we have this layer we can move the things accordingly. Regards, Muneendra. -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. [-- Attachment #1.2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4220 bytes --] [-- Attachment #2: Type: text/plain, Size: 158 bytes --] _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-20 6:54 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 23:06 [PATCH v9 00/13] blkcg:Support to track FC storage blk io traffic Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-06 23:06 ` [PATCH v9 01/13] cgroup: Added cgroup_get_from_id Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:26 ` Hannes Reinecke 2021-04-08 8:26 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 02/13] blkcg: Added a app identifier support for blkcg Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:26 ` Hannes Reinecke 2021-04-08 8:26 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 03/13] nvme: Added a newsysfs attribute appid_store Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-18 15:32 ` Benjamin Block 2021-04-18 15:32 ` Benjamin Block 2021-04-20 6:54 ` Muneendra Kumar M [this message] 2021-04-20 6:54 ` Muneendra Kumar M 2021-04-20 11:09 ` Benjamin Block 2021-04-20 11:09 ` Benjamin Block 2021-04-22 23:29 ` James Smart 2021-04-22 23:29 ` James Smart 2021-04-23 10:14 ` Benjamin Block 2021-04-23 10:14 ` Benjamin Block 2021-04-06 23:06 ` [PATCH v9 04/13] lpfc: vmid: Add the datastructure for supporting VMID in lpfc Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:28 ` Hannes Reinecke 2021-04-08 8:28 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 05/13] lpfc: vmid: VMID params initialization Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:29 ` Hannes Reinecke 2021-04-08 8:29 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 06/13] lpfc: vmid: Add support for vmid in mailbox command, does vmid resource allocation and vmid cleanup Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:32 ` Hannes Reinecke 2021-04-08 8:32 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 07/13] lpfc: vmid: Implements ELS commands for appid patch Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:34 ` Hannes Reinecke 2021-04-08 8:34 ` Hannes Reinecke 2021-04-20 12:38 ` Benjamin Block 2021-04-20 12:38 ` Benjamin Block 2021-04-21 22:55 ` James Smart 2021-04-21 22:55 ` James Smart 2021-04-22 9:28 ` Benjamin Block 2021-04-22 9:28 ` Benjamin Block 2021-04-06 23:06 ` [PATCH v9 08/13] lpfc: vmid: Functions to manage vmids Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:35 ` Hannes Reinecke 2021-04-08 8:35 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 09/13] lpfc: vmid: Implements CT commands for appid Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:37 ` Hannes Reinecke 2021-04-08 8:37 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 10/13] lpfc: vmid: Appends the vmid in the wqe before sending Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-06 23:06 ` [PATCH v9 11/13] lpfc: vmid: Timeout implementation for vmid Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:38 ` Hannes Reinecke 2021-04-08 8:38 ` Hannes Reinecke 2021-04-06 23:06 ` [PATCH v9 12/13] lpfc: vmid: Adding qfpa and vmid timeout check in worker thread Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-06 23:06 ` [PATCH v9 13/13] lpfc: vmid: Introducing vmid in io path Muneendra 2021-04-06 23:06 ` Muneendra 2021-04-08 8:46 ` Hannes Reinecke 2021-04-08 8:46 ` Hannes Reinecke 2021-04-10 15:00 ` James Smart 2021-04-10 15:00 ` James Smart 2021-04-12 5:27 ` Hannes Reinecke 2021-04-12 5:27 ` Hannes Reinecke
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=a6497bd924795a5a9279b893b0d83baf@mail.gmail.com \ --to=muneendra.kumar@broadcom.com \ --cc=bblock@linux.ibm.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=lkml@mageta.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.