Messages in this thread | | | Subject | Re: [PATCH RESEND v3 03/13] blk-mq: Relocate shared sbitmap resize in blk_mq_update_nr_requests() | From | Hannes Reinecke <> | Date | Tue, 14 Sep 2021 07:37:51 +0200 |
| |
On 9/13/21 5:12 PM, John Garry wrote: > For shared sbitmap, if the call to blk_mq_tag_update_depth() was > successful for any hctx when hctx->sched_tags is not set, then it would be > successful for all (due to nature in which blk_mq_tag_update_depth() > fails). > > As such, there is no need to call blk_mq_tag_resize_shared_sbitmap() for > each hctx. So relocate the call until after the hctx iteration under the > !q->elevator check, which is equivalent (to !hctx->sched_tags). > > Signed-off-by: John Garry <john.garry@huawei.com> > Reviewed-by: Ming Lei <ming.lei@redhat.com> > --- > block/blk-mq.c | 12 +++++++----- > 1 file changed, 7 insertions(+), 5 deletions(-) > Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
| |