Re: [PATCH] block: Improve IOPS by removing the fairness code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

在 2024/03/22 7:03, Bart Van Assche 写道:
On 3/21/24 15:48, Christoph Hellwig wrote:
On Thu, Mar 21, 2024 at 03:46:05PM -0700, Bart Van Assche wrote:
There is an algorithm in the block layer for maintaining fairness
across queues that share a tag set. The sbitmap implementation has
improved so much that we don't need the block layer fairness algorithm
anymore and that we can rely on the sbitmap implementation to guarantee
fairness.

IFF that was true it would be awesome.  But do you have proof for that
assertation?

Hi Christoph,

Is the test in this pull request sufficient as evidence that we don't
need the request queue fairness code anymore:
https://github.com/osandov/blktests/pull/135?

That test does the following:
* Create two request queues with a shared tag set and with different
   completion times (1 ms and 100 ms).
* Submit I/O to both request queues simultaneously and set the queue
   depth for both tests to the number of tags. This creates contention
   on tag allocation.
* After I/O finished, check that the fio job with the shortest
   completion time submitted the most requests.

This test is a little one-sided, I'm curious how the following test
shows as well:

- some queue is under heavy IO pressure with lots of thread, and they
can use up all the drivers tags;
- one queue only issue one IO at a time, then how does IO latency shows
for this queue? I assume this can be bad with this patch because sbitmap
implementation can't gurantee this.

Thanks,
Kuai


Thanks,

Bart.

.






[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux