From: Ming Lei <ming.lei@redhat.com>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: John Garry <john.garry@huawei.com>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
kashyap.desai@broadcom.com, chenxiang66@hisilicon.com,
yama@redhat.com
Subject: Re: [PATCH] blk-mq: Use request queue-wide tags for tagset-wide sbitmap
Date: Tue, 11 May 2021 09:47:34 +0800 [thread overview]
Message-ID: <YJniNq6LYqiLFIlP@T590> (raw)
In-Reply-To: <0faa2ad6-4ae9-02b2-2f34-cf58f1e23c5b@interlog.com>
On Mon, May 10, 2021 at 09:35:01PM -0400, Douglas Gilbert wrote:
> On 2021-05-10 8:52 p.m., Ming Lei wrote:
> > On Mon, May 03, 2021 at 06:22:13PM +0800, John Garry wrote:
> > > The tags used for an IO scheduler are currently per hctx.
> > >
> > > As such, when q->nr_hw_queues grows, so does the request queue total IO
> > > scheduler tag depth.
> > >
> > > This may cause problems for SCSI MQ HBAs whose total driver depth is
> > > fixed.
> > >
> > > Ming and Yanhui report higher CPU usage and lower throughput in scenarios
> > > where the fixed total driver tag depth is appreciably lower than the total
> > > scheduler tag depth:
> > > https://lore.kernel.org/linux-block/440dfcfc-1a2c-bd98-1161-cec4d78c6dfc@huawei.com/T/#mc0d6d4f95275a2743d1c8c3e4dc9ff6c9aa3a76b
> > >
> >
> > No difference any more wrt. fio running on scsi_debug with this patch in
> > Yanhui's test machine:
> >
> > modprobe scsi_debug host_max_queue=128 submit_queues=32 virtual_gb=256 delay=1
> > vs.
> > modprobe scsi_debug max_queue=128 submit_queues=1 virtual_gb=256 delay=1
> >
> > Without this patch, the latter's result is 30% higher than the former's.
> >
> > note: scsi_debug's queue depth needs to be updated to 128 for avoiding io hang,
> > which is another scsi issue.
>
> "scsi_debug: Fix cmd_per_lun, set to max_queue" made it into lk 5.13.0-rc1 as
> commit fc09acb7de31badb2ea9e85d21e071be1a5736e4 . Is this the issue you are
> referring to, or is there a separate issue in the wider scsi stack?
OK, that is it, then it isn't necessary to update scsi_debug's queue
depth for the test.
Thanks,
Ming
next prev parent reply other threads:[~2021-05-11 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 10:22 John Garry
2021-05-06 8:32 ` Ming Lei
2021-05-07 10:15 ` John Garry
2021-05-11 0:52 ` Ming Lei
2021-05-11 1:35 ` Douglas Gilbert
2021-05-11 1:47 ` Ming Lei [this message]
2021-05-11 7:33 ` 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=YJniNq6LYqiLFIlP@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=chenxiang66@hisilicon.com \
--cc=dgilbert@interlog.com \
--cc=john.garry@huawei.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yama@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
all inboxes | Powered by JetHome®