Page MenuHomeFreeBSD

vm: Remove handling for OBJT_DEFAULT objects
ClosedPublic

Authored by markj on Jul 12 2022, 4:22 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 5, 6:27 PM
Unknown Object (File)
Mar 21 2024, 7:12 PM
Unknown Object (File)
Mar 21 2024, 7:12 PM
Unknown Object (File)
Mar 21 2024, 7:12 PM
Unknown Object (File)
Mar 21 2024, 7:12 PM
Unknown Object (File)
Mar 20 2024, 10:04 PM
Unknown Object (File)
Jan 14 2024, 10:19 AM
Unknown Object (File)
Dec 28 2023, 9:46 AM
Subscribers

Details

Summary

Now that OBJT_DEFAULT objects can't be instantiated, we can simplify
various checks of the form `object->type == OBJT_DEFAULT ||
(object->flags & OBJ_SWAP) != 0`. No functional change intended.

Diff Detail

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

Event Timeline

markj requested review of this revision.Jul 12 2022, 4:22 PM
This revision is now accepted and ready to land.Jul 12 2022, 4:55 PM

Remove a stale comment from vm_object_split().

This revision now requires review to proceed.Jul 13 2022, 1:23 PM
alc added inline comments.
sys/vm/vm_object.c
1526–1527

As an aside, I don't see why we pass a charge to vm_object_allocate_anon(). Currently, the passed charge is always equal to ptoa(size). Moreover, I'm skeptical that there will be a future scenario where it differs.

This revision is now accepted and ready to land.Jul 13 2022, 3:05 PM
This revision was automatically updated to reflect the committed changes.