From: "Doug Smythies" <dsmythies@telus.net>
To: <yukuai@fnnas.com>
Cc: "'Nilay Shroff'" <nilay@linux.ibm.com>,
"'Bart Van Assche'" <bvanassche@acm.org>,
"'Jens Axboe'" <axboe@kernel.dk>, <linux-kernel@vger.kernel.org>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: REGRESSION BISECTED: mq-deadline: covert to use request_queue->async_depth
Date: Mon, 13 Apr 2026 20:21:16 -0700 [thread overview]
Message-ID: <002901dccbbd$c1c96110$455c2330$@telus.net> (raw)
In-Reply-To: <6e336fc5-bf39-41eb-a499-6728969bf164@fnnas.com>
Hi Kuai,
Thank you for your replies, and the time you took to write them.
On 2026.04.10 09:21 Yu Kuai wrote:
> Hi,
>
> 在 2026/4/10 13:18, Doug Smythies 写道:
>>> Do you ever use the async_depth for mq-deadline?
>> No.
>
> Then the only difference is the tag wake batch is changed from 1 to 8. However,
> batch wake up is the base design of sbitmap. And I do admit tail latency is
> bad under high concurrency is probably due to wake up is unfair, this is a
> know sbitmap design flaw and not fixed yet.
Good to know.
> You could try change wake up batch back to 1. However, I don't think this is a
> good solution. And I'll suggest you to try increase nr_requests to see if tail
> Latency gets better.
I just observed what I thought was a pretty significant regression, and thought
I should bring it the attention of the stake holders.
By decreasing the maximum concurrency of my workflow from 1000 to 64 the regression
decreased to noise levels, +/- 1.5%.
Thanks,
Doug Smythies
prev parent reply other threads:[~2026-04-14 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 23:20 REGRESSION BISECTED: mq-deadline: covert to use request_queue->async_depth Doug Smythies
2026-04-09 12:34 ` Yu Kuai
2026-04-10 5:18 ` Doug Smythies
2026-04-10 16:21 ` Yu Kuai
2026-04-14 3:21 ` Doug Smythies [this message]
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='002901dccbbd$c1c96110$455c2330$@telus.net' \
--to=dsmythies@telus.net \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nilay@linux.ibm.com \
--cc=yukuai@fnnas.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