On 30.11.22 г. 13:22 ч., Pavel Tikhomirov wrote:
Add a sysctl kernel.freeze_cgroup_timeout (default value 30 * HZ).
If one writes FROZEN to freezer.state file and after a timeout of
kernel.freeze_cgroup_timeout one still reads FREEZING from freezer.state
file (meaning that kernel does not succ
The commit is pushed to "branch-rh7-3.10.0-1160.80.1.vz7.191.x-ovz" and will
appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-1160.80.1.vz7.191.1
-->
commit b4013b3b36968232d163d7e4c49bc2fcf18ed1a3
Author: Alexander Atanasov
Date: Fri Dec 2 14:46:53 2022 +0200
sch
BTW, do we need a similar patch for vz7 as well?
On 30.11.2022 13:29, Nikolay Borisov wrote:
Our custom nr_unint logic follows the kernel's one about the global
nr_uninterruptible one. One invariant that both share is that values
of nr_unint can go negative when a task is migrated from a CPU.
Wha
On 7.12.22 г. 14:27 ч., nb wrote:
On 30.11.22 г. 13:22 ч., Pavel Tikhomirov wrote:
Add a sysctl kernel.freeze_cgroup_timeout (default value 30 * HZ).
If one writes FROZEN to freezer.state file and after a timeout of
kernel.freeze_cgroup_timeout one still reads FREEZING from freezer.state
fi
On 7.12.22 г. 20:02 ч., Konstantin Khorenko wrote:
BTW, do we need a similar patch for vz7 as well?
Looking at the vz7 kernel code I'd say yes since processes can still be
woken up on a different CPU than the one they went to sleep on. However,
I wonder why this issue hasn't manifested so f
