Page MenuHomeFreeBSD

tmpfs: avoid the vm object lock in tmpfs_pager_getvp in the common case
AbandonedPublic

Authored by mjg on May 30 2021, 3:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sep 9 2024, 3:19 AM
Unknown Object (File)
Aug 29 2024, 3:07 PM
Unknown Object (File)
Jun 21 2024, 10:21 AM
Unknown Object (File)
May 14 2024, 10:51 AM
Unknown Object (File)
May 10 2024, 6:03 AM
Unknown Object (File)
Apr 12 2024, 9:21 AM
Unknown Object (File)
Dec 20 2023, 7:34 AM
Unknown Object (File)
Aug 13 2023, 6:39 AM
Subscribers

Details

Reviewers
kib
markj
Summary

This saves about 8% of wait time on vm object lock when doing -j 104 incremental kernel-only tinderbox run.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

mjg requested review of this revision.May 30 2021, 3:55 PM
mjg created this revision.
sys/fs/tmpfs/tmpfs_subr.c
212

What for is this acquire fence?

247

Either this check is needed in the tmpfs_pager_getvp_smp(), or it is not needed there.

In fact, I am not sure that we clean up enough of the un_pager to guarantee that swp_tmpfs is always NULL for newly allocated object, so I think that OBJT_SWAP check is still needed.