Page MenuHomeFreeBSD

vmem: disable debug.vmem_check by default
ClosedPublic

Authored by mjg on Sep 2 2021, 9:51 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 6, 4:37 AM
Unknown Object (File)
Nov 18 2024, 2:44 PM
Unknown Object (File)
Sep 24 2024, 11:32 PM
Unknown Object (File)
Sep 24 2024, 6:39 AM
Unknown Object (File)
Sep 23 2024, 11:24 PM
Unknown Object (File)
Sep 23 2024, 1:49 AM
Unknown Object (File)
Sep 17 2024, 7:39 PM
Unknown Object (File)
Sep 17 2024, 5:44 AM
Subscribers
None

Details

Summary

It has a prohibitive performance impact when running real workloads.

Note this only affects kernels with DIAGNOSTIC.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

mjg requested review of this revision.Sep 2 2021, 9:51 AM
mjg created this revision.
mjg edited the summary of this revision. (Show Details)

As I understand, DIAGNOSTIC is exactly for these kinds of expensive debug checks, similar to vmmap_check for example. What's the purpose of running a real workload with DIAGNOSTIC configured?

The workload at hand is poudriere and the goal is to make sure the kernel survives with debug.

Disabling vmem_check makes it chug along with ~10% system time, while it was getting multisecond stalls otherwise. This check is just too expensive to run without being explicitly requested.

Ok, I don't think it is very useful anyway.

This revision is now accepted and ready to land.Sep 2 2021, 3:30 PM
This revision was automatically updated to reflect the committed changes.