From: "hch@lst.de" <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: sasaki tatsuya <tatsuya6.sasaki@kioxia.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] nvme: update keep alive interval when kato is modified
Date: Wed, 25 Aug 2021 11:04:24 +0200 [thread overview]
Message-ID: <20210825090424.GA468@lst.de> (raw)
In-Reply-To: <05033836-83b9-c060-0348-774a02b60d01@grimberg.me>
On Tue, Aug 24, 2021 at 01:41:44PM -0700, Sagi Grimberg wrote:
>> +{
>> + /*
>> + * Keep alive commands interval on the host should be updated
>> + * when KATO is modified by Set Features commands.
>> + */
>> + if (cmd->opcode == nvme_admin_set_features &&
>> + (cmd->cdw10 & 0xFF) == NVME_FEAT_KATO) {
>> + /* ms -> s */
>
> no need for this comment.
>
>> + unsigned int new_kato = DIV_ROUND_UP(cmd->cdw11, 1000);
>> +
>> + nvme_update_keep_alive(ctrl, new_kato);
>
> I think you can now inline nvme_update_keep_alive here, no need to keep
> it in a function.
Actually, іf thinking ahead I think one helper per fixup would be really
useful to keep the code organized. But the DIV_ROUND_UP should move into
nvme_update_keep_alive to keep it self-contained.
We can then restructure the caller a bit to make it easier to expand:
switch (cmd->opcode) {
case nvme_admin_set_features:
switch (cmd->cdw10 & 0xff) {
case NVME_FEAT_KATO:
nvme_update_keep_alive(ctrl, cmd);
break;
}
}
next prev parent reply other threads:[~2021-08-25 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 5:44 [PATCH v2] nvme: update keep alive interval when kato is modified sasaki tatsuya
2021-08-24 20:41 ` Sagi Grimberg
2021-08-25 8:26 ` sasaki tatsuya
2021-08-25 9:04 ` hch [this message]
2021-08-25 8:53 ` hch
2021-08-25 15:51 ` Hannes Reinecke
2021-08-30 11:27 ` sasaki tatsuya
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=20210825090424.GA468@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=tatsuya6.sasaki@kioxia.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