Page MenuHomeFreeBSD

Modify the vm.panic_on_oom sysctl to take a count of events
ClosedPublic

Authored by jtl on Feb 10 2020, 3:21 PM.
Tags
None
Referenced Files
F108941693: D23601.diff
Wed, Jan 29, 8:10 PM
Unknown Object (File)
Dec 12 2024, 12:59 AM
Unknown Object (File)
Dec 5 2024, 6:00 AM
Unknown Object (File)
Nov 12 2024, 5:32 PM
Unknown Object (File)
Oct 25 2024, 11:11 PM
Unknown Object (File)
Oct 21 2024, 9:35 AM
Unknown Object (File)
Oct 20 2024, 5:59 AM
Unknown Object (File)
Oct 20 2024, 3:34 AM
Subscribers

Details

Summary

Currently, the vm.panic_on_oom sysctl is a boolean. If set to 0, the VM system kills the largest process. If set to any other value, the VM system panics.

This change makes it a count of events. If set to 0, the VM system kills the largest process. If set to any other value, the VM system will kill the largest process until it has seen the specified number of out-of-memory events. Once it reaches the specified number of events, it will panic.

This change is helpful in capturing cores when the system is in a perpetual cycle of out-of-memory events (as opposed to just hitting one or two sporadic out-of-memory events).

Test Plan

Run on a system. Induce memory pressure. Ensure the system panics after the specified number of events. (This tested correctly.)

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable