[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf6452cd-b148-553c-781d-5c888537ac28@huawei.com>
Date: Mon, 27 Sep 2021 10:40:28 +0100
From: John Garry <john.garry@...wei.com>
To: Ming Lei <ming.lei@...hat.com>
CC: "axboe@...nel.dk" <axboe@...nel.dk>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"hare@...e.de" <hare@...e.de>
Subject: Re: [PATCH v4 11/13] blk-mq: Refactor and rename
blk_mq_free_map_and_{requests->rqs}()
On 27/09/2021 10:19, Ming Lei wrote:
>> However, apart from this, I can change __blk_mq_free_map_and_rqs() to
>> NULLify set->tags[i], as it is always passed set->tags[i].
>>
>> Do you have a preference?
> I meant there are 5 following uses in your patch:
>
> + blk_mq_free_map_and_rqs(set, set->tags[i], i);
> + set->tags[i] = NULL;
>
> and one new helper(blk_mq_free_set_map_and_rqs(set, i)?) can be added for just
> doing that,
Ah, ok, but in the next patch we replace these blk_mq_free_map_and_rqs()
calls with __blk_mq_free_map_and_rqs(), and __blk_mq_free_map_and_rqs()
is always passed set->tags[i], so we do as you request there, i.e.
NULLify set->tags[i] in __blk_mq_free_map_and_rqs().
Thanks,
John
Powered by blists - more mailing lists