From: Bart Van Assche <bvanassche@acm.org>
To: Wenchao Hao <haowenchao2@huawei.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, louhongxiang@huawei.com
Subject: Re: [PATCH v2 1/2] scsi: core: cleanup scsi_dev_queue_ready()
Date: Tue, 17 Oct 2023 14:15:34 -0700 [thread overview]
Message-ID: <b3334a8c-fb48-4b98-8571-8d85cbd4ed1e@acm.org> (raw)
In-Reply-To: <20231016020847.1270258-2-haowenchao2@huawei.com>
On 10/15/23 19:08, Wenchao Hao wrote:
> + /*
> + * device_blocked is not set at mostly time, so check it first
> + * and return token when it is not set.
> + */
> + if (!atomic_read(&sdev->device_blocked))
> + return token;
This patch looks like an improvement to me. But I don't think that the
above comment is useful. I propose to move it into the patch
description.
> - /*
> - * unblock after device_blocked iterates to zero
> - */
> - if (atomic_dec_return(&sdev->device_blocked) > 0)
> - goto out_dec;
> - SCSI_LOG_MLQUEUE(3, sdev_printk(KERN_INFO, sdev,
> - "unblocking device at zero depth\n"));
> + /*
> + * unblock after device_blocked iterates to zero
> + */
> + if (scsi_device_busy(sdev) > 1 ||
> + atomic_dec_return(&sdev->device_blocked) > 0) {
> + sbitmap_put(&sdev->budget_map, token);
> + return -1;
> }
Please make the above comment match the new code, e.g. by changing it
into the following: "Only unblock if no other commands are pending and
if device_blocked has decreased to zero".
Thanks,
Bart.
next prev parent reply other threads:[~2023-10-17 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 2:08 [PATCH v2 0/2] cleanup patch Wenchao Hao
2023-10-16 2:08 ` [PATCH v2 1/2] scsi: core: cleanup scsi_dev_queue_ready() Wenchao Hao
2023-10-17 21:15 ` Bart Van Assche [this message]
2023-10-18 2:22 ` Wenchao Hao
2023-10-16 2:08 ` [PATCH v2 2/2] scsi: Add comment of target_destroy in scsi_host_template Wenchao Hao
2023-10-17 21:04 ` Bart Van Assche
2023-10-18 2:24 ` Wenchao Hao
2023-10-17 17:01 ` [PATCH v2 0/2] cleanup patch Wenchao Hao
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=b3334a8c-fb48-4b98-8571-8d85cbd4ed1e@acm.org \
--to=bvanassche@acm.org \
--cc=haowenchao2@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=louhongxiang@huawei.com \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®