add kstat to track anon memory reservation failure (ENOMEM)
When debugging systems, it's often helpful to understand if they may have hit an ENOMEM case due to failure to reserve anonymous memory. This is particularly useful in application that simply explode or blow up on memory errors and make it easier to understand what happened to them.
Updated by Electric Monk about 6 years ago
- Status changed from New to Closed
commit d14b1d19b404dcc4795d8a76751a186717a0ddaa Author: Jerry Jelinek <firstname.lastname@example.org> Date: 2016-04-30T15:20:30.000Z 6934 add kstat to track anon memory reservation failure (ENOMEM) Reviewed by: Toomas Soome <email@example.com> Reviewed by: Josef 'Jeff' Sipek <firstname.lastname@example.org> Reviewed by: Garrett D'Amore <email@example.com> Reviewed by: Yuri Pankov <firstname.lastname@example.org> Reviewed by: Igor Kozhukhov <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>