From: John Garry <john.garry@huawei.com>
To: Kashyap Desai <kashyap.desai@broadcom.com>, <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ming.lei@redhat.com>, <hare@suse.de>
Subject: Re: [PATCH RFT 0/3] blk-mq: Optimise blk_mq_queue_tag_busy_iter() for shared tags
Date: Thu, 25 Nov 2021 14:09:33 +0000 [thread overview]
Message-ID: <9859e133-e3b8-4e53-dfad-cbf75ed3102f@huawei.com> (raw)
In-Reply-To: <b18285f4aa0e8be796aea19cdfde0293@mail.gmail.com>
On 25/11/2021 13:46, Kashyap Desai wrote:
>> John -
>>
>> I will try something this week and let you know.
> John - I tested patchset and looks good. Issue reported at below thread is
> fixed.
> https://lore.kernel.org/linux-block/e4e92abbe9d52bcba6b8cc6c91c442cc@mail.gmail.com/
>
> Here is perf top data.
>
> 5.70% [megaraid_sas] [k] complete_cmd_fusion
> 3.80% [megaraid_sas] [k]
> megasas_build_and_issue_cmd_fusion
> 2.75% [kernel] [k] syscall_return_via_sysret
> 2.68% [kernel] [k] entry_SYSCALL_64
> 2.22% [kernel] [k] io_submit_one
> 2.19% [megaraid_sas] [k] megasas_build_ldio_fusion
> 1.95% [kernel] [k] llist_add_batch
> 1.80% [kernel] [k] llist_reverse_order
> 1.79% [kernel] [k] scsi_complete
> 1.73% [kernel] [k] scsi_queue_rq
> 1.66% [kernel] [k] check_preemption_disabled
> 1.37% [megaraid_sas] [k] megasas_queue_command
> 1.16% [kernel] [k] native_irq_return_iret
> 1.11% [kernel] [k] aio_complete_rw
> 1.07% [kernel] [k] read_tsc
> 1.06% fio [.] __fio_gettime
> 1.05% [kernel] [k] flush_smp_call_function_queue
> 1.03% [kernel] [k] blk_complete_reqs
> 1.00% [kernel] [k] blk_mq_free_request
> 0.98% [kernel] [k] sbitmap_get
>
>
> I will continue testing and let you know how it goes.
ok, good to know, thanks. But I would still like to know what is
triggering blk_mq_queue_tag_busy_iter() so often. Indeed, as mentioned
in this cover letter, this function was hardly optimised before for
shared sbitmap.
And any opinion whether we would want this as a fix? Information
requested above would help explain why we would need it as a fix.
Cheers,
John
next prev parent reply other threads:[~2021-11-25 14:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 11:27 [PATCH RFT 0/3] blk-mq: Optimise blk_mq_queue_tag_busy_iter() for shared tags John Garry
2021-11-02 11:27 ` [PATCH RFT 1/3] blk-mq: Drop busy_iter_fn blk_mq_hw_ctx argument John Garry
2021-11-09 3:02 ` Ming Lei
2021-11-28 10:39 ` Hannes Reinecke
2021-11-02 11:27 ` [PATCH RFT 2/3] blk-mq: Delete busy_iter_fn John Garry
2021-11-09 3:05 ` Ming Lei
2021-11-28 10:40 ` Hannes Reinecke
2021-11-02 11:27 ` [PATCH RFT 3/3] blk-mq: Optimise blk_mq_queue_tag_busy_iter() for shared tags John Garry
2021-11-28 10:43 ` Hannes Reinecke
2021-11-29 2:19 ` Ming Lei
2021-11-15 15:56 ` [PATCH RFT 0/3] " John Garry
2021-11-15 16:31 ` Kashyap Desai
2021-11-25 13:46 ` Kashyap Desai
2021-11-25 14:09 ` John Garry [this message]
2021-11-26 11:25 ` Kashyap Desai
2021-11-26 11:51 ` John Garry
2021-12-06 9:57 ` John Garry
2021-12-06 10:03 ` Kashyap Desai
2021-12-08 13:04 ` John Garry
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=9859e133-e3b8-4e53-dfad-cbf75ed3102f@huawei.com \
--to=john.garry@huawei.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.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