[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z-pDY0aNYLgtiCUc@ryzen>
Date: Mon, 31 Mar 2025 07:25:23 +0000
From: Niklas Cassel <Niklas.Cassel@....com>
To: Kamaljit Singh <Kamaljit.Singh1@....com>
CC: "kbusch@...nel.org" <kbusch@...nel.org>, "axboe@...nel.dk"
<axboe@...nel.dk>, hch <hch@....de>, "sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Damien Le Moal
<Damien.LeMoal@....com>
Subject: Re: [PATCH v1 1/1] nvme: add admin controller support. prohibit ioq
creation for admin & disco ctrlrs
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@...nel.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@....com>
Kind regards,
Niklas
Powered by blists - more mailing lists