From: Nilay Shroff <nilay@linux.ibm.com>
To: Damien Le Moal <dlemoal@kernel.org>, linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me, axboe@fb.com,
chaitanyak@nvidia.com, gjoyce@linux.ibm.com
Subject: Re: [PATCH v2 3/3] nvme: use helper nvme_ctrl_state in nvme_keep_alive_finish function
Date: Tue, 8 Oct 2024 11:06:37 +0530 [thread overview]
Message-ID: <48689ead-f3c3-44a3-b1fe-be3ff01babaf@linux.ibm.com> (raw)
In-Reply-To: <4e159735-7703-4f39-b98e-25c21824506c@kernel.org>
On 10/8/24 10:49, Damien Le Moal wrote:
> On 10/8/24 13:13, Nilay Shroff wrote:
>> We no more need acquiring ctrl->lock for accessing the NVMe controller
>> state and instead we can now use the helper nvme_ctrl_state. So replace
>> the ctrl->lock from nvme_keep_alive_finish function with nvme_ctrl_state
>> call.
>>
>> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
>> ---
>> drivers/nvme/host/core.c | 7 ++-----
>> 1 file changed, 2 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
>> index 736adbf65ef5..5a690cf16e5e 100644
>> --- a/drivers/nvme/host/core.c
>> +++ b/drivers/nvme/host/core.c
>> @@ -1296,10 +1296,10 @@ static void nvme_keep_alive_finish(struct request *rq,
>> blk_status_t status,
>> struct nvme_ctrl *ctrl)
>> {
>> - unsigned long flags;
>> bool startka = false;
>> unsigned long rtt = jiffies - (rq->deadline - rq->timeout);
>> unsigned long delay = nvme_keep_alive_work_period(ctrl);
>> + enum nvme_ctrl_state state = nvme_ctrl_state(ctrl);
>>
>> /*
>> * Subtract off the keepalive RTT so nvme_keep_alive_work runs
>> @@ -1322,11 +1322,8 @@ static void nvme_keep_alive_finish(struct request *rq,
>>
>> ctrl->ka_last_check_time = jiffies;
>> ctrl->comp_seen = false;
>> - spin_lock_irqsave(&ctrl->lock, flags);
>> - if (ctrl->state == NVME_CTRL_LIVE ||
>> - ctrl->state == NVME_CTRL_CONNECTING)
>> + if (state == NVME_CTRL_LIVE || state == NVME_CTRL_CONNECTING)
>> startka = true;
>
> startka = state == NVME_CTRL_LIVE || state == NVME_CTRL_CONNECTING;
>
> But do you even need that variable now ? The below "if (startka)" could be
> replaced with "if (state == NVME_CTRL_LIVE || state == NVME_CTRL_CONNECTING)", no ?
>
>> - spin_unlock_irqrestore(&ctrl->lock, flags);
>> if (startka)
>> queue_delayed_work(nvme_wq, &ctrl->ka_work, delay);
>> }
>
>
Oops yeah you were correct, we don't need @startka. I will spin a new version.
Thanks for your comment!
--Nilay
prev parent reply other threads:[~2024-10-08 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 4:13 [PATCH v2 0/3] nvme: system fault while shutting down fabric controller Nilay Shroff
2024-10-08 4:13 ` [PATCH v2 1/3] nvme-loop: flush off pending I/O while shutting down loop controller Nilay Shroff
2024-10-08 4:13 ` [PATCH v2 2/3] nvme: make keep-alive synchronous operation Nilay Shroff
2024-10-08 4:13 ` [PATCH v2 3/3] nvme: use helper nvme_ctrl_state in nvme_keep_alive_finish function Nilay Shroff
2024-10-08 5:19 ` Damien Le Moal
2024-10-08 5:36 ` Nilay Shroff [this message]
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=48689ead-f3c3-44a3-b1fe-be3ff01babaf@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@fb.com \
--cc=chaitanyak@nvidia.com \
--cc=dlemoal@kernel.org \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@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