From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Kamaljit Singh <Kamaljit.Singh1@wdc.com>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>, hch <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH v1 1/1] nvme: add admin controller support. prohibit ioq creation for admin & disco ctrlrs
Date: Mon, 31 Mar 2025 07:25:23 +0000 [thread overview]
Message-ID: <Z-pDY0aNYLgtiCUc@ryzen> (raw)
In-Reply-To: <20250328213640.798910-2-kamaljit.singh1@wdc.com>
Hello Kamaljit,
On Fri, Mar 28, 2025 at 02:36:40PM -0700, Kamaljit Singh wrote:
Like Damien said,
> Added capability to connect to an administrative controller by
> preventing ioq creation for admin-controllers.
patch 2/4,
I think I deserve:
Suggested-by: Niklas Cassel <cassel@kernel.org>
on this patch.
> Also prevent ioq creation for discovery-controllers as the spec
> prohibits them.
patch 3/4
>
> * Added nvme_admin_ctrl() to check for an administrative controller
This could be part of patch 2/4.
>
> * Renamed nvme_discovery_ctrl() to nvmf_discovery_ctrl() as discovery is
> more relevant to fabrics
patch 1/4, you need to move the function, but can keep the name.
>
> * Similar to a discovery ctrl, prevent an admin-ctrl from getting a
> smart log (LID=2). LID 2 is optional for admin controllers but in the
> future when we add support for the newly added LID=0 (supported log
> pages), we can make GLP accesses smarter by basing such calls on
> response from LID=0 reads.
patch 4/4
>
> Signed-off-by: Kamaljit Singh <kamaljit.singh1@wdc.com>
Kind regards,
Niklas
next prev parent reply other threads:[~2025-03-31 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 21:36 [PATCH v1 0/1] nvme: add admin controller support. prohibit ioq creation for admin & disco ctrlrs Kamaljit Singh
2025-03-28 21:36 ` [PATCH v1 1/1] " Kamaljit Singh
2025-03-28 22:09 ` Damien Le Moal
[not found] ` <BY5PR04MB6849189D63EBB6EF4B66AD42BCAD2@BY5PR04MB6849.namprd04.prod.outlook.com>
2025-04-01 22:47 ` Kamaljit Singh
2025-03-31 7:25 ` Niklas Cassel [this message]
[not found] ` <BY5PR04MB68491AD9C47CD7AB9B552098BCAC2@BY5PR04MB6849.namprd04.prod.outlook.com>
2025-04-01 22:52 ` Kamaljit Singh
2025-03-31 15:03 ` Keith Busch
2025-04-01 2:20 ` Chaitanya Kulkarni
2025-04-01 8:04 ` Niklas Cassel
[not found] ` <BY5PR04MB68496CB7512F91FEA30DFF86BCAC2@BY5PR04MB6849.namprd04.prod.outlook.com>
2025-04-01 22:57 ` Kamaljit Singh
2025-04-02 6:37 ` Niklas Cassel
2025-04-02 21:03 ` Kamaljit Singh
2025-04-03 4:49 ` Christoph Hellwig
2025-04-03 18:59 ` 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=Z-pDY0aNYLgtiCUc@ryzen \
--to=niklas.cassel@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Kamaljit.Singh1@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 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.