This report is somehow related to and can be considered a continuation of:
We would be looking to minimize the number of context switches from the VDO threads this time.
Current state: starting VDO volumes that are not in use on an idle system increases the number of context switches with around 8000 context switches / second.
On an idle physical system with 4 CPUs running kernel 5.8.14 and kvdo-corp 188.8.131.52:
VDO devices are not started: 90 context switches / second
VDO devices(2 devices) are started and not used: 8000 context switches / second
The threads that consume the CPU seem to be:
In an ideal world, having started an idling VDO volume should not increase the number of context switches on the system.
any progress update with this?
(In reply to Nikolay Kichukov from comment #1)
> Hi folks,
> any progress update with this?
Sorry, Nikolay, not so far. I've had another work item ahead of it in my queue... I'll be looking into it this week though.
Verified with kmod-kvdo-184.108.40.206-79.el8
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (kmod-kvdo bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.