From: Sagi Grimberg <sagi@grimberg.me>
To: Aleksandr Miloserdov <a.miloserdov@yadro.com>,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-nvme@lists.infradead.org, linux@yadro.com,
Konstantin Shelekhin <k.shelekhin@yadro.com>,
Dmitriy Bogdanov <d.bogdanov@yadro.com>
Subject: Re: [PATCH v2 1/2] nvmet: expose IEEE OUI to configfs
Date: Tue, 15 Nov 2022 16:05:14 +0200 [thread overview]
Message-ID: <1243d214-e399-237f-e70d-bb4541a66b28@grimberg.me> (raw)
In-Reply-To: <20221115115810.75848-2-a.miloserdov@yadro.com>
> Allow user to set OUI for the controller vendor.
>
> Reviewed-by: Konstantin Shelekhin <k.shelekhin@yadro.com>
> Reviewed-by: Dmitriy Bogdanov <d.bogdanov@yadro.com>
> Signed-off-by: Aleksandr Miloserdov <a.miloserdov@yadro.com>
> ---
> drivers/nvme/target/admin-cmd.c | 7 ++---
> drivers/nvme/target/configfs.c | 49 +++++++++++++++++++++++++++++++++
> drivers/nvme/target/core.c | 2 ++
> drivers/nvme/target/nvmet.h | 1 +
> 4 files changed, 54 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/nvme/target/admin-cmd.c b/drivers/nvme/target/admin-cmd.c
> index c8a061ce3ee5..48a2f587f38a 100644
> --- a/drivers/nvme/target/admin-cmd.c
> +++ b/drivers/nvme/target/admin-cmd.c
> @@ -372,6 +372,8 @@ static void nvmet_execute_identify_ctrl(struct nvmet_req *req)
> memcpy_and_pad(id->fr, sizeof(id->fr),
> UTS_RELEASE, strlen(UTS_RELEASE), ' ');
>
> + put_unaligned_le24(subsys->ieee_oui, id->ieee);
> +
Any particular reason why it is placed here and not where the comment
was?
> id->rab = 6;
>
> if (nvmet_is_disc_subsys(ctrl->subsys))
> @@ -379,11 +381,6 @@ static void nvmet_execute_identify_ctrl(struct nvmet_req *req)
> else
> id->cntrltype = NVME_CTRL_IO;
>
> - /*
> - * XXX: figure out how we can assign a IEEE OUI, but until then
> - * the safest is to leave it as zeroes.
> - */
> -
> /* we support multiple ports, multiples hosts and ANA: */
> id->cmic = NVME_CTRL_CMIC_MULTI_PORT | NVME_CTRL_CMIC_MULTI_CTRL |
> NVME_CTRL_CMIC_ANA;
> diff --git a/drivers/nvme/target/configfs.c b/drivers/nvme/target/configfs.c
> index 89242b0f8614..ad62e36ec997 100644
> --- a/drivers/nvme/target/configfs.c
> +++ b/drivers/nvme/target/configfs.c
> @@ -1265,6 +1265,54 @@ static ssize_t nvmet_subsys_attr_model_store(struct config_item *item,
> }
> CONFIGFS_ATTR(nvmet_subsys_, attr_model);
>
> +static ssize_t nvmet_subsys_attr_ieee_oui_show(struct config_item *item,
> + char *page)
> +{
> + struct nvmet_subsys *subsys = to_subsys(item);
> +
> + return sysfs_emit(page, "0x%06x\n", subsys->ieee_oui);
> +}
> +
> +static ssize_t nvmet_subsys_attr_ieee_oui_store_locked(struct nvmet_subsys *subsys,
> + const char *page, size_t count)
> +{
> + uint32_t val = 0;
> + int ret;
> +
> + if (subsys->subsys_discovered) {
> + pr_err("Can't set IEEE OUI. 0x%06x is already assigned\n",
> + subsys->ieee_oui);
> + return -EINVAL;
> + }
> +
> + ret = kstrtou32(page, 0, &val);
> + if (ret < 0)
> + return ret;
> +
> + if (val >= 0x1000000)
> + return -EINVAL;
> +
> + subsys->ieee_oui = val;
> +
> + return count;
> +}
> +
> +static ssize_t nvmet_subsys_attr_ieee_oui_store(struct config_item *item,
> + const char *page, size_t count)
> +{
> + struct nvmet_subsys *subsys = to_subsys(item);
> + ssize_t ret;
> +
> + down_write(&nvmet_config_sem);
> + mutex_lock(&subsys->lock);
> + ret = nvmet_subsys_attr_ieee_oui_store_locked(subsys, page, count);
> + mutex_unlock(&subsys->lock);
> + up_write(&nvmet_config_sem);
> +
> + return ret;
> +}
> +CONFIGFS_ATTR(nvmet_subsys_, attr_ieee_oui);
> +
> #ifdef CONFIG_BLK_DEV_INTEGRITY
> static ssize_t nvmet_subsys_attr_pi_enable_show(struct config_item *item,
> char *page)
> @@ -1323,6 +1371,7 @@ static struct configfs_attribute *nvmet_subsys_attrs[] = {
> &nvmet_subsys_attr_attr_cntlid_max,
> &nvmet_subsys_attr_attr_model,
> &nvmet_subsys_attr_attr_qid_max,
> + &nvmet_subsys_attr_attr_ieee_oui,
> #ifdef CONFIG_BLK_DEV_INTEGRITY
> &nvmet_subsys_attr_attr_pi_enable,
> #endif
> diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
> index aecb5853f8da..ec697ceeac56 100644
> --- a/drivers/nvme/target/core.c
> +++ b/drivers/nvme/target/core.c
> @@ -1561,6 +1561,8 @@ struct nvmet_subsys *nvmet_subsys_alloc(const char *subsysnqn,
> goto free_subsys;
> }
>
> + subsys->ieee_oui = 0;
> +
> switch (type) {
> case NVME_NQN_NVME:
> subsys->max_qid = NVMET_NR_QUEUES;
> diff --git a/drivers/nvme/target/nvmet.h b/drivers/nvme/target/nvmet.h
> index dfe3894205aa..1dc0ff8b2f3f 100644
> --- a/drivers/nvme/target/nvmet.h
> +++ b/drivers/nvme/target/nvmet.h
> @@ -264,6 +264,7 @@ struct nvmet_subsys {
> struct config_group allowed_hosts_group;
>
> char *model_number;
> + u32 ieee_oui;
>
> #ifdef CONFIG_NVME_TARGET_PASSTHRU
> struct nvme_ctrl *passthru_ctrl;
next prev parent reply other threads:[~2022-11-15 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 11:58 [PATCH v2 0/2] Allow user to set nvmet firmware revision and IEEE OUI Aleksandr Miloserdov
2022-11-15 11:58 ` [PATCH v2 1/2] nvmet: expose IEEE OUI to configfs Aleksandr Miloserdov
2022-11-15 14:05 ` Sagi Grimberg [this message]
2022-11-16 6:58 ` Christoph Hellwig
2022-11-16 11:58 ` Aleksandr Miloserdov
2022-11-20 11:36 ` Sagi Grimberg
2022-11-15 11:58 ` [PATCH v2 2/2] nvmet: expose firmware revision " Aleksandr Miloserdov
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=1243d214-e399-237f-e70d-bb4541a66b28@grimberg.me \
--to=sagi@grimberg.me \
--cc=a.miloserdov@yadro.com \
--cc=d.bogdanov@yadro.com \
--cc=hch@lst.de \
--cc=k.shelekhin@yadro.com \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux@yadro.com \
/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