This has been reported upstream as well, with a tentative patch in
https://lkml.org/lkml/2019/3/7/8

I've done some tests in fio to get some more data on this issue, with the 
following scenarios:
- "raw" test     -> fio test without any sysfs queries
- "sysfs" test   -> fio + scripted sysfs queries
- "mutex" test   -> fio + sysfs + mutex patch
- "resched" test -> fio + sysfs + cond_resched() patch

The "mutex patch" removed bucket locking from the sysfs query. This
caused the stats to be computed all wrong of course, but we weren't
interested in the stats themselves for now (just on the performance
impact of the bucket locking).

The "cond_resched()" patch was suggested upstream by Shile Zhang, and
introduces a cond_resched() call in the comparison function used for
sorting.

Tests were run on a NVMe-backed bcache device with writeback enabled.
The full logs and graphs are available in the bcache-results.tar.gz
attachment.

** Attachment added: "bcache-results.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840043/+attachment/5282348/+files/bcache-results.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840043

Title:
  bcache: Performance degradation when querying priority_stats

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to