Doesn't prioritize requests and doesn't have fairness with LVM/DeviceMapper about bfq-mq HOT 4 OPEN

Il giorno 29 gen 2021, alle ore 00:17, Iván Baldo ***@***.***> ha scritto: Using a simple LVM setup without nothing fancy, just pvcreate, vgcreate and simple lvcreate, no encryption, no RAID, just simple normal LVM, idle priority tasks just use the disk evenly with normal priority ones, high priority tasks don't get any boost, etc. At least with kernel 5.4... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks for reporting this problem. Unfortunately, given my very limited time, it may take a lot before I'll reproduce and work on it. In contrast, since you already have the problem reproduced, it would be relatively easy for you to feed me with the information I need. If you are willing to help, just do this: - put in a script the commands with which you reproduce the problem, and show me the script - build and install the current dev version of bfq (dev-bfq-on-5.6) - reproduce the problem with the current dev version of bfq - show me the numbers that tell you that bandwidth is not divided as expected - after confirming the problem, download the S benchmark suite, and use the script utilities/tracing.sh contained there, to trace events (simple instructions in the script itself) - share the block trace that you get I'll take over from there, and maybe I'll ask you for some more trace while fixing the problem. Thanks, Paolo > Il giorno 29 gen 2021, alle ore 00:17, Iván Baldo < ***@***.***> ha scritto: > > > Using a simple LVM setup without nothing fancy, just pvcreate, vgcreate and simple lvcreate, no encryption, no RAID, just simple normal LVM, idle priority tasks just use the disk evenly with normal priority ones, high priority tasks don't get any boost, etc. > > At least with kernel 5.4... > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or unsubscribe. > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKASAMWR2LNBTWZ7ORPOBLS4JSHHANCNFSM4WX47KJA> .