From: Wenchao Hao <haowenchao2@huawei.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: "James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<louhongxiang@huawei.com>
Subject: Re: [PATCH 1/2] scsi: core: cleanup scsi_dev_queue_ready()
Date: Sun, 24 Sep 2023 15:49:21 +0800 [thread overview]
Message-ID: <236310e2-b253-553e-d210-4a4928ed8ec8@huawei.com> (raw)
In-Reply-To: <7a11374c-4e8e-b7f9-aca4-55686a6ec501@huawei.com>
On 2023/9/24 14:27, Wenchao Hao wrote:
> On 2023/9/22 20:50, Damien Le Moal wrote:
>> On 2023/09/22 2:38, Wenchao Hao wrote:
>>> This is just a cleanup for scsi_dev_queue_ready() to avoid
>>> redundant goto and if statement, it did not change the origin
>>> logic.
>>>
>>> Signed-off-by: Wenchao Hao <haowenchao2@huawei.com>
>>> ---
>>> drivers/scsi/scsi_lib.c | 35 ++++++++++++++++++-----------------
>>> 1 file changed, 18 insertions(+), 17 deletions(-)
>>>
>>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>>> index ca5eb058d5c7..f3e388127dbd 100644
>>> --- a/drivers/scsi/scsi_lib.c
>>> +++ b/drivers/scsi/scsi_lib.c
>>> @@ -1254,28 +1254,29 @@ static inline int scsi_dev_queue_ready(struct request_queue *q,
>>> int token;
>>> token = sbitmap_get(&sdev->budget_map);
>>> - if (atomic_read(&sdev->device_blocked)) {
>>> - if (token < 0)
>>> - goto out;
>>> + if (token < 0)
>>> + return -1;
>>
>> This is changing how this function works...
>>
>
> I don't think so...
> The origin function flow:
>
> static inline int scsi_dev_queue_ready(struct request_queue *q,
> struct scsi_device *sdev)
> {
> ...
> token = sbitmap_get(&sdev->budget_map);
> if (atomic_read(&sdev->device_blocked)) {
> if (token < 0)
> goto out;
> }
> return token;
> out:
> return -1
> }
>
> If the token is less than 0, it would always return -1. So we can found
> it's not necessary to check token after atomic_read().
>
>>> - if (scsi_device_busy(sdev) > 1)
>>> - goto out_dec;
>>> + /*
>>> + * 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;
>>
>> ...because you reversed the tests order.
>
> As explained in comment, the device_blocked is not set at mostly time,
> so when it's not set, just return the token.
>
>>> - /*
>>> - * 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) {
>>
>> And here too, you are changing how the function works. The atomic_dec may not be
>> done if the first condition is true.
>>
>
> the origin flow would not call atomic_dec_return() too when condition
> "scsi_device_busy(sdev) > 1" is true like following:
>
> static inline int scsi_dev_queue_ready(struct request_queue *q,
> struct scsi_device *sdev)
> {
> ...
> if (atomic_read(&sdev->device_blocked)) {
> if (scsi_device_busy(sdev) > 1)
> goto out_dec;
>
> /*
> * 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"));
> }
> return token;
> out_dec:
> if (token >= 0)
> sbitmap_put(&sdev->budget_map, token);
> out:
> return -1;
> }
>
> Here is the function before and after my change:
>
> The old function:
> static inline int scsi_dev_queue_ready(struct request_queue *q,
> struct scsi_device *sdev)
> {
> int token;
>
> token = sbitmap_get(&sdev->budget_map);
> if (token < 0)
> return -1;
>
> /*
> * 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;
>
> /*
> * 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;
> }
>
> SCSI_LOG_MLQUEUE(3, sdev_printk(KERN_INFO, sdev,
> "unblocking device at zero depth\n"));
>
> return token;
> }
>
Sorry, I paste wrong for old function, the old function is:
static inline int scsi_dev_queue_ready(struct request_queue *q,
struct scsi_device *sdev)
{
int token;
token = sbitmap_get(&sdev->budget_map);
if (atomic_read(&sdev->device_blocked)) {
if (token < 0)
goto out;
if (scsi_device_busy(sdev) > 1)
goto out_dec;
/*
* 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"));
}
return token;
out_dec:
if (token >= 0)
sbitmap_put(&sdev->budget_map, token);
out:
return -1;
}
next prev parent reply other threads:[~2023-09-24 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 9:38 [PATCH 0/2] cleanup patch Wenchao Hao
2023-09-22 9:38 ` [PATCH 1/2] scsi: core: cleanup scsi_dev_queue_ready() Wenchao Hao
2023-09-22 12:50 ` Damien Le Moal
2023-09-24 6:27 ` Wenchao Hao
2023-09-24 7:49 ` Wenchao Hao [this message]
2023-10-11 12:37 ` Wenchao Hao
2023-09-22 9:38 ` [PATCH 2/2] scsi: Add comment of target_destroy in scsi_host_template Wenchao Hao
2023-09-22 14:53 ` Bart Van Assche
2023-09-24 6:29 ` 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=236310e2-b253-553e-d210-4a4928ed8ec8@huawei.com \
--to=haowenchao2@huawei.com \
--cc=dlemoal@kernel.org \
--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®