From: Damien Le Moal <dlemoal@kernel.org>
To: Kamaljit Singh <kamaljit.singh1@wdc.com>,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: cassel@kernel.org
Subject: Re: [PATCH v2 1/3] nvme: add capability to connect to an admin controller
Date: Wed, 2 Jul 2025 11:11:35 +0900 [thread overview]
Message-ID: <22f8ec86-2d50-4237-9313-79bfc93c8e3d@kernel.org> (raw)
In-Reply-To: <20250702005830.889217-2-kamaljit.singh1@wdc.com>
On 7/2/25 09:58, Kamaljit Singh wrote:
> Suggested-by: Niklas Cassel <cassel@kernel.org>
>
> Add capability to connect to an administrative controller by
> preventing ioq creation for admin-controllers.
>
> * Add helper nvme_admin_ctrl() to check for an administrative controller
> * Add helper nvme_override_prohibited_io_queues() to override
> queue_count in nvme_ctrl
>
> Reference: NVMe Base rev 2.2, sec 3.1.3.4, fig 28.
>
> Signed-off-by: Kamaljit Singh <kamaljit.singh1@wdc.com>
> ---
> drivers/nvme/host/core.c | 21 +++++++++++++++++++++
> drivers/nvme/host/nvme.h | 1 +
> drivers/nvme/host/rdma.c | 2 ++
> drivers/nvme/host/tcp.c | 2 ++
> 4 files changed, 26 insertions(+)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index e533d791955d..a1155fb8d5be 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -3149,6 +3149,22 @@ static inline bool nvme_discovery_ctrl(struct nvme_ctrl *ctrl)
> return ctrl->opts && ctrl->opts->discovery_nqn;
> }
>
> +static inline bool nvme_admin_ctrl(struct nvme_ctrl *ctrl)
> +{
> + return (ctrl->cntrltype == NVME_CTRL_ADMIN);
No need for the parenthesis.
> +}
> +
> +/*
> + * An admin controller has one admin queue, but no I/O queues.
> + * Override queue_count so it only creates an admin queue.
> + */
> +void nvme_override_prohibited_io_queues(struct nvme_ctrl *ctrl)
> +{
> + if (nvme_admin_ctrl(ctrl))
> + ctrl->queue_count = 1;
> +}
> +EXPORT_SYMBOL_GPL(nvme_override_prohibited_io_queues);
Why not have this done in nvme_init_subsystem() ? That would avoid needing to
call this in all fabrics drivers.
> +
> static bool nvme_validate_cntlid(struct nvme_subsystem *subsys,
> struct nvme_ctrl *ctrl, struct nvme_id_ctrl *id)
> {
> @@ -3215,6 +3231,11 @@ static int nvme_init_subsystem(struct nvme_ctrl *ctrl, struct nvme_id_ctrl *id)
> kfree(subsys);
> return -EINVAL;
> }
> + if (nvme_admin_ctrl(ctrl))
> + dev_info(ctrl->device,
> + "Subsystem %s is an administrative controller",
> + subsys->subnqn);
We do not print an equivalent message for other subsystem controller types. So
drop this.
> +
> nvme_mpath_default_iopolicy(subsys);
>
> subsys->dev.class = &nvme_subsys_class;
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-07-02 2:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 0:58 [PATCH v2 0/3] Support for Administrative Controllers Kamaljit Singh
2025-07-02 0:58 ` [PATCH v2 1/3] nvme: add capability to connect to an admin controller Kamaljit Singh
2025-07-02 2:11 ` Damien Le Moal [this message]
2025-07-02 18:39 ` Kamaljit Singh
2025-07-03 9:04 ` hch
2025-07-03 8:55 ` Hannes Reinecke
2025-07-16 21:27 ` Kamaljit Singh
2025-07-02 0:58 ` [PATCH v2 2/3] nvme: prevent admin controller from smart log fetch (LID 2) Kamaljit Singh
2025-07-02 2:13 ` Damien Le Moal
2025-07-02 18:21 ` Kamaljit Singh
2025-07-03 8:56 ` Hannes Reinecke
2025-07-03 9:05 ` Christoph Hellwig
2025-07-02 0:58 ` [PATCH v2 3/3] nvme: prevent ioq creation for discovery controllers Kamaljit Singh
2025-07-02 2:18 ` Damien Le Moal
2025-07-02 18:09 ` Kamaljit Singh
2025-07-02 23:59 ` Damien Le Moal
2025-07-03 9:05 ` hch
2025-07-03 9:42 ` 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=22f8ec86-2d50-4237-9313-79bfc93c8e3d@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=cassel@kernel.org \
--cc=hch@lst.de \
--cc=kamaljit.singh1@wdc.com \
--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 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).