mirror of
https://github.com/Zygo/bees.git
synced 2025-05-17 21:35:45 +02:00
context: downgrade toxic extent workaround message
Toxic extents are much less of a problem now than they were in kernels before 5.7. Downgrade the log message level to reflect their lesser importance. Signed-off-by: Zygo Blaxell <bees@furryterror.org>
This commit is contained in:
parent
d6732c58e2
commit
3f23a0c73f
@ -832,7 +832,7 @@ BeesContext::resolve_addr_uncached(BeesAddress addr)
|
|||||||
if (sys_usage_delta < BEES_TOXIC_SYS_DURATION) {
|
if (sys_usage_delta < BEES_TOXIC_SYS_DURATION) {
|
||||||
rv.m_is_toxic = false;
|
rv.m_is_toxic = false;
|
||||||
} else {
|
} else {
|
||||||
BEESLOGNOTICE("WORKAROUND: toxic address: addr = " << addr << ", sys_usage_delta = " << round(sys_usage_delta* 1000.0) / 1000.0 << ", user_usage_delta = " << round(user_usage_delta * 1000.0) / 1000.0 << ", rt_age = " << rt_age << ", refs " << rv_count);
|
BEESLOGDEBUG("WORKAROUND: toxic address: addr = " << addr << ", sys_usage_delta = " << round(sys_usage_delta* 1000.0) / 1000.0 << ", user_usage_delta = " << round(user_usage_delta * 1000.0) / 1000.0 << ", rt_age = " << rt_age << ", refs " << rv_count);
|
||||||
BEESCOUNT(resolve_toxic);
|
BEESCOUNT(resolve_toxic);
|
||||||
rv.m_is_toxic = true;
|
rv.m_is_toxic = true;
|
||||||
}
|
}
|
||||||
|
Loading…
x
Reference in New Issue
Block a user