From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbusch@kernel.org, chaitanya.kulkarni@wdc.com, sagi@grimberg.me,
linux-nvme@lists.infradead.org, oren@nvidia.com
Subject: Re: [PATCH 1/1] nvmet: allow setting model_number once
Date: Wed, 24 Feb 2021 11:59:22 +0200 [thread overview]
Message-ID: <119dbae3-9dc8-a5d8-0f35-20d619931db6@nvidia.com> (raw)
In-Reply-To: <20210224094347.GA5965@lst.de>
On 2/24/2021 11:43 AM, Christoph Hellwig wrote:
> So looking at this and Chaitanya patch I think this version simplifies
> things quite nicely, and it also happens to get rid of the RCU annotation
> sparse warnings.
>
> Let me know what you think of the incremental cleanup and micro-opimization
> below, though:
>
>
> diff --git a/drivers/nvme/target/admin-cmd.c b/drivers/nvme/target/admin-cmd.c
> index 3da285e22e9209..2ca13dd7e7b88a 100644
> --- a/drivers/nvme/target/admin-cmd.c
> +++ b/drivers/nvme/target/admin-cmd.c
> @@ -313,34 +313,40 @@ static void nvmet_execute_get_log_page(struct nvmet_req *req)
> nvmet_req_complete(req, NVME_SC_INVALID_FIELD | NVME_SC_DNR);
> }
>
> -static int nvmet_id_set_model_number(struct nvme_id_ctrl *id,
> - struct nvmet_subsys *subsys)
> +static u16 nvmet_set_model_number(struct nvme_id_ctrl *id,
> + struct nvmet_subsys *subsys)
> {
> - int ret = 0;
> + u16 status = 0;
>
> mutex_lock(&subsys->lock);
> if (!subsys->model_number) {
> - subsys->model_number = kstrdup(NVMET_DEFAULT_CTRL_MODEL,
> - GFP_KERNEL);
> - if (!subsys->model_number) {
> - ret = -ENOMEM;
> - goto out_unlock;
> - }
> + subsys->model_number =
> + kstrdup(NVMET_DEFAULT_CTRL_MODEL, GFP_KERNEL);
> + if (!subsys->model_number)
> + status = NVME_SC_INTERNAL;
> }
> - memcpy_and_pad(id->mn, sizeof(id->mn), subsys->model_number,
> - strlen(subsys->model_number), ' ');
> -out_unlock:
> mutex_unlock(&subsys->lock);
> - return ret;
> +
> + return status;
> }
>
> static void nvmet_execute_identify_ctrl(struct nvmet_req *req)
> {
> struct nvmet_ctrl *ctrl = req->sq->ctrl;
> + struct nvmet_subsys *subsys = ctrl->subsys;
> struct nvme_id_ctrl *id;
> u32 cmd_capsule_size;
> u16 status = 0;
> - int ret;
> +
> + /*
> + * If there is no model number yet, so it now. It will then remain
> + * stable for the life time of the subsystem.
> + */
> + if (!subsys->model_number) {
> + status = nvmet_set_model_number(id, subsys);
you don't need the id argument here.
Otherwise looks good and it can be squashed to my patch.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-02-24 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 18:11 [PATCH 1/1] nvmet: allow setting model_number once Max Gurtovoy
2021-02-18 3:17 ` Chaitanya Kulkarni
2021-02-18 9:51 ` Max Gurtovoy
2021-02-24 9:43 ` Christoph Hellwig
2021-02-24 9:59 ` Max Gurtovoy [this message]
2021-02-24 10:00 ` Christoph Hellwig
2021-02-24 10:02 ` Max Gurtovoy
2021-02-24 10:04 ` Christoph Hellwig
2021-02-24 12:57 ` Max Gurtovoy
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=119dbae3-9dc8-a5d8-0f35-20d619931db6@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=oren@nvidia.com \
--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