From: Bart Van Assche <bvanassche@acm.org>
To: YangYang <yang.yang@vivo.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Zhiguo Niu <zhiguo.niu@unisoc.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v2 2/2] block/mq-deadline: Fix the tag reservation code
Date: Thu, 16 May 2024 15:27:49 -0600	[thread overview]
Message-ID: <c9900a6e-889d-4b7c-8aba-4ab1a89c3672@acm.org> (raw)
In-Reply-To: <fcaa5844-e2fb-41d6-8a38-2e318b3e3311@vivo.com>
On 5/16/24 02:14, YangYang wrote:
>> @@ -513,9 +527,9 @@ static void dd_depth_updated(struct blk_mq_hw_ctx 
>> *hctx)
>>       struct deadline_data *dd = q->elevator->elevator_data;
>>       struct blk_mq_tags *tags = hctx->sched_tags;
>> -    dd->async_depth = max(1UL, 3 * q->nr_requests / 4);
>> +    dd->async_depth = q->nr_requests;
>> -    sbitmap_queue_min_shallow_depth(&tags->bitmap_tags, 
>> dd->async_depth);
>> +    sbitmap_queue_min_shallow_depth(&tags->bitmap_tags, 1);
> 
> If sbq->min_shallow_depth is set to 1, sbq->wake_batch will also be set
> to 1. I guess this may result in batch wakeup not working as expected.
The value of the sbq->min_shallow_depth parameter may affect performance
but does not affect correctness. See also the comment above the
sbitmap_queue_min_shallow_depth() declaration. Is this sufficient to
address your concern?
Thanks,
Bart.
next prev parent reply	other threads:[~2024-05-16 21:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 17:01 [PATCH v2 0/2] Fix the mq-deadline async_depth implementation Bart Van Assche
2024-05-09 17:01 ` [PATCH v2 1/2] block: Call .limit_depth() after .hctx has been set Bart Van Assche
2024-07-02  8:39   ` 答复: " 牛志国 (Zhiguo Niu)
2024-07-02 12:08   ` Christoph Hellwig
2024-05-09 17:01 ` [PATCH v2 2/2] block/mq-deadline: Fix the tag reservation code Bart Van Assche
2024-05-16  8:14   ` YangYang
2024-05-16 21:27     ` Bart Van Assche [this message]
2024-06-04  9:08       ` 答复: " 牛志国 (Zhiguo Niu)
2024-06-04 11:48         ` Bart Van Assche
2024-07-01  1:30           ` 答复: " 牛志国 (Zhiguo Niu)
2024-07-01 23:21             ` Bart Van Assche
2024-07-02 12:09   ` Christoph Hellwig
2024-12-07  2:17   ` Yu Kuai
2024-12-09 19:08     ` Bart Van Assche
2024-12-10  1:09       ` Yu Kuai
     [not found] ` <202407020202.46222wCt089266@SHSPAM01.spreadtrum.com>
2024-07-02  8:41   ` 答复: " 牛志国 (Zhiguo Niu)
2024-07-02 14:48 ` [PATCH v2 0/2] Fix the mq-deadline async_depth implementation Jens Axboe
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=c9900a6e-889d-4b7c-8aba-4ab1a89c3672@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=yang.yang@vivo.com \
    --cc=zhiguo.niu@unisoc.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;
as well as URLs for NNTP newsgroup(s).