From: Bart Van Assche <bvanassche@acm.org>
To: Yu Kuai <yukuai1@huaweicloud.com>, Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v4 0/3] Support disabling fair tag sharing
Date: Tue, 31 Oct 2023 09:25:36 -0700 [thread overview]
Message-ID: <99c47a2c-e9ff-4528-ad80-98dbcc4e67ed@acm.org> (raw)
In-Reply-To: <a6575723-4903-d098-6be0-722635db1339@huaweicloud.com>
On 10/30/23 19:01, Yu Kuai wrote:
> I'm afraid that is not correct, fairness can't be guranteed at all, not
> even with just one scsi disk. This is because there are 8 wait queues in
> sbitmap, and threads are waiting in roundrobin mode, and each time
> wake_batch tags are released, wake_batch threads of one wait queue will
> be woke up, regardless that some threads can't grab tag after woken up,
> what's worse, thoese thread will be added to the tail of waitqueue
> again.
>
> In the case that high io pressure under a slow disk, this behaviour will
> cause that io tail latency will be quite bad compared to sq from old
> kernel.
>
> AFAIC, disable tag sharing will definitely case some regresion, for
> example, one disk will high io pressure, and another disk only issure
> one IO at a time, disable tag sharing can improve brandwith of fist
> disk, however, for the latter disk, IO latency will definitely be much
> worse.
Hi Yu,
All UFS users I know prefer that fair tag sharing is disabled for UFS
devices. So I propose to proceed with this patch series and additionally
to improve fair tag sharing for devices and transport layers that need
an improved sharing algorithm.
Thanks,
Bart.
prev parent reply other threads:[~2023-10-31 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 20:36 [PATCH v4 0/3] Support disabling fair tag sharing Bart Van Assche
2023-10-23 20:36 ` [PATCH v4 1/3] block: Introduce flag BLK_MQ_F_DISABLE_FAIR_TAG_SHARING Bart Van Assche
2023-10-23 20:36 ` [PATCH v4 2/3] scsi: core: Support disabling fair tag sharing Bart Van Assche
2023-10-23 20:36 ` [PATCH v4 3/3] scsi: ufs: Disable " Bart Van Assche
2023-10-24 5:36 ` Avri Altman
2023-10-24 2:28 ` [PATCH v4 0/3] Support disabling " Ming Lei
2023-10-24 16:41 ` Bart Van Assche
2023-10-25 1:33 ` Ming Lei
2023-10-25 18:50 ` Avri Altman
2023-10-26 16:37 ` Bart Van Assche
2023-10-25 19:01 ` Bart Van Assche
2023-10-25 23:37 ` Ming Lei
2023-10-26 16:29 ` Bart Van Assche
2023-10-31 2:01 ` Yu Kuai
2023-10-31 16:25 ` Bart Van Assche [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=99c47a2c-e9ff-4528-ad80-98dbcc4e67ed@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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).