lockmgr: add adaptive spinning
ClosedPublic
Actions

Authored by mjg on Jul 21 2020, 3:18 PM.

Details

Reviewers

Commits

rS363415: lockmgr: add adaptive spinning

Summary

It is very conservative. Only spinning when LK_ADAPTIVE is passed, only on exclusive lock and never when any waiters are present. buffer cache is remains not spinning.

This reduces total sleep times during buildworld etc., but it does not help there (vm contention is the culprit along with slock + upgrade which is not covered).

For microbenchmarks: open3_processes -t 52 (open/close of the same file for writing) ops/s
before: 258845
after: 801638

Test Plan

tested by pho

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

mjg requested review of this revision.Jul 21 2020, 3:18 PM

mjg created this revision.

mjg edited the summary of this revision. (Show Details)

kib added inline comments.Jul 21 2020, 5:38 PM

sys/kern/kern_lock.c
1048	This change is unrelated ?
1234	And this.
sys/ufs/ffs/ffs_vnops.c
448	Why you enforce LK_ADAPTIVE inside lockmgr_xlock/slock, while for lockmgr_lock_flags() only do that for UFS ?

mjg added inline comments.Jul 21 2020, 6:43 PM

sys/kern/kern_lock.c
1048	with the patch lockmgr_slock_try stops reading on its own
sys/ufs/ffs/ffs_vnops.c
448	lockmgr_lock_flags is fully compatible with original lockmgr entry point in terms of semantics and I did not want to change that. In particular it may be feasible to convert bufcache to use it instead of the current __lockmgr entry point (which should be refactored away). that said, i don't have a strong opinion on this one.